* [Cerowrt-devel] what is the right way to do, and rationale, for wifi channel scans?
@ 2016-05-14 0:19 Dave Taht
2016-05-14 3:19 ` [Cerowrt-devel] [Make-wifi-fast] " Aaron Wood
0 siblings, 1 reply; 3+ messages in thread
From: Dave Taht @ 2016-05-14 0:19 UTC (permalink / raw)
To: make-wifi-fast, cerowrt-devel
I finally tracked down the source of many of the anomalies I'd
seen thus far... channel scans.
For the related rant, see:
http://blog.cerowrt.org/post/disabling_channel_scans/
Still haven't been able to kill it off entirely.
--
Dave Täht
Let's go make home routers and wifi faster! With better software!
http://blog.cerowrt.org
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [Cerowrt-devel] [Make-wifi-fast] what is the right way to do, and rationale, for wifi channel scans?
2016-05-14 0:19 [Cerowrt-devel] what is the right way to do, and rationale, for wifi channel scans? Dave Taht
@ 2016-05-14 3:19 ` Aaron Wood
2016-05-16 4:07 ` Dave Taht
0 siblings, 1 reply; 3+ messages in thread
From: Aaron Wood @ 2016-05-14 3:19 UTC (permalink / raw)
To: Dave Taht; +Cc: make-wifi-fast, cerowrt-devel
[-- Attachment #1: Type: text/plain, Size: 1451 bytes --]
wpa_supplicant? I've seen some atrocious behavior from wpa_supplicant in
the past (especially the closed-source versions from some chipset
companies).
One reason it's likely to be scanning is that it's looking for alternate
APs for the same SSID, which are "better".
I saw one implementation that would do an all-channel wildcard ssid scan
(elicting a response from every AP in range), and then would proceed to
scan every channel for just the ssid it was configured to use (hardcoded in
the wifi config). Why it was doing a broadcast for all APs, I don't know.
But once you get enough APs in a small enough area, that behavior causes a
broadcast storm as the probe responses (all at 1Mbps) flood the air, and
then cause other STAs to miss beacons, and re-scan, and it death-spirals
from there.
-Aaron
On Fri, May 13, 2016 at 5:19 PM, Dave Taht <dave.taht@gmail.com> wrote:
> I finally tracked down the source of many of the anomalies I'd
> seen thus far... channel scans.
>
> For the related rant, see:
>
> http://blog.cerowrt.org/post/disabling_channel_scans/
>
> Still haven't been able to kill it off entirely.
>
> --
> Dave Täht
> Let's go make home routers and wifi faster! With better software!
> http://blog.cerowrt.org
> _______________________________________________
> Make-wifi-fast mailing list
> Make-wifi-fast@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/make-wifi-fast
>
[-- Attachment #2: Type: text/html, Size: 2262 bytes --]
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [Cerowrt-devel] [Make-wifi-fast] what is the right way to do, and rationale, for wifi channel scans?
2016-05-14 3:19 ` [Cerowrt-devel] [Make-wifi-fast] " Aaron Wood
@ 2016-05-16 4:07 ` Dave Taht
0 siblings, 0 replies; 3+ messages in thread
From: Dave Taht @ 2016-05-16 4:07 UTC (permalink / raw)
To: Aaron Wood; +Cc: make-wifi-fast, cerowrt-devel
The discussion on the g+ thread for the channel scan issue got hot and
heavy, here:
https://plus.google.com/u/0/107942175615993706558/posts/WA915Pt4SRN
On Fri, May 13, 2016 at 8:19 PM, Aaron Wood <woody77@gmail.com> wrote:
> wpa_supplicant? I've seen some atrocious behavior from wpa_supplicant in
> the past (especially the closed-source versions from some chipset
> companies).
>
> One reason it's likely to be scanning is that it's looking for alternate APs
> for the same SSID, which are "better".
>
> I saw one implementation that would do an all-channel wildcard ssid scan
> (elicting a response from every AP in range), and then would proceed to scan
> every channel for just the ssid it was configured to use (hardcoded in the
> wifi config). Why it was doing a broadcast for all APs, I don't know. But
> once you get enough APs in a small enough area, that behavior causes a
> broadcast storm as the probe responses (all at 1Mbps) flood the air, and
> then cause other STAs to miss beacons, and re-scan, and it death-spirals
> from there.
>
> -Aaron
>
> On Fri, May 13, 2016 at 5:19 PM, Dave Taht <dave.taht@gmail.com> wrote:
>>
>> I finally tracked down the source of many of the anomalies I'd
>> seen thus far... channel scans.
>>
>> For the related rant, see:
>>
>> http://blog.cerowrt.org/post/disabling_channel_scans/
>>
>> Still haven't been able to kill it off entirely.
>>
>> --
>> Dave Täht
>> Let's go make home routers and wifi faster! With better software!
>> http://blog.cerowrt.org
>> _______________________________________________
>> Make-wifi-fast mailing list
>> Make-wifi-fast@lists.bufferbloat.net
>> https://lists.bufferbloat.net/listinfo/make-wifi-fast
>
>
--
Dave Täht
Let's go make home routers and wifi faster! With better software!
http://blog.cerowrt.org
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2016-05-16 4:07 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2016-05-14 0:19 [Cerowrt-devel] what is the right way to do, and rationale, for wifi channel scans? Dave Taht
2016-05-14 3:19 ` [Cerowrt-devel] [Make-wifi-fast] " Aaron Wood
2016-05-16 4:07 ` Dave Taht
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox