[Hardy] wpa_supplicant fails to associate if bssid is specified in network block

[Brandon Applegate]

Binary package hint: wpasupplicant

Background: I'm not using NetworkManager at all. All disabled, custom wpa_supplicant.conf and custom /etc/network/interfaces. I manually control interfaces with ifup/ifdown and wpa_cli. This was working fine in Gutsy. Specifically the ability to add a bssid=xx:xx:xx:xx:xx:xx line to a network block in /etc/wpa_supplicant.conf. When I do that now (Hardy), everything appears to be working but association never happens. In fact, wlan_tkip/wlan_ccmp don't get pulled in because wpa_supplicant doesn't 'match' my SSID/BSSID. When I remove the bssid declaration, association works (wlan_tkip/wlan_ccmp get pulled in etc). It of course picks whichever AP wpa_supplicant chooses (using default ap_scan=1 (wpa_supplicant controls scanning / selection - NOT the driver)).

I had thought this was a problem with svn madwifi drivers, but even using the default *restricted* modules from Hardy (madwifi 0.9.4) this behaviour persists.

I've been essentially using the same wpa_supplicant.conf since Dapper I believe. Since I'm submitting this now via my WPA AP at my house, obviously the driver is working. I am of the opinion that this is a wpa_supplicant issue because with ap_scan=1 (the default), wpa_supplicant is responsible for doing scanning and picking the AP.

[Brandon Applegate (vom)]

I should add that this only happens when wpa_supplicant is daemonized (-B). This is of course the normal operational mode. If I remove -B and run it in the foreground, I successfully associate to the bssid I specify.

[Brandon Applegate (vom)]

This is not the root cause symptom, I jumped the gun. I am definitely having issues with WPA since moving from Gutsy to Hardy, and I will wait until I have a better handle on it to open a bug.