[Cerowrt-devel] Will there ever be a stable version of cerowrt?

Sebastian Moeller moeller0 at gmx.de
Fri Feb 7 13:37:46 EST 2014

Hi Dave,

On Feb 7, 2014, at 18:57 , Dave Taht <dave.taht at gmail.com> wrote:

> On Fri, Feb 7, 2014 at 12:01 PM, Stephen Hemminger
> <stephen at networkplumber.org> 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.
> 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 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.

> I DO plan a stable release this month if possible, and at the very
> least a code freeze fairly soon.
> 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.
> *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.
> the remaining problems are:
> 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.
> There is still one unaligned_instruction trap left to beat that
> appears to be triggered by odhcpd.
> root at comcast-gw:~# cat /sys/kernel/debug/mips/unaligned_instructions
> 18000

	So with my non-working IP6 on 3.10.28-1, I get:
root at nacktmulle:~# cat /sys/kernel/debug/mips/unaligned_instructions
root at 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!

> 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

> 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äht
> Fixing bufferbloat with cerowrt: http://www.teklibre.com/cerowrt/subscribe.html
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel at lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel

More information about the Cerowrt-devel mailing list