On Wed, 2011-09-28 at 14:13 -0400, Andy Pintar wrote: > > I'm able to replicate the problem using just wpa_supplicant. After the > > connection drops (due to bad reception) wpa_supplicant gets stuck trying > > to re-authenticate. I have to kill wpa_supplicant and start it again to > > get my connection back. > > Hmm... that's weird. Can you clarify what you mean by 'stuck' trying to > reauth?
The wpa_supplicant debug output is a bit overwhelming, but basically it just can't re-authenticate for whatever reason. I see a lot "EAPOL: Supplicant port status: Unauthorized" and some timeout messages, when I run the "status" command from wpa_cli the output looks like this: > status bssid=00:25:45:34:eb:f0 ssid=ConcordiaUniversity id=0 mode=station pairwise_cipher=CCMP group_cipher=TKIP key_mgmt=WPA2/IEEE 802.1X/EAP wpa_state=ASSOCIATED ip_address=132.205.157.148 Supplicant PAE state=AUTHENTICATING suppPortStatus=Unauthorized EAP state=IDLE selectedMethod=25 (EAP-PEAP) EAP TLS cipher=DHE-RSA-AES256-SHA EAP-PEAPv0 Phase2 method=MSCHAPV2 So I'm associated with the AP, but the authentication just ain't happening. > Do you have wpa_supplicant working for ifup/down? No, I've been doing running wpa_supplicant and dhclient manually. > If so does that work to reconnect? Yup, generally if I kill the wpa_supplicant process and start it up again then the connection comes back. > Also are you sure it's not a dhcp thing? This has nothing to do with dhcp, in fact for this test I don't even have a dhcp client running (I actually have a wired connection atm). I'm just testing with wpa_supplicant. > Do you know what kind of AP it is? I think they're Cisco-brand, if that's what you're asking for... nick _______________________________________________ mlug mailing list [email protected] https://listes.koumbit.net/cgi-bin/mailman/listinfo/mlug-listserv.mlug.ca
