From: Dave Taht <dave.taht@gmail.com>
To: Aaron Wood <woody77@gmail.com>
Cc: make-wifi-fast@lists.bufferbloat.net,
"cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] [Make-wifi-fast] what is the right way to do, and rationale, for wifi channel scans?
Date: Sun, 15 May 2016 21:07:25 -0700 [thread overview]
Message-ID: <CAA93jw6NdXTf_aaGF2FekwFhoGBROty+GxuSD8dJRKGDjWwMbw@mail.gmail.com> (raw)
In-Reply-To: <CALQXh-MUPWZtM4ex=wTr2NVospHmR4bJoHVauvCm4wHr0CPauA@mail.gmail.com>
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
prev parent reply other threads:[~2016-05-16 4:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-14 0:19 [Cerowrt-devel] " Dave Taht
2016-05-14 3:19 ` [Cerowrt-devel] [Make-wifi-fast] " Aaron Wood
2016-05-16 4:07 ` Dave Taht [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAA93jw6NdXTf_aaGF2FekwFhoGBROty+GxuSD8dJRKGDjWwMbw@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=make-wifi-fast@lists.bufferbloat.net \
--cc=woody77@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox