[Cerowrt-devel] pretty happy with cerowrt 3.6.9-5

[Cerowrt-devel] pretty happy with cerowrt 3.6.9-5

[Dave Taht]

[-- Attachment #1: Type: text/plain, Size: 1245 bytes --]

ok, I've pounded 3 wndr3800s flat with a variety of tests, got openvpn
working, filed a bug or two, hacked on simple_qos,
and have used it as a default gw on both wired and wifi, meshed 'em
together, and made a lot of rrul graphs, pounding the machines flat
with 6 different boxes driving it all at once and never a hitch.

Also installed openvpn today, it "just worked". I see the tun driver
dropping a ton of packets but I'm unfamiliar with the correct
behavior... polipo works... can't remember what else I tried...

Remaining minuses...

- ipv6 is mostly untested - multiple things in flux there - but it
does work and route...
- bind-latest is eating 100% of cpu (dnsmasq is the default now anyway)
- gui is largely untested
- haven't got around to fixing minidlna

upcoming in 3.6.9-6 will be:

Ketan landed a patch for httpping to support tcp fast open
the new ipv6 scripts have landed
ccnx .7
better simple_qos script

So IF you don't need the above features and are feeling daring, go
ahead and give cerowrt 3.6.9-5 a little wider testing...

I am trying to get a little analysis done on very long RTTs...

-- 
Dave Täht

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

[-- Attachment #2: rtt_fair_long_efq_codel.svg --]
[-- Type: image/svg+xml, Size: 403918 bytes --]

Re: [Cerowrt-devel] pretty happy with cerowrt 3.6.9-5

[Richard Brown]

A field report on 3.6.9-5. I installed it on my WNDR3700v2, then used my two configuration scripts to get it set, and it's working pretty well.

- I used a version of the config.sh script at http://www.bufferbloat.net/projects/cerowrt/wiki/Installation_Guide to enable SNMP and net flow. This seemed to work OK.

- I used a version of the tunnel.sh script at http://www.bufferbloat.net/projects/cerowrt/wiki/IPv6_Tunnel to enable IPv6 tunneling through to Hurricane Electric. The CeroWrt router itself gets an IPv6 address and can ping IPv6 addresses in the Internet as expected, local interfaces get a global address as well, but devices on the local interfaces do not get a global IPv6 address. If I read the release notes correctly, this is an expected result.

- Startup seems faster. Here's what I saw: It seems as if DNS resolution started faster, or am I just imagining it?

21:06:00 turned on power
21:07:38  Got IPv4 DHCP address on se00
21:08:00 DNS resolution to outside world started up

I haven't done any performance or latency testing, but I'm sending this email via the CeroWrt5 wireless interface.

Rich