Dan Williams <dcbw@xxxxxxxxxx> writes: > When L2 drops the supplicant will attempt to reconnect only to the SSID > of the enabled network block sent by Connman. When the supplicant > enters the DISCONNECTED state from a previously-connected state, > Connman could start a short timer (15 or 20 seconds?) and wait for the > ASSOCIATING state to happen. If the supplicant does begin associating > that's great, wait for COMPLETED and leave L3 up and running. But if > the timer expires, it's likely the supplicant doesn't have anything to > connect to, and L3 can be torn down. > > Does that seem like reasonable behavior? I think the supplicant's > behavior is currently sufficient for the problem you describe, just > that Connman's interpretation of that behavior is somewhat wrong. FWIW I tried adding the timer something like 5 years ago, no luck :) http://connman.connman.narkive.com/ib9Fhk62/patch-0-2-wifi-disconnect-timer -- Kalle Valo _______________________________________________ Hostap mailing list Hostap@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/hostap
