On Thu, Mar 16, 2017 at 9:48 PM, Dan Williams <dcbw@xxxxxxxxxx> wrote: > Yeah, so changing the password gets you into trouble. The supplicant > keeps trying to connect and keeps failing, so it starts backing off: Yea, changing the password was the easiest way I knew how to replicate the issue. I'm not sure what is exactly wrong with the AP I'm having trouble with out in the field (or even which exact AP is the issue). > The bug here is probably that the supplicant doesn't set a wakeup timer > for when the temporary disablement expires, and then clear the > disablement and retry the connection. So, there doesn't appear to be an official bug tracker or anything for wpa_supplicant... In the mean time, I'm working around the issue with a bash script as a cron job every 5 minutes. But, I would love to have a better solution / integrated fix (I like having as few band-aids and hacks as possible). Thanks, jake _______________________________________________ Hostap mailing list Hostap@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/hostap
