From: Frantisek Borsik <frantisek.borsik@gmail.com>
To: Cake List <cake@lists.bufferbloat.net>,
Dave Taht via Starlink <starlink@lists.bufferbloat.net>,
bloat <bloat@lists.bufferbloat.net>,
Jeremy Austin via Rpm <rpm@lists.bufferbloat.net>,
libreqos <libreqos@lists.bufferbloat.net>,
Make-Wifi-fast <make-wifi-fast@lists.bufferbloat.net>
Subject: [Make-wifi-fast] Bufferbloat info made it into the latest WLAN Pros Toolbox update!
Date: Fri, 9 Oct 2026 14:28:57 +0200 [thread overview]
Message-ID: <CAJUtOOg7Y1kgUh7T8_xOzqDHxJswuy_tUs1DWdv=cxo4pEx+Og@mail.gmail.com> (raw)
Hello to all,
Since I met Dave, I was hoping to get this done! WLAN Pros
<https://wlanprofessionals.com> is a community of WLAN, Wi-Fi engineers,
mostly working for big companies like Cisco, Juniper HPE, doing consulting
jobs in Wi-Fi or setting up big Wi-Fi networks at airports, hotels,
stadiums, cruise ships and other big venues.
I was always "harassing" them with BUFFERBLOAT when attending their WLPC
events - in fact, I'm attending the European one
<https://www.thewlpc.com/conferences/prg26> in Prague, starting tomorrow!
For years, it was:
"well, it's an ISP thing, we have nothing to do with it" or even worse
> "there is no such thing as bufferbloat!"
Now, I'm happy to report that their Educational Resources at
*https://toolbox.wlanpros.com/app/
<https://toolbox.wlanpros.com/app/>* were updated with:
*Bufferbloat: Latency Under Load* (it eventually leads to bufferbloat.net)
*LibreQoS Bufferbloat Test* (leads to https://test.libreqos.com)
*Waveform Bufferbloat Test *(leading to
https://www.waveform.com/tools/bufferbloat)
On top of this wonderful news, I'm happy to report that there will be also
one latency related talk at WLPC Prague 2026: *"Bandwidth Is a Red Herring:
Why Latency Breaks Collaboration in Wi-Fi Networks, Even with Wi-Fi 7"
<https://www.thewlpc.com/presentations/bandwidth-is-a-red-herring-why-latency-breaks-collaboration-in-wi-fi-networks-even-with-wi-fi-7-prg-26>*
yay!
All the best,
Frank
Frantisek (Frank) Borsik
*In loving memory of Dave Täht: *1965-2025
https://libreqos.io/2025/04/01/in-loving-memory-of-dave/
https://www.linkedin.com/in/frantisekborsik
Signal, Telegram, WhatsApp: +421919416714
iMessage, mobile: +420775230885
Skype: casioa5302ca
frantisek.borsik@gmail.com
reply other threads:[~2026-10-09 12:16 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='CAJUtOOg7Y1kgUh7T8_xOzqDHxJswuy_tUs1DWdv=cxo4pEx+Og@mail.gmail.com' \
--to=frantisek.borsik@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=cake@lists.bufferbloat.net \
--cc=libreqos@lists.bufferbloat.net \
--cc=make-wifi-fast@lists.bufferbloat.net \
--cc=rpm@lists.bufferbloat.net \
--cc=starlink@lists.bufferbloat.net \
/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