On Fri, 2009-05-15 at 09:33 -0400, John W. Linville wrote: > On Fri, May 15, 2009 at 01:10:28PM +0200, Jan Engelhardt wrote: > > > when the AP flakes out, or I just appen to be out of range, the kernel > > drops the AP association, as dmesg shows: > > > > wlan0: No ProbeResp from current AP 00:0b:0e:4f:cf:80 - assume out of > > range > > > > Manually rerunning `iwconfig wlan0 essid FooNet channel 11` > > reassociates, but I wonder whether the kernel could not do that itself, > > given that it knows the previous settings like ESSID. > > Patches welcome... :-) This does cause problems in some cases, at least for WEXT. iwl does attempt to continually reassociate, and that results in some cases where streams of disassoc events overwhelm userspace. The supplicant should obviously get fixed here, but before doing something like this, we should make sure that all the nl80211 calls are implemented to tell the driver "Stop whatever you're doing and idle yourself". I've talked about this with Johannes before so he may have already stuffed that into nl80211 somewhere. Dan -- 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
