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]

Message-ID: <87y6uexie4.fsf@litku.valot.fi>
Date:	Mon, 06 Apr 2009 12:04:35 +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:

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

Yeah, but it's ugly. And if the scan takes too long, for example over
four seconds, mlme would disconnect from AP. That's not good.

But I haven't looked at this in detail yet, just speculating here :)

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