From: Dave Taht <dave.taht@gmail.com>
To: Make-Wifi-fast <make-wifi-fast@lists.bufferbloat.net>,
Cake List <cake@lists.bufferbloat.net>,
Rpm <rpm@lists.bufferbloat.net>
Subject: [Make-wifi-fast] Oct 2-6 wispa-apalooza conference in las vegas
Date: Tue, 20 Sep 2022 03:30:53 -0700 [thread overview]
Message-ID: <CAA93jw7mEVsgZmLdbqdzpm-18xm0WwX+gPJN370i7P0e0zEEww@mail.gmail.com> (raw)
I am speaking (talking about rfc7567's demand for fq+aqm on
everything), moderating a panel, and haunting a booth or two, guitar
in hand, at this WISP-oriented conference. A lot of things I(we've)
been working on this past year are coming to a head here, everything
from coping with the broadband maps debacle, the FCC not taking ookla
or samknows latency under load data, and the $60B NTIA broadband fund
programs still not funding ipv6, to the new openwrt and mikrotik
releases, to seeing cake and fq_codel enter more ISP middleboxes via
preseem and libreqos. Anyone here going?
https://wispaevents.org/booth-map/
Rumor has it that at least one new PtMP WISP radio will have fq_codel
in it, in addition to the mikrotik, openwifi and ISPAPP stuff. There
are a bunch of other products there, when I went last time, that were
running "our stuff" (most didn't know it). It's not a hugely technical
conference, but in particular if you want to learn more than you ever
wanted to know about the current state of outdoor fixed wireless,
fiber, and legal stuff, very worth doing. And the food is good.
I like WISP folk a lot, the kind of ornery old-fashioned american
small businessfolk that get s**t done. In my case I'm going to try and
drum up a bit of business for "network tuneups" and custom openwrt
builds, in addition to getting a feel for the state of things in DC.
Bringing funnels.
--
FQ World Domination pending: https://blog.cerowrt.org/post/state_of_fq_codel/
Dave Täht CEO, TekLibre, LLC
reply other threads:[~2022-09-20 10:31 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=CAA93jw7mEVsgZmLdbqdzpm-18xm0WwX+gPJN370i7P0e0zEEww@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=cake@lists.bufferbloat.net \
--cc=make-wifi-fast@lists.bufferbloat.net \
--cc=rpm@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