Lets make wifi fast again!
 help / color / mirror / Atom feed
From: David Lang <david@lang.hm>
To: Sebastian Moeller <moeller0@gmx.de>
Cc: Frantisek Borsik <frantisek.borsik@gmail.com>,
	codel@lists.bufferbloat.net, bob.mcmahon@umbernetworks.com,
	dan <dandenson@gmail.com>, Cake List <cake@lists.bufferbloat.net>,
	Make-Wifi-fast <make-wifi-fast@lists.bufferbloat.net>,
	bloat <bloat@lists.bufferbloat.net>
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 03:19:30 -0700 (MST)	[thread overview]
Message-ID: <8qr7qons-5sp9-o30o-49qr-02p67prss6rr@ynat.uz> (raw)
In-Reply-To: <52CE3DA7-EC5A-4FF8-A88E-26A7A6661983@gmx.de>

Sebastian Moeller via Bloat wrote:

> the point is current WiFi sucks under staturating loads, period.

This is correct and I doubt that it can be fixed.

Wifi was designed for a different era. I remember renting a pcmcia card for a 
conference with a $800 deposit because that was the purchase price for the card. 
Wifi was expected to be something rare and the protocol reflects that.

In an environment where there are only a few statinos, the retry and then retry 
at a slower data rate do work, and the slower data rate is more likely to be 
deciphered if the problem is a weak signal or high noise level

but today you only see such environments in a lab, on a farm, or possibly a 
large estate.

In the more common conditions today where airtime is the limiting factor and 
hidden transmitters (where the receiving station can hear two stations that 
can't hear each other) are the rule rather than the exception, having to 
retransmit everything when you are stepped on because the receiving station 
can't validate anything it heard if it doesn't hear the complete transmission 
wastes airtime, and transmitting at a lower data rate will make it more likely 
that you get stepped on, not more likely that you will get your message through

this leads to performance falling off a cliff when the available airtime fills 
up rather than graceful degredation

If the next wifi standard could have checksums at various places during the 
broadcast, it would be possible for part of the data to get through, and get 
acked and normal tcp retries to get the rest transmitted later. Combine this 
with NOT slowing down when you have trouble getting through would help greatly 
reduce this cliff (as long as your signal strength is high enough, acks from the 
AP would have to report how they hear you)

but without coordination between the stations that can't hear each other, you 
can't fix the hidden transmitter problem.

you can somewhat mitigate it if you have lots of APs and you set the APs to only 
pay attemtion to signals that are pretty strong. If you tune this just exactly 
right you can make it so the stations at opposite sides of you can hear each 
other to avoid collisions. This tuning would be very difficult to get right.

the only theoretical answer to the problem is to have the AP manage transmission 
slots, but that doesn't work very well in practice (the management eats so much 
airtime that the 'dumber' design wins with higher throughput, up until total 
collapse.



getting cake to be able to adjust to changing bandwidth would help avoid driving 
the network to saturation, but being able to deploy more APs to use more 
channels at lower power is adding additional airtime, pushing the limit futher 
out. It's not the best solution, it just works in practice (most of the time)

David Lang

  reply	other threads:[~2026-06-07 10:19 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                                               ` David Lang [this message]
2026-06-07 18:10                                                 ` [Make-wifi-fast] Re: [Bloat] Re: [Codel] [Rpm] " 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
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=8qr7qons-5sp9-o30o-49qr-02p67prss6rr@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=make-wifi-fast@lists.bufferbloat.net \
    --cc=moeller0@gmx.de \
    /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