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]

Message-Id: <200904060914.32245.helmut.schaa@gmail.com>
Date:	Mon, 6 Apr 2009 09:14:31 +0200
From:	Helmut Schaa <helmut.schaa@...glemail.com>
To:	Kalle Valo <kalle.valo@....fi>
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

Am Sonntag, 5. April 2009 schrieb Kalle Valo:
> Jaswinder Singh Rajput <jaswinder@...nel.org> writes:
> 
> >> And besides that, I think one can easily remotely trigger this
> >> message and flood the logs. So it should probably _also_ be
> >> ratelimited.
> >
> > normally it prints after 120 seconds:
> >
> > [ 1078.848434] wlan0: beacon loss from AP 00:11:95:9e:df:f6 - sending probe request
> > [ 1198.822913] wlan0: beacon loss from AP 00:11:95:9e:df:f6 - sending probe request
> > [ 1318.824931] wlan0: beacon loss from AP 00:11:95:9e:df:f6 - sending probe request

> 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.

Helmut
--
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/