From: David Lang <david@lang.hm>
To: Rich Brown <richb.hanover@gmail.com>
Cc: bloat@lists.bufferbloat.net
Subject: Re: [Bloat] fixing bufferbloat in 2017
Date: Wed, 23 Nov 2016 10:46:41 -0800 (PST) [thread overview]
Message-ID: <nycvar.QRO.7.75.62.1611231040050.9765@qynat-yncgbc> (raw)
In-Reply-To: <4BD9ED0C-9FF6-4A12-9F8C-76791BFA38E8@gmail.com>
On Wed, 23 Nov 2016, Rich Brown wrote:
> I feel particularly acutely the fact that we don't have a good "simple to
> deliver" solution today for the curious (not deeply commited) person. I was
> trying to help a friend with a TP-Link Archer C7, but was stymied because I
> can't simply install OpenWrt CC because of their "FCC fix".
The FCC has issued an order that TP-Link open their devices to being flashed by
third pary firmware. We just need to wait for this to trickle back down to the
supply chain. It may be that they have a new firmware that you can update to
that will then let you install OpenWRT
> Besides, OpenWrt CC is now eight months old: although it's stable, it probably
> doesn't have the latest bufferbloat/make-wifi-fast fixes. The DD development
> and release process is uncertain. DD-Wrt is of unknown quality (does it
> include fq_codel? make-wifi-fast? will it ever?), with a really ugly and not
> terribly-welcoming forum. I have great hopes for LEDE, but it is still
> sprinting toward its first stable release, so we can't count on it today.
CC doesn't have the latest, but it does have fq_codel, so it's a huge step up
from the factory firmware.
Most of the OpenWRT developers left to fork the project and now have the LEDE
project. Most of the development and testing of new stuff is happening there.
Neither project has made a release since the split, but LEDE is working on
setting up the infrastructure to do a release.
In the meantime, you can install the nightly builds or compile your own.
> So we are stuck in the short term with a "lack of a product". I have faith
> that it will happen, but we need to build our plan around its arrival date.
Part of the question boils down to what you define as the "product" that you are
waiting for.
OpenWRT/LEDE are very unlikly to have rapid releases, if they do one a year they
will be doing much better than they have in the past.
Do you need a device that ships with the fixes in it from the factory?
Do you need a stable release of OpenWRT/LEDE?
Do you need the fixes in the master git repository for OpenWRT/LEDE?
Do you need the latest and greatest fixes?
the last one in incompatible with the earlier ones :-)
David Lang
next prev parent reply other threads:[~2016-11-23 18:46 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.447.1479909940.3555.bloat@lists.bufferbloat.net>
2016-11-23 18:16 ` Rich Brown
2016-11-23 18:46 ` David Lang [this message]
2016-11-23 18:58 ` Jonathan Morton
2016-11-23 19:15 ` David Lang
2016-11-23 20:37 ` Toke Høiland-Jørgensen
[not found] <mailman.454.1479929363.3555.bloat@lists.bufferbloat.net>
2016-11-26 15:33 ` [Bloat] Fixing " Rich Brown
2016-11-27 1:53 ` Aaron Wood
2016-11-27 6:10 ` Mikael Abrahamsson
2016-11-27 21:24 ` Dave Taht
2016-11-28 2:11 ` Kathleen Nichols
2016-11-28 2:16 ` Jim Gettys
2016-11-28 6:00 ` Jan Ceuleers
2016-11-28 12:48 ` David Collier-Brown
2016-11-28 15:12 ` Dave Taht
2016-11-28 15:23 ` Wesley Eddy
2016-11-28 15:35 ` Dave Taht
2016-11-28 16:58 ` Stephen Hemminger
2016-11-28 17:07 ` Dave Taht
2016-11-28 19:02 ` Jonathan Morton
2016-11-28 17:52 ` Kathleen Nichols
2016-11-28 15:14 ` Pedro Tumusok
2016-11-28 15:23 ` Dave Taht
2016-11-28 15:10 ` Dave Taht
2016-11-28 2:47 ` David Lang
2016-11-22 15:32 [Bloat] fixing " Dave Taht
2016-11-22 16:19 ` Jan Ceuleers
2016-11-22 16:25 ` Dave Taht
2016-11-22 16:38 ` Jim Gettys
2016-11-23 8:28 ` Mikael Abrahamsson
2016-11-23 11:04 ` Jonathan Morton
2016-11-23 11:59 ` Kelvin Edmison
2016-11-23 13:31 ` Pedro Tumusok
2016-11-23 14:05 ` Mário Sérgio Fujikawa Ferreira
2016-11-23 17:20 ` Mikael Abrahamsson
2016-11-23 17:27 ` Benjamin Cronce
2016-11-23 17:31 ` Mikael Abrahamsson
2016-11-23 17:40 ` Sebastian Moeller
2016-11-23 17:50 ` Noah Causin
2016-11-23 17:56 ` David Lang
2016-11-23 18:05 ` Benjamin Cronce
2016-11-23 18:38 ` David Lang
2016-11-23 19:29 ` Benjamin Cronce
2016-11-23 19:42 ` David Lang
2016-11-23 20:20 ` Dave Taht
2016-11-23 17:54 ` David Lang
2016-11-23 18:09 ` Mikael Abrahamsson
2016-11-23 18:18 ` Sebastian Moeller
2016-11-23 18:24 ` Dave Taht
2016-11-23 20:39 ` Toke Høiland-Jørgensen
2016-11-23 19:13 ` David Lang
2016-11-23 18:17 ` Dave Taht
2016-11-23 15:32 ` Pedretti Fabio
2016-11-23 19:29 ` Stephen Hemminger
2016-11-23 19:22 ` Dave Taht
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=nycvar.QRO.7.75.62.1611231040050.9765@qynat-yncgbc \
--to=david@lang.hm \
--cc=bloat@lists.bufferbloat.net \
--cc=richb.hanover@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