Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Sebastian Moeller <moeller0@gmx.de>
To: Joe Touch <touch@isi.edu>
Cc: cerowrt-devel@lists.bufferbloat.net, bloat@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] failing to find the "declared victory" in a current wifi router
Date: Wed, 8 Jul 2015 22:15:06 +0200	[thread overview]
Message-ID: <8F877E8A-6DD2-4318-B690-DF7395394037@gmx.de> (raw)
In-Reply-To: <559D6DD7.9020806@isi.edu>

Hi Joe,

On Jul 8, 2015, at 20:37 , Joe Touch <touch@isi.edu> wrote:

> 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

	If you look at http://wiki.openwrt.org/toh/start you should have noticed two columns: version and status:
status was/is supposed from which version openwrt supports that specific router
version is supposed to tell which versions of said router actually fall under the supported status. 
Granted, status are not filled for all routers and sometimes with the unfortunate label “trunk” without stating a date or release number, but these seem to be the minority. Versionseems to be in worse shape with lots of “-“ and “?”. 
	By the way, you keep repeating the phrase “most recent hardware rev.” as if there was a common repository somewhere on the web from which to deduce what the most recent incarnation of each specific router name/type is; as it stands this information is filled in by volunteers, based on what version they got from a store/vendor/OEM and their installation testing/development. 
	I would love to learn if you have a better way of collecting that information preferably in an automated fashion?

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

        What is bad about keeping information? Just because a device is EOL by its manufacturer/vendor does not necessarily mean it is completely out of the retail channel/ second hand retail/sharing channel, so keeping information how to give such devices a “second life” as openwrt routers seems like a good idea to me.

> 
> To those who have invited me to participate in the research, thanks, but
> sometimes I just want to *use* a solution.

	Fair enough. I noticed I might seem a bit grumpy, not sure why but I would blame it on the weird weather here...

Best Regards
	Sebastian


> 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
> 
> 
> 
> 
> 
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel


  reply	other threads:[~2015-07-08 20:15 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
2015-07-08 20:15           ` Sebastian Moeller [this message]
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=8F877E8A-6DD2-4318-B690-DF7395394037@gmx.de \
    --to=moeller0@gmx.de \
    --cc=bloat@lists.bufferbloat.net \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=touch@isi.edu \
    /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