From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mout.gmx.net (mout.gmx.net [212.227.17.21]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-1" (verified OK)) by huchra.bufferbloat.net (Postfix) with ESMTPS id E228021FCF8; Wed, 8 Jul 2015 13:15:39 -0700 (PDT) Received: from hms-beagle-7.home.lan ([217.237.70.193]) by mail.gmx.com (mrgmx103) with ESMTPSA (Nemesis) id 0MRXVc-1ZbEyG0Mw4-00ShWd; Wed, 08 Jul 2015 22:15:12 +0200 Content-Type: text/plain; charset=windows-1252 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Sebastian Moeller In-Reply-To: <559D6DD7.9020806@isi.edu> Date: Wed, 8 Jul 2015 22:15:06 +0200 Content-Transfer-Encoding: quoted-printable Message-Id: <8F877E8A-6DD2-4318-B690-DF7395394037@gmx.de> References: <559B2513.3020909@isi.edu> <559B53E8.90201@isi.edu> <8CBE744B-CE0D-4C44-A4B1-C7FB27403E1D@gmail.com> <20150707181911.7759D208@taggart.lackof.org> <559D6DD7.9020806@isi.edu> To: Joe Touch X-Mailer: Apple Mail (2.1878.6) X-Provags-ID: V03:K0:QhKNDx+G5diUedsDYXC0UpH7V+bSooIxqLwq7IxYSS2JS0f2lEh 4nRNpWTUvpI8ou2Df1oMap01QVPLDDMUQyejYu3gyVJsiu84xNZdQZX6o24yk+BENgKuRmr zzwv+T+C7V032yIxIpypYVot49Z3H2hUFepxtgy5GoVafdsdlS1YJvqhCFt/OPV5f/XBTp0 BK7But+2FYIvmLRRey9cQ== X-UI-Out-Filterresults: notjunk:1;V01:K0:UzpgUQHR7Kc=:MBeBHSw/lByR/sw05TLn13 w59vibyVcCIQcdZGnfmwArX/VHZdNvomya219+hsZLyH25tHl2VLOerjWC/zYfowgohHz78Pw Oop8wyWofLEt5sTJG3f9gE3S1KPD+S7nDVWUUaId1F+5k8sJdB9jyA6V/E5rV4AGkG9Hoyzxz 6orDjdd5B4vkVZSgutGXZDO9u7OSwKlVzQjl9CZ0l9sY++XhKrDKm4K8fwCe0mVV9Wogr7uKW K4romWAFFr7B5ZOe/RUOkBpf8zO4Vg0cEtyKMvnCb8uykIz/Hci9OuV4ys4y7e8kXHEPCx53F Z3NBOMGjmoQ+H6unpFknCNTqYBKtemzYv3dr5nQx/paVlAY5XjWG2QgYnbaQbH8YaQMa0vwxf C6vANoB61fWk7R0qV7N/mi9KTRMNQrKRNcE4Soxodrj1XALtqMFju+nfMHxwtv+NN8HW5qgFp RpIe1eEJ7E6ziXTC33TOEUp5CXZESseMB/JSy6MOJqUFJanE3X94cqT1laIG0jwr1GEZCLx46 h2nsLscs39Un1sqdYnEw8UDB8i9LHoJzLZbFvxqGNX9SPZGDapzhsvl101GghL7xE2Pt/JtVu m8U5/b/oLI7fCcxZlCx1blNclaIRXduXLLHMrNx+Lqkuwvi2fd3MGnk6qLZ/vP4D7vfeV3q3w 4/RPYzGkqhyv17OsYsZR5SD/3AD8ONRftp39FiZNS6eqYXvbx/fn9nfgefJ6GUoNUljg= 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 X-BeenThere: cerowrt-devel@lists.bufferbloat.net X-Mailman-Version: 2.1.13 Precedence: list List-Id: Development issues regarding the cerowrt test router project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Jul 2015 20:16:08 -0000 Hi Joe, On Jul 8, 2015, at 20:37 , Joe Touch wrote: > Hi, Matt, >=20 > 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, >>=20 >> https://we.riseup.net/lackof/openwrt >=20 > FWIW, this is a big step in the direction I was suggesting. >=20 > Thanks! >=20 > The other step, IMO, would be two flags in the OpenWRT list of = hardware: >=20 > - a flag/color that indicates that the most recent hardware rev > supports BB >=20 > - 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.=20 Granted, status are not filled for all routers and sometimes with the = unfortunate label =93trunk=94 without stating a date or release number, = but these seem to be the minority. Versionseems to be in worse shape = with lots of =93-=93 and =93?=94.=20 By the way, you keep repeating the phrase =93most recent = hardware rev.=94 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.=20 I would love to learn if you have a better way of collecting = that information preferably in an automated fashion? >=20 > 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 =93second = life=94 as openwrt routers seems like a good idea to me. >=20 > 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. >=20 > Joe >=20 >=20 >=20 >=20 >=20 > _______________________________________________ > Cerowrt-devel mailing list > Cerowrt-devel@lists.bufferbloat.net > https://lists.bufferbloat.net/listinfo/cerowrt-devel