On Fri, 2017-04-14 at 00:15 +0200, Gilles wrote: > On 13/04/2017 17:43, Dan Williams wrote: > > One really stupid question; have you power-cycled your AP? I have > > seen > > quite a few consumer-level APs get into states like this, which a > > reboot fixes temporarily. > > Thanks for the tip. Power-cycling the AP did the trick. Yeah, unfortunately that is often what's required. > Still… > 1. Why does it work fine with XPSP3 runnning on that same hardware, > or > my Android smartphone? Probably driver differences between Windows and Linux that trigger that bug in the AP. And the Android phone probably has different wifi hardware that wouldn't have that issue. > 2. It still takes 30-45 seconds for Linux Mint to connect: Why is it > that slow? That's a great question, and it shouldn't take that long. Can you grab supplicant debugging for that? Run these two commands: sudo dbus-send --system --print-reply --dest=fi.w1.wpa_supplicant1 /fi/w1/wpa_supplicant1 org.freedesktop.DBus.Properties.Set string:fi.w1.wpa_supplicant1 string:DebugTimestamp variant:boolean:true sudo dbus-send --system --print-reply --dest=fi.w1.wpa_supplicant1 /fi/w1/wpa_supplicant1 org.freedesktop.DBus.Properties.Set string:fi.w1.wpa_supplicant1 string:DebugLevel variant:string:"msgdump" (yeah I know they're long) and then you should have lots of debugging info in your logs for the supplicant process. Note this may disclose your passphrase, so you might want to take a look first and scrub them. Dan _______________________________________________ Hostap mailing list Hostap@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/hostap
