On Tue, Apr 01, 2008 at 02:03:54PM +0200, Johannes Berg wrote: > > > > > After browsing the internet, I found a lot of people with the same > > > > problem and no solution. So, I dived into the code and found a simple > > > > solution: ignore disassociation. When a new request arrives to the > > > > wireless, a reconnection is done automatically. > > > > Ignoring the disassociation from the AP is suspect... wouldn't the AP > > be releasing resources associated with the station, requiring a > > reassociate/reauth from the station? Reason 4 seems to mean "Inactivity > > timer expired and station was disassociated". > > Indeed. > > > A better solution would be to queue up a reassocation worker if the AP > > kicked you off for reason 4, maybe? > > It would think so, yes. But would that reassociation be any more likely to succeed than the one that the current (unpatched) code is attempting? It seems likely to me that the patch ignoring disassociation (thereby provoking a deauth and new assoc) is effectively hacking the MLME state machine. I'll take a look to see if I can figure it out -- suggestions welcome. John -- John W. Linville linville@xxxxxxxxxxxxx -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
