Am Montag, 6. April 2009 schrieb Kalle Valo: > Helmut Schaa <helmut.schaa@xxxxxxxxxxxxxx> writes: > > >> Then there is something happening in ath9k or your AP which prevents > >> ath9k from receiving beacons. Try pinging your AP with 100 ms > >> interval. Do you see anything happening in 120 s intervals? > > > > NetworkManager typically scans every 120 seconds and I can also trigger > > the messages by a manual scan with iwlist. I did not dig any further but > > the messages seem to appear right at the end of the scan. Tried with iwlagn > > and both sw_scan and hw_scan. > > Thanks, this was valuable info. It might be that my beacon filtering > patches broke something related to scanning and beacon loss check. I'll > take a look at this. Maybe you did not break anything. During a scan we will stay away from the operating channel for some seconds which indeed prevents us from receiving beacons. I'd say sending a probe request to the AP in that case won't hurt. Helmut -- 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
