Gareth McCaughan <[email protected]> writes: > I have some reason to believe the following: > > * Some Cisco wireless APs will regularly try to force clients > to reauthenticate by sending deauthorization frames > with reason code 2 (PREV_AUTH_NOT_VALID). > > * When one of these arrives, wpa_supplicant will respond by > putting the AP on a blacklist and roaming to another AP > rather than by immediately trying to reauthenticate with > the same AP. > > This is a Bad Thing (isn't it?) because e.g. if you have two of > these APs within range but one provides a much better signal > than the other, you'll alternate between them rather than > sticking with the good one. It seems like it might be better > for wpa_supplicant to try the original AP again immediately. > > (The problem that actually sent me looking at this stuff is > more severe and involves machines completely falling off > the network after several of these transitions, but I think > that's a separate issue that I don't understand yet.) > > Some details follow.
wpa_supplicant and hostapd have a dedicated list: http://lists.infradead.org/mailman/listinfo/hostap -- Kalle Valo -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
