From: Joe Touch <touch@isi.edu>
To: Rich Brown <richb.hanover@gmail.com>
Cc: bloat@lists.bufferbloat.net, cerowrt-devel@lists.bufferbloat.net,
touch@isi.edu
Subject: Re: [Cerowrt-devel] failing to find the "declared victory" in a current wifi router
Date: Mon, 6 Jul 2015 21:22:00 -0700 [thread overview]
Message-ID: <559B53E8.90201@isi.edu> (raw)
In-Reply-To: <ACB21509-F29C-4004-8ACE-D5BEC822DA8A@gmail.com>
Hi, Rich,
On 7/6/2015 7:23 PM, Rich Brown wrote:
> Hi Joe,
>
> The OpenWrt firmware project is a "some assembly required" affair.
That might be less daunting if there were assembly instructions. I.e.,
I'm suggesting that the instructions need revision. Work there could
have a significant payoff in a larger test community (I'm not exactly a
hardware noob, but I found it annoyingly obfuscated).
> Although it's not always easy to find, the site has a number of resources:
> - Buyer's Guide at http://wiki.openwrt.org/toh/buyerguide
That is useful for picking from among the currently supported versions,
but perhaps it'd be useful to take a colleague with you to a store and
see how helpful that all is. It's nearly impossible to find any of the
devices in the list or to verify whether a particular device in a box
has the required version of motherboard and firmware needed.
> - The specific guidance to search Amazon for "OpenWrt" - see: http://amzn.to/1mONYr0
That turns up quite a bit of devices that aren't supported, FWIW.
> - The forum at: https://forum.openwrt.org/viewforum.php?id=10 mentions lots of routers
Indeed; more isn't better.
> As for specific routers:
> - The WNDR3800 remains our gold standard for CeroWrt builds. It'll
> do SQM up to ~30 mbps, then the CPU runs out of gas.
May I also suggest moving to another standard that hasn't been
explicitly "end-of-life'd" by the manufacturer.
> - Check the OpenWrt Table of Hardware (ToH) to see what other routers
> support the current stable 14.07/Barrier Breaker (BB) builds.
Sure - I spent several days in Target, Best Buy, and Fry's trying to
decipher whether particular products were supported - again often
difficult without UPC numbers (boxes don't always indicate version)
> - Many people on this list have good luck with the TP-Link Archer C7
> v2. I believe it'll route at cable speeds. I'm using it very
> successfully with OpenWrt BB release on a 7 mbps DSL line.
Here's a good example of how useful the information on the OpenWRT
website can be. Everyone seems to refer to this as "Archer C7", everyone
except the TP-Link website. Their search finds no products matching that
description, and the WIFI routers there are listed with other codes,
e.g.:TL-WDR7500 - except you won't find that number on the hardware page
-- you have to click through to the page for that device.
For that device, like for many, the most recent version (i.e., the one
more likely to arrive on a blind web order, or on most store shelves) is
not yet supported.
> - If you have been following the Linksys WRT1900AC and WRT1200AC
> thread at
> https://forum.openwrt.org/viewtopic.php?id=50173&action=newyou'll see
> that the CC builds are sorta, kinda working. There are a lot of moving
> pieces still, and despite the CC RC2 status, stable builds only come
> out a few days apart. I would stay away from it if you're not willing
> to participate in a science experiment.
Well, the 23-Apr-2015 build by Kaloz works fine - except that the SQM
package fails to install.
What I'm baffled by here is that the main trunk builds leave LUCI out;
that's seems
quite short-sighted, IMO.
> There is a team working to improve the OpenWrt site, but our work
> has not yet been "blessed" by the the admin's who maintain the core pages of
> the site.
And I appreciate and understand that. The CeroWRT site could similarly
use an update.
I.e., there's ample opportunity here to build a larger community with a
few simple steps:
- refer to routers by the manufacturer's designation
- create builds with both LUCI and (if possible) SQM
- make a short-list of a few currently available routers
for which an integrated build exists *for the most recent
motherboard version*
All of this could be done on the CeroWRT site until it can be put on
OpenWRT.
These are fairly direct ways to lower the bar, which seems unnecessarily
high here.
Joe
> Best,
>
> Rich Brown
>
> On Jul 6, 2015, at 9:02 PM, Joe Touch <touch@isi.edu> wrote:
>
>> Hi, all,
>>
>> I'm posting because of my recent frustration with the claim that
>> bufferbloat solutions have been "pushed up into the OpenWRT and
>> commercial routers.
>>
>> I spent the bulk of last weekend trying to find a COTS WIFI router that
>> supported OpenWRT with bufferbloat (SQM) extensions.
>>
>> I tried a Linksys WRT1200AC, and here's what I found:
>>
>> - Kaloz's 23-Apr-2015 build installs fine and comes up
>> with a web server (LUCI), but does NOT include SQM
>>
>> - trying to install the SQM packages fails
>> due to a kernel version incompatibility
>> (for a 23-Apr-2015 build?!)
>>
>> - CC-rc2 doesn't have a WRT1200AC build
>> presumably I should have used mvebu-armada-385-linksys-caiman,
>> but it's not at all clear
>>
>> - and I'd have to install LUCI and/or reinstall
>> factory firmware from the command line, and none
>> of that is all that clear, esp. a recovery route
>> that doesn't involve voiding warranty to wire in
>> a serial port
>>
>> Given the "declared victory" (http://www.bufferbloat.net/news/53),
>> perhaps someone one one of these lists can explain why there's no clear
>> information on a current device that supports a current build that
>> actually supports these fixes?
>>
>> I.e., if you were trying to make this obscure, you're doing a very good job.
>>
>> FWIW.
>>
>> Joe
>>
>>
>>
>>
>> _______________________________________________
>> Cerowrt-devel mailing list
>> Cerowrt-devel@lists.bufferbloat.net
>> https://lists.bufferbloat.net/listinfo/cerowrt-devel
>
next prev parent reply other threads:[~2015-07-07 4:22 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-07 1:02 Joe Touch
2015-07-07 2:23 ` Rich Brown
2015-07-07 4:22 ` Joe Touch [this message]
2015-07-07 7:20 ` Sebastian Moeller
2015-07-07 12:03 ` [Cerowrt-devel] [Bloat] " Kevin Darbyshire-Bryant
2015-07-07 14:07 ` [Cerowrt-devel] " Rich Brown
2015-07-07 18:19 ` Matt Taggart
2015-07-08 1:54 ` Rich Brown
2015-07-08 18:37 ` Joe Touch
2015-07-08 20:15 ` Sebastian Moeller
2015-07-08 20:28 ` Joe Touch
2015-07-08 22:16 ` Sebastian Moeller
2015-07-09 1:34 ` Rich Brown
2015-07-08 0:48 ` Jim Reisert AD1C
2015-07-08 2:47 ` Dave Taht
2015-07-07 6:16 ` Mikael Abrahamsson
2015-07-07 18:34 ` Joe Touch
2015-07-10 7:03 ` Mikael Abrahamsson
2015-07-10 7:22 ` Joe Touch
2015-07-10 7:48 ` Mikael Abrahamsson
2015-07-10 8:01 ` Sebastian Moeller
2015-07-10 16:57 ` Joe Touch
2015-07-07 15:40 ` 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/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=559B53E8.90201@isi.edu \
--to=touch@isi.edu \
--cc=bloat@lists.bufferbloat.net \
--cc=cerowrt-devel@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