From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-qc0-x233.google.com (mail-qc0-x233.google.com [IPv6:2607:f8b0:400d:c01::233]) (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 D130621F18F for ; Fri, 7 Feb 2014 10:43:42 -0800 (PST) Received: by mail-qc0-f179.google.com with SMTP id e16so6563295qcx.38 for ; Fri, 07 Feb 2014 10:43:41 -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=4QdJ61hVso9H69+2XHzb5FFlrsngmc20HQ51mvO4Vjc=; b=cChXqf8XvR1mOYBH7rJFy9+Be90eGvo/p9XisXEFwKMfuCIFC+o/JFfLe8S184gdRh 3X15rjPIZLkVO19OMsH8LawXoC4NqddlNTIZyooF1pI12oBa7rAKH+0I1+7cKgT6Sirb svVOn/D/0Duoy3INKViaYOOy6nICtjXf2cFpry1jbVdcJwUw61b0SAScPTkcwkyni1Hi w9sdw+0VmiUjCMquQajkATnYeaqkOzJ+Qafa6+aIbjmaURq8Hcyqq4YRa9XfrKBdLo7q mOZGFq3Pf2Kn3J7IWvJRy8ujS26QXxcEgVlwdZ8FYpaR5WsoY1KDeOoTTtIHdSiPOVGP cxfQ== MIME-Version: 1.0 X-Received: by 10.140.98.135 with SMTP id o7mr23057544qge.102.1391798621661; Fri, 07 Feb 2014 10:43:41 -0800 (PST) Received: by 10.224.27.133 with HTTP; Fri, 7 Feb 2014 10:43:41 -0800 (PST) In-Reply-To: <7A5BD219-4F0F-48AA-B414-77F07CBF7095@gmx.de> References: <20140207100146.5ba027c3@samsung-9> <7A5BD219-4F0F-48AA-B414-77F07CBF7095@gmx.de> Date: Fri, 7 Feb 2014 13:43:41 -0500 Message-ID: From: Dave Taht To: Sebastian Moeller Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: "cerowrt-devel@lists.bufferbloat.net" Subject: Re: [Cerowrt-devel] Will there ever be a stable version of cerowrt? 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: Fri, 07 Feb 2014 18:43:43 -0000 On Fri, Feb 7, 2014 at 1:37 PM, Sebastian Moeller wrote: > Hi Dave, > > > On Feb 7, 2014, at 18:57 , Dave Taht wrote: > >> On Fri, Feb 7, 2014 at 12:01 PM, Stephen Hemminger >> wrote: >>> Any progress on getting a stable version? Recent versions seem to be ta= rgeted >>> at IPv6 and other things which do not impact me for home use. What does= matter >>> is fixing the wireless hanging issue on 2.4Ghz. >> >> Do I detect a plainative note? I share it... >> >> I'm not aware of any problems on 2.4ghz in the last specific release I >> did for comcast. It's been in day-to-day use here since I put it out. >> >> http://snapon.lab.bufferbloat.net/~cero2/cerowrt/wndr/comcast/3.10.28-4/ >> >> Feel free to give it a shot. The stuff that made it comcast specific >> (co-existence with HE tunnels) is solved, so the next gen will be >> generic. >> >> I AM painfully aware that ht40+ at 5ghz appears to have broken on >> several channels (Seems to work on 36 and fail on 44) There was a >> fresh merge from wireless-testing recently, that I hope fixes it. > > With ht40+ on 44 I get MCS index 7 with transmigrate 150 reported= on my macbook, that according to the table in http://en.wikipedia.org/wiki= /IEEE_802.11n-2009 means 40MHz channel, with netperf-wrapper I get an accum= ulate of ~100Mbits/s (which actually sounds too good to be true I would hav= e expected 75 tops, but with the macbook hogging all tops, there seems to b= e less wasted airtime for direction changes). So at least with country code= GE channel 44 is capable of operating in ht40+ mode. What release exactly? I confess to have merely seen the bug on a release or two back. You should get MCS15, btw. >> There is still one unaligned_instruction trap left to beat that >> appears to be triggered by odhcpd. >> >> root@comcast-gw:~# cat /sys/kernel/debug/mips/unaligned_instructions >> 18000 > > So with my non-working IP6 on 3.10.28-1, I get: > root@nacktmulle:~# cat /sys/kernel/debug/mips/unaligned_instructions > 0 > root@nacktmulle:~# uptime > 19:35:13 up 11 days, 22:46, load average: 0.09, 0.43, 1.06 No, not fixed, it's triggered by ipv6 traffic. > > so most of the traps seem fixed! > > >> >> One of the things that scares me is that a bunch of openwrt targets >> are migrating to 3.13 and if I miss a window the very stable 3.10.28 >> release is going to get replaced upstream with 3.13 and resultant >> headaches. (and benefits) > > Do yu know what their plan is? Put out a stable version an mainta= in that or switch to a rolling release cycle? I have had few detailed conversations with the #openwrt-devel folk of late. I have been ignoring irc in favor of doing work. There is a ton of good stuff landing in openwrt, let me forward something in a second... > > > Best Regards & many Thanks for doing all this > Sebastian > >> >> As my own deadlines slip everywhere, I made a big push earlier this >> week to appeal to many folk to get dnsmasq + dnssec more widely tested >> on other platforms in the hope that whenever I got unburied it would >> be stable enough to toss into cero. (that's going along swimmingly on >> x86 and arm so far) >> >> I hope to replace the failed server this tonight and burn sunday on >> trying to resolve the problems above. The currently borked srcs are on >> github. >> >> >> -- >> Dave T=E4ht >> >> Fixing bufferbloat with cerowrt: http://www.teklibre.com/cerowrt/subscri= be.html >> _______________________________________________ >> 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