On 17-01-26 09:36 AM, Andrew Shadura wrote: > Hi everyone, > > I have cherry-picked a few patches from the upstream Git repository. > > While I don't have much hope they fix all of your issues, there's still > some chance they do improve the state of things. > > Please test this version, ensuring you have the latest NM/wicd/whatever > installed, making sure you don't have misconfigurations with MSCHAPv2 as > in [1], and you have MAC randomisation disabled as in [2].
Thanks. I just upgraded wpasupplicant to the latest (2.6-3) from 2.5-2+v2.4-3+b1 (I was holding at that version, until now). I am also using the latest network-manager (1.6.0-1), with the "wifi.scan-rand-mac-address=no" setting documented in [2]. The result is an improvement over what I was experiencing with the previous version of wpasupplicant (2.6-2). Specifically, I can now get a reliable wifi connection with WPA/WPA2 security. However, when creating a new connection profile in NM (using nmtui), I do need to "activate" the profile twice before it connects successfully. What happens is: the first attempt to activate the new connection always fails after ~25 seconds, but then a second "activate" usually succeeds immediately. Weird. On subsequent reboots, the connection seems to come up successfully automatically. So, for me, this version of wpasupplicant is working adequately. However, I feel like wpasupplicant 2.5-2+v2.4-3+b1 is still more stable with my wifi hardware and driver (BCM43228 and broadcom-sta-dkms, respectively), since it never seems to have any hiccups or problems activating new connection profiles. > If by any chance you're not observing your symptoms any longer, please > report here, and if you have enough time, try reverting [2] and seeing > whether that breaks it again or not — and report here again. I tried removing "wifi.scan-rand-mac-address=no" from my NM config. It seems to make wifi reconnections after a reboot to fail quite often (but not always). So, for now, I am going keep that configuration. Steven M. > > Thanks. > > [1]: > https://wiki.archlinux.org/index.php/WPA_supplicant#Problems_with_eduroam_and_other_MSCHAPv2_connections > > [2]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=849077#50 >
