Hi Kalle, On Tue, Oct 26, 2010 at 07:30:53PM +0300, Kalle Valo wrote: > In a big network, for example at Ubuntu Developer Summit which has >10 APs, > connman and wpasupplicant got out of sync very easily. connman claimed it > was connected even though wpasupplicant (and the kernel driver) was actually > connected to the AP. Did you mean connman claimed it was _disconnected_ ?
> The problem is that while roaming between APs inside ESS wpasupplicant states > go like this: > > COMPLETED -> DISCONNECTED -> SCANNING -> AUTHENTICATING ... -> COMPLETED > > So what happens is that connman unnecessarily marks the network disconnected > even though wpasupplicant is just roaming to a different AP within ESS. Well it really got disconnected from the AP, so ConnMan should just track that. I'm really not a big fan of trying to be smarter than wpa_supplicant. In my experience, it's the shortest paths to new bugs > To fix this add a timer which waits 10 seconds after a disconnected state. > If wpasupplicant hasn't connected to a network at time only then set the > network disconnected. It looks a bit like a hack to me, the fundamental issue (ConnMan not tracking the wpa_supplicant states properly, it seems) is not fixed. Cheers, Samuel. -- Intel Open Source Technology Centre http://oss.intel.com/ _______________________________________________ connman mailing list [email protected] http://lists.connman.net/listinfo/connman
