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: Windows password security audit tool. GUI, reports in PDF.

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

Date:	Mon, 6 Apr 2009 10:56:27 +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 Montag, 6. April 2009 schrieb Kalle Valo:
> 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.

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