Johannes Berg <johannes@xxxxxxxxxxxxxxxx> writes: >> Perhaps the new beacon filtering work [1] is changing more than it >> intended? > > I think it only changed the messages here. Previously, that message > simply wouldn't have been there, instead you'd only have seen the "No > ProbeResp from current AP - assume out of range" thing. At least I have been using latest wireless-testing with iwl3945 all the time (for example right now) and I haven't noticed any problems. But your comment makes me think is the "beacon loss" message too verbose. Maybe we should remove it? BTW, what are the AP settings (beacon interval, DTIM)? Was power save enabled in the driver? If the beacon interval is really long, like 1 second, our timer is far from optimal and missing beacon only once might trigger the warning. We should fix that properly at some point. -- Kalle Valo -- 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
