On Wed, 2009-12-02 at 16:25 +0100, Oliver Kastner wrote: > Hello, > here's a weird WPA2 problem: > After having sucessfully connected to a (formerly unkown) WPA/WPA2 > secured WIFI network, any consecutive login fails. Deleting the > according entry in the Wireless networks configartion menu does not > alter the situation. > > The Network is recognised properly, but the secrets are not accepted. > The secrets input dialog is iteratively prompted after input. > > Similar problems occur with other WPA/WPA2 secured WIFI networks.
For that specific log you sent, code 17 is "Association denied; access point is resource-constrained". That basically means the problem is not your problem, the AP is overloaded and there's not much you can do. I guess it would be helpful if wpa_supplicant would simply blacklist that AP for a while, or if the supplicant could get information out of the kernel (it can't yet) about the real association failure and then try another AP. But the end result is that it's the AP's problem, not a problem with your machine. We need to do better with telling you, the user, why something doesn't work, and that's happening slowly with the new supplicant dbus interface and the supplicant's nl80211 driver. Dan _______________________________________________ NetworkManager-list mailing list [email protected] http://mail.gnome.org/mailman/listinfo/networkmanager-list
