Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Joe Touch <touch@isi.edu>
To: Matt Taggart <matt@lackof.org>, 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: Wed, 08 Jul 2015 11:37:11 -0700	[thread overview]
Message-ID: <559D6DD7.9020806@isi.edu> (raw)
In-Reply-To: <20150707181911.7759D208@taggart.lackof.org>

Hi, Matt,

On 7/7/2015 11:19 AM, Matt Taggart wrote:...
> This message made me realize I hadn't posted the CC+SQM HOWTO I
> wrote, maybe it will be useful,
>
> https://we.riseup.net/lackof/openwrt

FWIW, this is a big step in the direction I was suggesting.

Thanks!

The other step, IMO, would be two flags in the OpenWRT list of hardware:

	- a flag/color that indicates that the most recent hardware rev
	supports BB

	- a different flag/color that indicates that the most recent
	hardware rev supports CC

The current list is a confusing mix of information about very old,
sometimes EOL (end-of-life) equipment.

To those who have invited me to participate in the research, thanks, but
sometimes I just want to *use* a solution. I'm OK with a buggy,
partially unstable one, but I don't always want to dive into
developer-mode for every system I'd like to test out.

Joe






  parent reply	other threads:[~2015-07-08 18:37 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
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 [this message]
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=559D6DD7.9020806@isi.edu \
    --to=touch@isi.edu \
    --cc=bloat@lists.bufferbloat.net \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=matt@lackof.org \
    --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