wpa_supplicant + hostap -- won't associate with open APs.
Wed Dec 22 12:58:11 PST 2004
Jouni Malinen wrote:
> On Sat, Dec 18, 2004 at 08:01:32PM -0500, Tony Espy wrote:
>>I think I may have uncovered a bug in wpa_supplicant v0.2.5 in
>>combination with the hostAP driver.
>>I'm using wpa_supplicant for associating with APs running WEP & WPA-PSK
>>as well as open APs. I found in my testing that wpa_supplicant wouldn't
>>properly associate with open APs.
>>The function wpa_supplicant_hostap_set_wpa() in driver_hostap.c is
>>always called by wpa_supplicant_driver_init(). It always sets
>>PRISM2_PARAM_PRIVACY_INVOKED to true. I've found that this has the ill
>>side-effect of preventing wpa_supplicant from associating with an open
>>AP ( ie. no WEP or WPA ). When I commented this line out, everything
> Which AP did you use? This may be somewhat implementation specific since
> I was able to associate with an AP using plaintext.
The AP is a Linksys WRT54G.
When I use the base 0.2.5 code, wpa_driver_hostap_associate() is called
for the configured AP, the authentication timeout is set to 5 sec, and
then I see a SIOCGIWAP wireless event received with a BSSID of all 00's.
My configuration file looks like this:
> Anyway, the change you have looks fine and I did a similar changed,
> though based on key_mgmt, not wpa_ie == NULL, to cover IEEE 802.1X
> with WEP keys case.
Can you post your version of the change so I can try and stay in sync?
More information about the Hostap