Historic archive of defunct list bloat-announce@lists.bufferbloat.net
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: bloat <bloat@lists.bufferbloat.net>,
	 bloat-devel <bloat-devel@lists.bufferbloat.net>,
	bloat-announce@lists.bufferbloat.net
Subject: Smoketesting 'CeroWrt''s Ocean City release
Date: Sat, 9 Jul 2011 11:45:15 -0600	[thread overview]
Message-ID: <CAA93jw4Qv3dO-BW4+wijeSYRhdxsi=MvcRy3JjJq47tRprLDmw@mail.gmail.com> (raw)

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

After a long gestation, we're happy to announce the existence of a 'smoke
test' release of 'CeroWrt', for the NETGEAR WNDR3700v2 series of routers.

Documentation, flash images, and installation guide are at:

http://www.bufferbloat.net/projects/cerowrt/wiki/OCEAN_CITY_INSTALLATION_GUIDE

This smoke test release is only for the brave... of whom I hope there are
many on these lists.

I hope to put out one release candidate per week for the next month, until
this is baked enough to freeze for a while.

The existing bug/feature database is out of date, I'll be updating that
soon, but as this is hopefully baked enough for others than myself, jg, esr,
and evan hunt to be be using, I'd love it if more people could get one of
these routers and try out this code.

What the heck is CeroWrt?

Cerowrt is the outgrowth of trying to de-heisenbug debloat-testing. The
results we were getting on conventional boxes were not repeatable on
conventional routers, until now. The project gradually grew from OpenWrt
into a kitchen sink worth of useful network analysis stuff from other
projects until it became... CeroWrt. Much of it has been pushed back into
openwrt...

To quote from it's integral help screen:

CeroWrt is an OpenWrt router platform for use by individuals, researchers,
and students interested in advancing the state of the art on the Internet.
Specifically, it is aimed at investigating the problems of latency under
load, bufferbloat, wireless-n, QoS, and the effects of various TCP
algorithms on shared networks. The features of this release include:

* linux 2.6.39.2 with a few bloat-related patches
* Bind9 DNS services with DNSSEC
* extensive network diagnostic, performance measurement, and simulation
tools
* support for TCP bic, cubic, westwood, and reno
* comprehensive IPv6 support
* integral web and rsync servers
* support for mesh networking
* a web proxy server

and most importantly, extensive debloating throughout the stack.

For more details please see the wiki pages and bug database, and check in on
the #bufferbloat irc channel. I will be at Georgia Tech all next week
working on getting their test tools up and running on it, but will be
available for help and upgrades on the mailing lists and

Additional details on on the wiki.

http://www.bufferbloat.net/projects/cerowrt/wiki/

Happy debloating!

-- 
Dave Täht
SKYPE: davetaht
US Tel: 1-239-829-5608
http://the-edge.blogspot.com

[-- Attachment #2: Type: text/html, Size: 2837 bytes --]

                 reply	other threads:[~2011-07-09 17:10 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAA93jw4Qv3dO-BW4+wijeSYRhdxsi=MvcRy3JjJq47tRprLDmw@mail.gmail.com' \
    --to=dave.taht@gmail.com \
    --cc=bloat-announce@lists.bufferbloat.net \
    --cc=bloat-devel@lists.bufferbloat.net \
    --cc=bloat@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