[Cerowrt-devel] notes on going for a stable release

Tue Jan 14 07:30:13 PST 2014

On Tue, Jan 14, 2014 at 8:20 AM, Rich Brown <richb.hanover at gmail.com> wrote:
> Since I kicked off this thread, let me second what David and Toke have said.
>
> I used the wrong word - "stable" - when I really wanted a new stake in the
> ground. Our first was CeroWrt 3.7.5-2 - it was great. I used it for a long
> 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 to
> 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 that
> 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 standards.

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 my
> WNDR3700v2. I had to reset one of my Wifi interfaces the other day.
>
> root at cerowrt:~# uptime
>  07:57:57 up 7 days, 20:04,  load average: 0.00, 0.01, 0.04
> root at cerowrt:~# cat /sys/kernel/debug/mips/unaligned_instructions
> 25561
> root at cerowrt:~# dmesg | grep "TX DMA"
> [114502.492187] ath: phy0: Failed to stop TX DMA, queues=0x084!
> [114504.027343] ath: phy0: Failed to stop TX DMA, queues=0x006!
> root at cerowrt:~# dmesg | grep "checksum failed"
> root at 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 at cerowrt:~#
>
> On Jan 14, 2014, at 7:51 AM, David Personette <dperson at gmail.com> wrote:
>
> I agree with Toke on this, cerowrt with a single supported router was never
> about mass adoption. I think everyone using it is in the self selected group
> of people that knew enough about networking to find why their internet
> connection was *breaking* for interactive use, then go out and buy a router
> 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 many
> 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 real
> 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øiland-Jørgensen <toke at toke.dk>
> wrote:
>>
>> Christopher Robin <pheoni at gmail.com> 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=0x004!
>> # 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 at lists.bufferbloat.net
>> https://lists.bufferbloat.net/listinfo/cerowrt-devel
>>
>
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel at lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel
>
>
>
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel at lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel
>

-- 
Dave Täht

Fixing bufferbloat with cerowrt: http://www.teklibre.com/cerowrt/subscribe.html