[Cerowrt-devel] happy 4th!

[Dave Taht]

I will be taking off for a few days. I've been terribly distracted
with getting the yurtlab fully up, some details here:

https://plus.google.com/u/0/107942175615993706558/posts/XFGgMTUUDWC

Suggestions as to things to test and code to test them welcomed. In
particular I'd like to find something more robust that apache's
benchmarks to more closely emulate the cablelabs tests of realistic
web sites and more realistic RTTs.

It has generally been my hope to sit down and focus on cerowrt again
starting next week, but I just took a contract (money trumps research)
which is going to push that back another week.

The present dev build seems pretty stable, but there are some busted
packages, and I will be revising the default ahcp setup to be more
useful, and adding some more polishing touches on the aqm thing. I
also need to get around to pushing up the 6in4 fq_codel fix into the
kernel mainline at the very least.

Has anyone looked at ACC from gargoyle? It's pretty interesting...

known broken stuff in the present build:

bind-latest: Presently I plan to abandon the bind-latest code, as much
as I liked the xinetd based launcher, and revert to openwrt's mainline
version of bind as an installable option. Doing that primarily to get
"nsupdate", actually...

bloat-test-scripts: keep meaning to package these up (from the ietf demo)
unbound: will add to next build
miniupnp: I saw the conversation, have no means to duplicate the
problem (should I get an xbox for the lab?)
minissd: no clue
mosh-server: dies on trying to create a pty terminal
quagga: I am toying with switching to babeld for the next build as
there is exciting stuff going on in the RTT and source routing
branches. I have some very beta homenet code for quagga that I'd like
to be able to test separately...

Kernel 3.10 is out and as the rest of the lab is moving towards
running that, I'd like to move cero to 3.10 when patches become
available rather than sticking with 3.8.13 for the next stable
release.

I would like to take a better stab at addressing

https://www.bufferbloat.net/issues/433

than merely saying: use ahcp and babel.


-- 
Dave Täht

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