From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wi0-x22b.google.com (mail-wi0-x22b.google.com [IPv6:2a00:1450:400c:c05::22b]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by huchra.bufferbloat.net (Postfix) with ESMTPS id EB3F321F151 for ; Tue, 14 Jan 2014 07:30:15 -0800 (PST) Received: by mail-wi0-f171.google.com with SMTP id cc10so2730428wib.4 for ; Tue, 14 Jan 2014 07:30:13 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=xBiZ9/WQh9ywcfSTsC0xH5i1Q1sLrVMvZQ7wytBFkjc=; b=UUcozGnx+99R/R9WfkyrqP08Cx7jtqe3l9NdzxFe8eDwe4agh2qM7nkeSu6zUi0z72 FLJBFaXaUoRjoC6lZri9sTXsJL9K5M9hObF2csauT541qrZLvOo6Zml1fUnAKC5mBNq7 fxhxnbElUCVCSuLqbbgCY/ptyhgr5lPk1iaglfhzJbzhY/KnhlkEY8KAuyP94os611/I qZvgm5UEVQQwdRhHG3RVrtQ/xdntCy9tcDgcuI8myh84YthRzwmpGTvKtMQsHwzdv0cE dKjeP9ccxaLZHrh9qweoQb2gT5SvZu7g86fwk7mWDcNN6wkYQKb3C3jILs2SI2izt2nF ufSg== MIME-Version: 1.0 X-Received: by 10.194.142.231 with SMTP id rz7mr2849011wjb.89.1389713413530; Tue, 14 Jan 2014 07:30:13 -0800 (PST) Received: by 10.217.123.69 with HTTP; Tue, 14 Jan 2014 07:30:13 -0800 (PST) In-Reply-To: References: <871u0aew48.fsf@toke.dk> Date: Tue, 14 Jan 2014 10:30:13 -0500 Message-ID: From: Dave Taht To: Rich Brown Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: =?ISO-8859-1?Q?Toke_H=F8iland=2DJ=F8rgensen?= , "cerowrt-devel@lists.bufferbloat.net" Subject: Re: [Cerowrt-devel] notes on going for a stable release 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: Tue, 14 Jan 2014 15:30:20 -0000 On Tue, Jan 14, 2014 at 8:20 AM, Rich Brown wrote= : > Since I kicked off this thread, let me second what David and Toke have sa= id. > > I used the wrong word - "stable" - when I really wanted a new stake in th= e > ground. Our first was CeroWrt 3.7.5-2 - it was great. I used it for a lon= g > time before these newer builds got even better and I was willing to risk > family ire. (So far, so good with 3.10.24-8). "A new stake in the ground". I like it. We need to put that new stake in the ground and then go off to improve wifi= ! > To continue to attract attention, I'd love to be able to post news about > 3.10 on the main page of the Bufferbloat site. This would give a signal t= o > technically savvy people that we're alive and kicking and making good > things. (And many thanks for the outpouring of love and offers to help th= at > have come in from some of the new members!) In general my attempts at a "stabler" release have been keyed around ietf conferences, which this year is march 2-7 in london. http://www.ietf.org/meeting/89/index.html It's now mid-january. So if we aim for early feburary that would be good. Most of the time prior to this we've been presenting research (cheshire and I may do a preso on ECN), but *THIS TIME* it's time to propose new standard= s. So... I have been taking a thwack at updating several existing and writing several new rfcs. Very rough drafts are at https://github.com/dtaht/bufferbloat-rfcs and https://github.com/dtaht/twd/blob/master/rfc/middle.mkd "TWD" (naming still in progress) is essentially rrul v2. I took off from cero the past couple weekends and (with sean connor) got most of the truly gnarly C bits written. co-authors and reviewers welcomed! Please note that I write in outlines and in bits and bursts randomly until somehow at the end a document emerges. > We're still a research project. (Nobody has time for World Domination :-) Oh, well, DOCSIS 3.0 got the pie engineering change order a few weeks back. So some form of aqm will be on the modems starting late next year probably. No news on fixing the CMTSes of late. And I do find tales like this inspiring: http://www.forbes.com/sites/markrogowsky/2014/01/14/5-reasons-nest-sold-to-= google/ > A > stable release with 1-2 year maintenance, etc. is *way* beyond our grasp. > But I was hoping for another teaser build that addresses the worst of the > problem that Dave identified. OK. There are still 140+ bugs to review. > > Best, > > Rich > > Obligatory performance stats for 3.10.24-8. IPv4 only for the moment on m= y > WNDR3700v2. I had to reset one of my Wifi interfaces the other day. > > root@cerowrt:~# uptime > 07:57:57 up 7 days, 20:04, load average: 0.00, 0.01, 0.04 > root@cerowrt:~# cat /sys/kernel/debug/mips/unaligned_instructions > 25561 > root@cerowrt:~# dmesg | grep "TX DMA" > [114502.492187] ath: phy0: Failed to stop TX DMA, queues=3D0x084! > [114504.027343] ath: phy0: Failed to stop TX DMA, queues=3D0x006! > root@cerowrt:~# dmesg | grep "checksum failed" > root@cerowrt:~# dmesg | tail -5 > [559339.007812] gw01: Trigger new scan to find an IBSS to join > [559342.328125] gw01: Trigger new scan to find an IBSS to join > [559344.812500] gw01: Trigger new scan to find an IBSS to join > [559344.847656] gw01: Creating new IBSS network, BSSID 32:96:29:8f:34:d8 > [559344.855468] IPv6: ADDRCONF(NETDEV_CHANGE): gw01: link becomes ready > root@cerowrt:~# > > On Jan 14, 2014, at 7:51 AM, David Personette wrote: > > I agree with Toke on this, cerowrt with a single supported router was nev= er > about mass adoption. I think everyone using it is in the self selected gr= oup > of people that knew enough about networking to find why their internet > connection was *breaking* for interactive use, then go out and buy a rout= er > that cost 2x-3x what other similar specification consumer units cost. As = far > as I recall, initial installation required TFTP. Not a real hurdle for ma= ny > of us, but quite a barrier to the normal consumer. I've been using it for= my > primary router for over a year now, and have been very happy with it's > stability and reliability. I've had to roll back a few builds, but no rea= l > issues otherwise. People that are here, are here to be where all the new > development of consumer level implementations of internet protocols and > things getting fixed is happening. My 2 cents. > > -- > David P. > > > > On Tue, Jan 14, 2014 at 4:44 AM, Toke H=F8iland-J=F8rgensen > wrote: >> >> Christopher Robin writes: >> >> > ***Are we here for research and development, or are we here for final >> > implementation? >> >> I've always thought about CeroWRT as an R&D project. As Dave points out >> I don't think it's realistic to provide a "stable" release in the sense >> of having it upgraded and maintained. At least not as things stand now. >> However, designating a release as "stable" in the same way as the >> previous one (i.e. something that won't crash and where most or all of >> the advertised features (mostly) work) would probably be a good idea. >> In particular, crash bugs and things that are completely broken should >> probably be fixed? >> >> >> As far as my installation goes: >> >> # cat /sys/kernel/debug/mips/unaligned_instructions >> 154737 >> # uptime >> 10:39:18 up 5 days, 10:56, load average: 0.05, 0.03, 0.04 >> # dmesg | grep "TX DMA" >> [348064.371093] ath: phy0: Failed to stop TX DMA, queues=3D0x004! >> # dmesg | grep "checksum failed" >> [13551.957031] ICMPv6 checksum failed >> [2001:xxxx:xxxx:xxxx:0000:0000:0000:0001 > >> 2001:xxxx:xxxx:xxxx:0000:0000:0000:0002] >> [16072.535156] ICMPv6 checksum failed >> [2001:xxxx:xxxx:xxxx:0000:0000:0000:0001 > >> 2001:xxxx:xxxx:xxxx:0000:0000:0000:0002] >> [22734.054687] ICMPv6 checksum failed >> [2001:xxxx:xxxx:xxxx:0000:0000:0000:0001 > >> 2001:xxxx:xxxx:xxxx:0000:0000:0000:0002] >> [93252.820312] ICMPv6 checksum failed >> [2001:xxxx:xxxx:xxxx:0000:0000:0000:0001 > >> 2001:xxxx:xxxx:xxxx:0000:0000:0000:0002] >> [96253.570312] ICMPv6 checksum failed >> [2001:xxxx:xxxx:xxxx:0000:0000:0000:0001 > >> 2001:xxxx:xxxx:xxxx:0000:0000:0000:0002] >> [106396.003906] ICMPv6 checksum failed >> [2001:xxxx:xxxx:xxxx:0000:0000:0000:0001 > >> 2001:xxxx:xxxx:xxxx:0000:0000:0000:0002] >> [156808.253906] ICMPv6 checksum failed >> [2001:xxxx:xxxx:xxxx:0000:0000:0000:0001 > >> 2001:xxxx:xxxx:xxxx:0000:0000:0000:0002] >> [163650.000000] ICMPv6 checksum failed >> [2001:xxxx:xxxx:xxxx:0000:0000:0000:0001 > >> 2001:xxxx:xxxx:xxxx:0000:0000:0000:0002] >> [224205.101562] ICMPv6 checksum failed >> [2001:xxxx:xxxx:xxxx:0000:0000:0000:0001 > >> 2001:xxxx:xxxx:xxxx:0000:0000:0000:0002] >> [269216.191406] ICMPv6 checksum failed >> [2001:xxxx:xxxx:xxxx:0000:0000:0000:0001 > >> 2001:xxxx:xxxx:xxxx:0000:0000:0000:0002] >> [276718.035156] ICMPv6 checksum failed >> [2001:xxxx:xxxx:xxxx:0000:0000:0000:0001 > >> 2001:xxxx:xxxx:xxxx:0000:0000:0000:0002] >> [316807.695312] ICMPv6 checksum failed >> [2001:xxxx:xxxx:xxxx:0000:0000:0000:0001 > >> 2001:xxxx:xxxx:xxxx:0000:0000:0000:0002] >> [329890.929687] ICMPv6 checksum failed >> [2001:xxxx:xxxx:xxxx:0000:0000:0000:0001 > >> 2001:xxxx:xxxx:xxxx:0000:0000:0000:0002] >> [333792.148437] ICMPv6 checksum failed >> [2001:xxxx:xxxx:xxxx:0000:0000:0000:0001 > >> 2001:xxxx:xxxx:xxxx:0000:0000:0000:0002] >> [399208.269531] ICMPv6 checksum failed >> [2001:xxxx:xxxx:xxxx:0000:0000:0000:0001 > >> 2001:xxxx:xxxx:xxxx:0000:0000:0000:0002] >> [410070.828125] ICMPv6 checksum failed >> [2001:xxxx:xxxx:xxxx:0000:0000:0000:0001 > >> 2001:xxxx:xxxx:xxxx:0000:0000:0000:0002] >> [435757.078125] ICMPv6 checksum failed >> [2001:xxxx:xxxx:xxxx:0000:0000:0000:0001 > >> 2001:xxxx:xxxx:xxxx:0000:0000:0000:0002] >> [441458.539062] ICMPv6 checksum failed >> [2001:xxxx:xxxx:xxxx:0000:0000:0000:0001 > >> 2001:xxxx:xxxx:xxxx:0000:0000:0000:0002] >> [449560.417968] ICMPv6 checksum failed >> [2001:xxxx:xxxx:xxxx:0000:0000:0000:0001 > >> 2001:xxxx:xxxx:xxxx:0000:0000:0000:0002] >> >> >> I've had to re-initialise the wifi a couple of times for no apparent >> reason, and one or two reboots necessary, but nothing that major... >> >> -Toke >> >> _______________________________________________ >> Cerowrt-devel mailing list >> Cerowrt-devel@lists.bufferbloat.net >> https://lists.bufferbloat.net/listinfo/cerowrt-devel >> > > _______________________________________________ > Cerowrt-devel mailing list > Cerowrt-devel@lists.bufferbloat.net > https://lists.bufferbloat.net/listinfo/cerowrt-devel > > > > _______________________________________________ > Cerowrt-devel mailing list > Cerowrt-devel@lists.bufferbloat.net > https://lists.bufferbloat.net/listinfo/cerowrt-devel > --=20 Dave T=E4ht Fixing bufferbloat with cerowrt: http://www.teklibre.com/cerowrt/subscribe.= html