On Fri, 2016-10-21 at 17:54 +0000, Stéphane Boucher wrote: > Here's the driver, as well as a failed activation (I hit escape when > I got the popup) and a successful activation (no popup) > > $ ethtool -i wlp3s0 > driver: wl0 > version: 6.30.223.248 (r487574)
So proprietary Broadcom wl driver, which gives you: Oct 21 13:34:32 toaster wpa_supplicant[932]: wlp3s0: WPA: Failed to set PTK to the driver (alg=3 keylen=16 bssid=34:97:f6:06:26:88) Oct 21 13:34:32 toaster wpa_supplicant[932]: wlp3s0: CTRL-EVENT- DISCONNECTED bssid=34:97:f6:06:26:88 reason=1 locally_generated=1 Oct 21 13:34:32 toaster wpa_supplicant[932]: wlp3s0: WPA: 4-Way Handshake failed - pre-shared key may be incorrect Oct 21 13:34:32 toaster wpa_supplicant[932]: wlp3s0: CTRL-EVENT-SSID- TEMP-DISABLED id=0 ssid="Castonguay" auth_failures=1 duration=10 reason=WRONG_KEY This is most likely a driver problem. The driver is refusing to accept the WPA key that the supplicant is trying to give it, and that's what's causing the disconnect. To the supplicant and NM, this looks like the key is actually wrong. While the supplicant could handle this better and notice that the failure to install the PTK is not actually the key being wrong but the driver falling over, the driver really shouldn't do that... Dan _______________________________________________ networkmanager-list mailing list [email protected] https://mail.gnome.org/mailman/listinfo/networkmanager-list
