linux-kernel - Re: ath9k becon loss messages

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 06 Apr 2009 11:17:34 +0300
From:	Kalle Valo <kalle.valo@....fi>
To:	Helmut Schaa <helmut.schaa@...glemail.com>
Cc:	Jaswinder Singh Rajput <jaswinder@...nel.org>,
	Michael Buesch <mb@...sch.de>,
	Sujith <Sujith.Manoharan@...eros.com>,
	wireless <linux-wireless@...r.kernel.org>,
	David Miller <davem@...emloft.net>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: ath9k becon loss messages

Helmut Schaa <helmut.schaa@...glemail.com> 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.

-- 
Kalle Valo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/