From: Dave Taht <dave.taht@gmail.com>
To: "cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>,
bloat <bloat@lists.bufferbloat.net>
Subject: [Bloat] help wanted: maintaining and upgrading the yurtlab campus network
Date: Thu, 12 Mar 2015 15:15:07 -0700 [thread overview]
Message-ID: <CAA93jw4S47ko0TC_T0SqeKcig7JJMpp2Q1m_Xbe2J7du3ms7eA@mail.gmail.com> (raw)
I have deployed bits and pieces of the latest bits of the
make-wifi-fast work, and there are now 4 generations of AP and
directional APs on the los gatos, ca, campground I use for this stuff.
But: The latest deployment (running babels) seems to be messing up
the oldest generation of radios (running babel on zebra on linux
3.7.5!), and I really lack time to go around climbing ladders and
trees to update the remaining radios to the latest firmware - and
would prefer to be adding things and testing things like
minstrel-blues to that firmware - and maybe getting hnetd to finally
work - rather than fixing on the campus.
If anyone out there would like to - or knows anyone(s) that would like
to - help out spending a day or three every month in the coming months
in deploying new debloated wifi code and radios, (I can do this as a
paid thing, if needed, or get you a free yurt to stay in overnight), I
would really appreciate it.
I note that it is kind of an unusual place by many standards... but
was the only place in the world I found in 2 years of trying where I
could control all the wifi hardware and software, and few labs in the
universe come with a pool, and hottub.
http://www.cringely.com/2012/10/01/clothing-may-be-optional-but-bufferbloat-isnt/
--
Dave Täht
Let's make wifi fast, less jittery and reliable again!
https://plus.google.com/u/0/107942175615993706558/posts/TVX3o84jjmb
reply other threads:[~2015-03-12 22:15 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/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAA93jw4S47ko0TC_T0SqeKcig7JJMpp2Q1m_Xbe2J7du3ms7eA@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=cerowrt-devel@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