From: Dave Taht <dave.taht@gmail.com>
To: cerowrt-devel@lists.bufferbloat.net
Subject: [Cerowrt-devel] 3.3rc5-1 is out
Date: Thu, 1 Mar 2012 15:30:41 +0100 [thread overview]
Message-ID: <CAA93jw4Df6QFacW1Sx5LmU5Z97kAt=nwgYLWTrps3hSviyjshA@mail.gmail.com> (raw)
3.3rc5-1 is out at:
http://huchra.bufferbloat.net/~cero1/3.3/3.3-rc5-1/
This was the first time I've had a chance to try to actually deploy
cero as the main router in a production environment (esr's) in quite
some time. Enough problems cropped up for me to recommend against
doing that at this point, although I am writing this email through it.
I did get some good data on how FIOS works (short summary: it's *hard*
to stress out fios)
Features:
Kernel 3.3rc5 + 83 patches to get it closer to rc6
gpsd 3.4+ package (from git head, trying to fix a PPS problem)
bind9.9.0 (released version)
dibbler-client (git head, fixing a crash with multiple interfaces)
A couple bugs have crept in due to bitrot, some of which I've bug
reported. The most severe appears that I have a problem with
power-save and crypto at 2.4 ghz in this (trouble with an android
phone, and the like)
firewall: syntax has changed, rules notably re ipv6 have changed,
all kinds of problems with multiple interfaces
6to4: distributing 6to4 addresses onto interfaces didn't work
ipv6: radvd doesn't always manage to distribute an address
(multicast? client side problems?) - usually crops up on more modern
wireless interfaces
ipv6: dibbler-client eats 100% of cpu after being idle overnight
http://www.bufferbloat.net/issues/341
ipv6: dibbler-client wants to 'own' radvd
bind9: needs allow-recursion
http://www.bufferbloat.net/issues/342
I'm pretty sure that most of these bugs have existed in prior releases, with the
exception of the wireless power save one... which was kind of hard to trigger.
--
Dave Täht
SKYPE: davetaht
US Tel: 1-239-829-5608
http://www.bufferbloat.net
next reply other threads:[~2012-03-01 14:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-01 14:30 Dave Taht [this message]
2012-03-01 14:48 ` Dave Taht
2012-03-01 16:24 ` Dave Taht
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAA93jw4Df6QFacW1Sx5LmU5Z97kAt=nwgYLWTrps3hSviyjshA@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox