From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-iy0-f171.google.com (mail-iy0-f171.google.com [209.85.210.171]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority" (verified OK)) by huchra.bufferbloat.net (Postfix) with ESMTPS id 5AC97200993 for ; Sun, 4 Dec 2011 11:16:19 -0800 (PST) Received: by iaen33 with SMTP id n33so10676818iae.16 for ; Sun, 04 Dec 2011 11:16:18 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=p3QCFHVF1vtIMuBIDI/cpqzTMZUbm37HZbxbwTiLOWA=; b=msmOSrzkTxZBTo4JOAG8mI4N2M/Z4Mz92AdHU61X9kaigVI+wlWE9enLVnMWCXTd1I aO+mK978Uo2c9lGpkheuAUHMCfCbJWaH7J1yNwSWZ5X7blNfvAzPa+Hcy2HjGnyBMI2k rJT6Oe0IZLjfJhJZ/C/VmvcHgVwBJO+DSW0IA= MIME-Version: 1.0 Received: by 10.50.88.135 with SMTP id bg7mr7849886igb.11.1323026178513; Sun, 04 Dec 2011 11:16:18 -0800 (PST) Received: by 10.231.204.83 with HTTP; Sun, 4 Dec 2011 11:16:18 -0800 (PST) Date: Sun, 4 Dec 2011 20:16:18 +0100 Message-ID: From: Dave Taht To: cerowrt-devel@lists.bufferbloat.net Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Subject: [Cerowrt-devel] Where we're winning 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: Sun, 04 Dec 2011 19:16:19 -0000 All: I am incredibly open to suggestions as to how to make cerowrt less of a success disaster. First up on my list was to try and communicate better about the state of the project. This includes things like activating the cerowrt-commits mailing list, and starting this one. Where we are winning: 1) Stability - no final release candidate has EVER crashed. So far as I know none of the smoketests later than say, a '4', has ever crashed, either. This is an amazing tribute to the linux and openwrt development process, and (in some small part) the degree of testing that I do. 2) Press. With cringley and lwn.net and slashdot, we have got nothing but rave reviews and encouragement for what we're trying to do. 3) We have incredible amounts of verbal support from heavyweights in the industry, starting wtih jim gettys of course. The expressions of support and interest from tons of people that I admire deeply keep me going... 4) Openwrt itself has improved dramatically - 99.9% of this would have happened without our feedback, frankly - but it has been amazing to watch the quality of its tools, device drivers, kernel, and packages improve on what seems to be a daily basis. Recently, I took a look at the gui from back in june to where it is now, and *wow*. 5) As a research tool, Cerowrt has been utterly invaluable (to me at least) for understanding the current (mis)behavior of wireless, the interrelationships of the stack and drivers and packet scheduler, and for getting a good grip on what is actually possible to achieve on a modern consumer-grade device. At this point I'm utterly certain that A) it is possible to implement very complex queue management and thus, begin to beat bufferbloat at the network edge, where it bothers people the most. B) it is possible to improve wired and wireless behavior enormously C) it is possible to implement advanced functionality like dnssec and windows services D) it is possible to get ipv6 working, routing working, local web and DNS services working, and a whole lot more In summary, it IS possible to build a device far superior to anything shipped today, one that can set an example for the rest of the industry, save everyone time, and hassle, and do it for very low cost, AND consisting almost purely of software that can be applied to any hardware with the same capabilities, thus introducing competition to drive the costs down while holding the desirable feature set to a whole new standard. and we didn't know any of that when we started. I am very encouraged by the progress we've made towards understanding and defeating bufferbloat over the past year. However, the last several months of this project have had some problems that have really been holding back progress, and I'll get to talking about the negatives in a day or two. In the meantime, if you have any thoughts towards where we can go with this project in the coming year that will have the most impact on improving the state of things at the Internet edge, please share them here. "Ask not what cerowrt can do for you, but what you can do for cerowrt!" Where else are we winning? What else can do better? --=20 Dave T=E4ht SKYPE: davetaht US Tel: 1-239-829-5608 FR Tel: 0638645374 http://www.bufferbloat.net