From: Aaron Wood <woody77@gmail.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: make-wifi-fast@lists.bufferbloat.net, Felix Fietkau <nbd@nbd.name>
Subject: Re: [Make-wifi-fast] station measurements in a stadium
Date: Sun, 6 Sep 2015 13:49:20 -0700 [thread overview]
Message-ID: <CALQXh-NGUZJ7B7p0ewUBM423SRFcPKXFzcUs1ntmzX2rvgYQ=A@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw5Scb3Px-2=9sgvAicxshv8S9-wdAyVhpkJucb59cz4sw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 859 bytes --]
I have some traces from a lab environment where probes from mobile stations
caused congestion collapse. The active broadcast probes, on all channels,
in an AP-rich environment caused the probe responses to use up all the
tx-ops. It's ugly, ugly, ugly.
Unfortunately (or maybe fortunately?), the stations are all old
kernels+drivers (Froyo Android, some kernel 2.6 devices, etc). But the
problem is the basic operation of wifi APs.
(I wish I could share the raw pcaps, but I can't).
-Aaron
On Sun, Sep 6, 2015 at 1:15 PM, Dave Taht <dave.taht@gmail.com> wrote:
> --
> Dave Täht
> endo is a terrible disease: http://www.gofundme.com/SummerVsEndo
>
> _______________________________________________
> 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: 1534 bytes --]
prev parent reply other threads:[~2015-09-06 20:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-06 20:15 Dave Taht
2015-09-06 20:49 ` Aaron Wood [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/make-wifi-fast.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CALQXh-NGUZJ7B7p0ewUBM423SRFcPKXFzcUs1ntmzX2rvgYQ=A@mail.gmail.com' \
--to=woody77@gmail.com \
--cc=dave.taht@gmail.com \
--cc=make-wifi-fast@lists.bufferbloat.net \
--cc=nbd@nbd.name \
/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