From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mout.gmx.net (mout.gmx.net [212.227.17.22]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-1" (verified OK)) by huchra.bufferbloat.net (Postfix) with ESMTPS id B5ED7201299 for ; Fri, 7 Feb 2014 10:37:50 -0800 (PST) Received: from hms-beagle.home.lan ([217.86.112.208]) by mail.gmx.com (mrgmx002) with ESMTPSA (Nemesis) id 0MQzIE-1Vn88z3U4M-00UNNH for ; Fri, 07 Feb 2014 19:37:48 +0100 Content-Type: text/plain; charset=iso-8859-1 Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\)) From: Sebastian Moeller In-Reply-To: Date: Fri, 7 Feb 2014 19:37:46 +0100 Content-Transfer-Encoding: quoted-printable Message-Id: <7A5BD219-4F0F-48AA-B414-77F07CBF7095@gmx.de> References: <20140207100146.5ba027c3@samsung-9> To: Dave Taht X-Mailer: Apple Mail (2.1510) X-Provags-ID: V03:K0:UhgPzF1s+jsuQEJCCHitl/tCBUGRAToUmcTK+luTt+oLyp/O1HI 0vgSVaLXF8m1O1lYLwCski5+o4U9tcprGQRmP584k6FKp9bbZyvS0F7v7pSrgRcPZyNSm6P /V/qQIZoL2orgx4I6vYQhDAZvEbTB2bnvZsYq1NXnRxVa/ntLZ8Gq5Ux4LrsRLPeIMUCB6U JnbCEskU6bfWJpy8PTm3Q== 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:37:51 -0000 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 = targeted >> 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. >=20 > Do I detect a plainative note? I share it... >=20 > 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. >=20 > = http://snapon.lab.bufferbloat.net/~cero2/cerowrt/wndr/comcast/3.10.28-4/ >=20 > 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. >=20 > 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 accumulate of ~100Mbits/s (which actually = sounds too good to be true I would have expected 75 tops, but with the = macbook hogging all tops, there seems to be less wasted airtime for = direction changes). So at least with country code GE channel 44 is = capable of operating in ht40+ mode. >=20 > I DO plan a stable release this month if possible, and at the very > least a code freeze fairly soon. >=20 > in cerowrt head are fixes for ipv6 tunnel co-existence, mostly > everything now using procd, fixed upnp support (think that landed in > the release above), cleanups of the SQM code for eventual submittal to > mainline landed also. >=20 > *Please note* that a source of hangs in the last several cero releases > was an oopsy in turning off logging for ahcp and babeld, which filled > up available memory rapidly. EVERYBODY: Do turn send those logs to > /dev/null if you haven't already in the relevant /etc/config/ files > and look for other sources of memory growth from logs. >=20 > the remaining problems are: >=20 > got competing work requirements terribly pressing, final pie release > needs to be added, (kind of wanted sch_fq and the other new qdisc from > 3.13, too) a bunch of ietf drafts are in the nascent stage and stuck > there, a build server crashed and a whole string of openwrt builds > failed to build, still need /etc/init.d/babeld support for source > specific routing and babel to run out of procd, package signing is > broken, and worst of the cerowrt build broke last week due to some > changes in the openwrt build process I still don't understand. >=20 > There is still one unaligned_instruction trap left to beat that > appears to be triggered by odhcpd. >=20 > 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 so most of the traps seem fixed! >=20 > 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 = maintain that or switch to a rolling release cycle? Best Regards & many Thanks for doing all this Sebastian >=20 > 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) >=20 > 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. >=20 >=20 > --=20 > Dave T=E4ht >=20 > Fixing bufferbloat with cerowrt: = http://www.teklibre.com/cerowrt/subscribe.html > _______________________________________________ > Cerowrt-devel mailing list > Cerowrt-devel@lists.bufferbloat.net > https://lists.bufferbloat.net/listinfo/cerowrt-devel