Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Joe Touch <touch@isi.edu>
To: bloat@lists.bufferbloat.net, cerowrt-devel@lists.bufferbloat.net
Cc: touch@isi.edu
Subject: [Cerowrt-devel] failing to find the "declared victory" in a current wifi router
Date: Mon, 06 Jul 2015 18:02:11 -0700	[thread overview]
Message-ID: <559B2513.3020909@isi.edu> (raw)

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



	

             reply	other threads:[~2015-07-07  1:02 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-07  1:02 Joe Touch [this message]
2015-07-07  2:23 ` Rich Brown
2015-07-07  4:22   ` Joe Touch
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=559B2513.3020909@isi.edu \
    --to=touch@isi.edu \
    --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