From: David Lang <david@lang.hm>
To: dan <dandenson@gmail.com>
Cc: bob.mcmahon@umbernetworks.com, David Lang <david@lang.hm>,
Sebastian Moeller <moeller0@gmx.de>,
Frantisek Borsik <frantisek.borsik@gmail.com>,
codel@lists.bufferbloat.net,
Cake List <cake@lists.bufferbloat.net>,
Make-Wifi-fast <make-wifi-fast@lists.bufferbloat.net>,
bloat <bloat@lists.bufferbloat.net>, Jiml <jiml@quicksmart.com>,
William Fisher <zzyzxr99@gmail.com>, Thomas <thomas@monjalon.net>,
Tim Odriscoll <tim.odriscoll@intel.com>
Subject: [Make-wifi-fast] Re: [Bloat] Re: [Codel] [Rpm] Re: Re: [Cake] "Fi-Wi is a new forwarding plane for wireless" - Bob McMahon
Date: Sun, 7 Jun 2026 21:06:13 -0700 (MST) [thread overview]
Message-ID: <3s9r65o6-n27r-1802-9p33-406o6p1sr9np@ynat.uz> (raw)
In-Reply-To: <CAA_JP8WhXx0LYg2rZnYE-O0WMz13cKp7_vPLzCjMmysppYOUwg@mail.gmail.com>
dan wrote:
> Also, I don't operate in a niche space, my space is where every
> non-ethernet connected device operates. I do home, small business, large
> event centers, hotels, campgrounds, whole building solutions with hundreds
> of concurrent users. My wISP operation is the smallest part of the
> business, it just happens to have the cheapest clients so needs the
> cheapest solutions. I'm the anti-niche.
I run the wifi for the SCALE conference, we have north of 3000 users, with
hundreds in a single room. We also have zero control over the client devices.
We just reequipped outselves with openWRT one APs replacing the WNDR3800s we've
been using since 2011. The actual facility wifi is a shadow of what we deploy
> The issues described above are non-OFDMA experiences. OFDMA, at it's very
> core, is a bi-directional scheduler that is TDMA which erases the CSMA
> problems that cause retransmit 'storms'. A single OFDMA AP and virtually
> any number of OFDMA clients before you run out of CPU, will not collapse
> under saturation on OFDMA because they have strict timeslots.
>
> Worth noting, most decent WiFi7 access points with 6Ghz can strongly
> encourage OFDMA in clients if you setup a 6Ghz WPA3 only SSID. It's not a
> hard rule, but that combination generally strips out all non-OFDMA speaking
> devices.
so, no existing devices need to be supported?
> This comes down to quality drivers/software on the AP. WiFi8 is still a
> paper tiger practically speaking, but WiFi7 is out in full deployment and
> showing it's power. Noise at a client is reported to the AP, the AP won't
> schedule noisy RUs to that client, and vice versa. Multiple AP deployments
> see the other APs and channels and schedule RUs based on the amount of data
> to deliver. It'll use noisy RUs at lower modulations and clean ones at
> higher modulations and it does it bi-directionally so noise at the AP can
> be used to transmit to clients that don't see that noise and vice versa.
please point me on how to do this with openwrt
> We have been deploying a hybrid approach with APs operating with WPA3 and
> >= 80Mhz channels to encourage OFDMA and then separate APs on separate
> channels for older devices on WPA2.
and what do you do when those older devices are the vast majority?
David Lang
next prev parent reply other threads:[~2026-06-08 4:06 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-14 14:40 [Make-wifi-fast] "Fi-Wi is a new forwarding plane for wireless" - Bob McMahon Frantisek Borsik
2026-05-14 17:08 ` [Make-wifi-fast] Re: [Cake] " David Lang
2026-05-14 15:20 ` Frantisek Borsik
2026-05-14 19:38 ` bob.mcmahon
2026-05-14 19:55 ` David Lang
2026-05-15 11:11 ` bob.mcmahon
2026-05-15 13:57 ` David Lang
2026-05-15 14:18 ` David Lang
2026-05-15 15:17 ` bob.mcmahon
2026-05-19 13:52 ` [Make-wifi-fast] Re: [Bloat] " Livingood, Jason
2026-05-19 18:59 ` David Lang
2026-05-19 22:45 ` bob.mcmahon
2026-05-21 19:42 ` Frantisek Borsik
2026-05-21 20:02 ` dan
2026-05-22 16:36 ` [Make-wifi-fast] Re: [Rpm] " Robert McMahon
2026-05-23 2:18 ` dan
2026-05-23 16:36 ` bob.mcmahon
2026-05-23 22:12 ` dan
2026-05-24 20:06 ` Frantisek Borsik
2026-05-24 21:57 ` bob.mcmahon
2026-05-25 5:43 ` Frantisek Borsik
2026-05-25 6:58 ` [Make-wifi-fast] Re: [Codel] " Sebastian Moeller
2026-05-25 12:45 ` Frantisek Borsik
2026-05-25 13:36 ` [Make-wifi-fast] Re: [Codel] " Sebastian Moeller
2026-06-07 6:15 ` Frantisek Borsik
2026-06-07 9:03 ` Sebastian Moeller
2026-06-07 10:19 ` [Make-wifi-fast] Re: [Bloat] Re: [Codel] [Rpm] " David Lang
2026-06-07 18:10 ` bob.mcmahon
2026-06-07 18:30 ` dan
2026-06-07 19:10 ` bob.mcmahon
2026-06-08 0:29 ` dan
2026-06-08 2:55 ` bob.mcmahon
2026-06-08 4:06 ` David Lang [this message]
2026-06-08 6:26 ` [Make-wifi-fast] Re: [Bloat] " Sebastian Moeller
2026-06-08 3:59 ` [Make-wifi-fast] Re: [Bloat] " David Lang
2026-06-08 5:18 ` bob.mcmahon
2026-06-08 6:53 ` David Lang
2026-06-08 10:29 ` Frantisek Borsik
[not found] ` <e68abec2-6fd8-4fc4-ad26-5ca10859551c@rogers.com>
2026-06-09 3:40 ` [Make-wifi-fast] Re: [Codel] Re: [Bloat] " bob.mcmahon
2026-06-07 6:49 ` [Make-wifi-fast] Re: [Bloat] Re: [Codel] " David Lang
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=3s9r65o6-n27r-1802-9p33-406o6p1sr9np@ynat.uz \
--to=david@lang.hm \
--cc=bloat@lists.bufferbloat.net \
--cc=bob.mcmahon@umbernetworks.com \
--cc=cake@lists.bufferbloat.net \
--cc=codel@lists.bufferbloat.net \
--cc=dandenson@gmail.com \
--cc=frantisek.borsik@gmail.com \
--cc=jiml@quicksmart.com \
--cc=make-wifi-fast@lists.bufferbloat.net \
--cc=moeller0@gmx.de \
--cc=thomas@monjalon.net \
--cc=tim.odriscoll@intel.com \
--cc=zzyzxr99@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