wpa & wds attempts

Leonardo Maccari maccari-thisaintpartofmyaddress- at lenst.det.unifi.it
Fri Jun 10 11:04:28 EDT 2005

I'm trying to make it work, and I'd appreciate some suggestions to see if
I'm on the right direction.
If the two AP share the same ssid, using wpa_supplicant on wlan0wds* gets
till association, so the supplicant can send EAPOL START (I'm using a
802.11i configuration with RADIUS). Then, first problem is that the packet
is not a TODS packet, so the one acting as an authenticator doesn't consider
it, but this can be patched in driver.c. then the Authenticator sends
identity request.
the problem now is that packets from the AP acting as a supplicant are
intercepted by hostapd demon, that bothers about receiving datas from
unassociated station. I understand this and can be patched as well.
what I don't understand is why the packet fails the check with
rfc1042_header and exactly how this works.

then even if the packet makes its way through the driver, will it ever be
received also from wds interface?

I was thinking to write a "fake" driver file, that the supplicant
can use when it wants to use a wds interface, but I encounter problems 
in the generic driver.c code, but the interface in repeater mode does
behave like a master mode or what?


   Key fingerprint = 3129 C583 F03B 2E73 0115  C040 3489 0185 B592 19FE
 Obviously -thisaintpartofmyaddress- is not part of my real email address 

More information about the HostAP mailing list