wpa_supplicant deassociated, doesn't reassociate

Michael Smith msmith at cbnco.com
Thu Nov 24 16:36:56 EST 2005


Hi,

I'm on Linux 2.6.11.11, trying to switch to wpa_supplicant/hostapd 0.4.7 + 
madwifi-ng (was wpa/hostapd 0.4.3 and a madwifi-bsd checkout from June).

I have a ~3km noisy test link and I'm having a problem that I can't 
reliably reproduce yet. If the madwifi-ng master deassociates the station 
(e.g. due to AP config change), sometimes the client isn't able to 
reassociate on the first try, probably because of a lost packet:

Nov 24 21:24:27 auriga-red-0 hostapd: ath0: STA 00:02:6f:xx:xx:xx IEEE 
802.11: associated
Nov 24 21:24:30 auriga-red-0 hostapd: ath0: STA 00:02:6f:xx:xx:xx IEEE 
802.11: deauthenticated due to local deauth request
Nov 24 21:24:30 auriga-red-0 hostapd: ath0: STA 00:02:6f:xx:xx:xx IEEE 
802.11: deassociated

Normally the client immediately tries to reassociate, but a few times I've 
seen it never come back. Logging into the client over another link, I can 
check wpa_supplicant and it thinks it is in state COMPLETED, with bssid 
00:00:00:00:00:00. I told it "reassoc", but it didn't seem to do anything 
(no association reported on the master). A reboot of the client fixes it, 
a reboot of the master does not.

I know it's pretty vague at this point, but any suggestions on where to 
look in wpa_supplicant would be helpful.

Thanks,
Mike



More information about the HostAP mailing list