On Sunday 02 November 2008 23:29:35 Luis R. Rodriguez wrote: > On Sun, Nov 2, 2008 at 2:03 PM, Michael Buesch <mb@xxxxxxxxx> wrote: > > On Sunday 02 November 2008 22:05:56 Luis R. Rodriguez wrote: > >> I'm curious if others are getting this frequently as I am: > >> > >> No ProbeResp from current AP 00:DE:AD:BE:EE:FF - assume out of range > >> > >> I get this with ath5k and ath9k, can be triggered easily in ath5k by > >> doing a lot of consecutive: > >> > >> iwlist wlan0 scan > >> > >> I have to check if I can trigger this with ath9k by scanning too. We > >> were seeing this with ath9k but were thinking it was ath9k related as > >> it can be triggered on it after doing a large TX. Wondering if this is > >> more of a generic and mac80211 issue. > > > > IMO this is a mac80211 issue. > > mac80211 immediately assumes the connection is broken, if one probe-resp > > to a keekalife-proberequest is lost. > > So if you scan just after the request got sent, you'll never receive the response > > and mac80211 will terminate the connection. > > It should try a few times, instead, before blowing up things. > > Agreed, and I can trigger this without scanning BTW, Yeah, me too. This can happen on normal life packet loss. It just has to lose the right packet. :) > do we simply bail > out immediately if *one* probe response was not received? Last time I looked, the code was pretty much that way. It's a bit complicated, as it uses some statemachine, but I think it bailed out after one failure. Dunno how the code looks today, but I bet it's pretty much the same. -- Greetings Michael. -- 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
