Historic archive of defunct list bismark-devel@lists.bufferbloat.net
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: bismark-devel@lists.bufferbloat.net,
	 bloat-devel <bloat-devel@lists.bufferbloat.net>
Subject: [Bismark-devel] latest dev build of cerowrt is looking great
Date: Tue, 9 Aug 2011 12:03:59 -0600	[thread overview]
Message-ID: <CAA93jw5aB_=F7SSb4Doc1QEFiSXt7JFVYohT5GxqSe6wenrxTA@mail.gmail.com> (raw)
Message-ID: <20110809180359.xwiTrHF8TB_1P-ADPFBjYe7xjnRz-pH70YTpwsqZyvc@z> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 2158 bytes --]

It's looking like bugs 195 and 216 have been thoroughly stomped.

A HUGE tip O the hat to Felix for nailing 195 and to both Felix and Andrew
for 216. 216 makes for epic reading...

http://www.bufferbloat.net/issues/216

After running overnight in the new lab at isc, fixes for those two bugs
appear to be stable, and performance is indeed improved. I'd love for some
more folk to give the dev version a shot:

http://huchra.bufferbloat.net/~andrewm/cerowrt/

I'll be building up the lab over the coming week which will ease the testing
burden. The first router is up and can be seen at:

http://jupiter.lab.bufferbloat.net/cerowrt/


In this build  are:

Fixes to bugs 195 and 216.

New versions of babel, ahcp have landed (thx, gabriel, juliusz, all),
there's a few cool new packages - like inetdxtra (which has jabber support
and a tiny dhcp server)  and dnssec-tools (thank you swalker!), and there's
a start at web10g integration that I was too scared to put in tcp's hot path
on this build, but the client side tool is in there (thx, jacobo, swalker!)


And I have a HUGE backlog of other bits to pull together, need to
re-integrate the rebased source trees... push more stuff out to openwrt, AND
a get this lab setup at isc.org, so I don't know yet when we can commit to
doing another RC or getting the sources and git trees fully out.

d-itg 2.8 is being pushed into openwrt head, waiting on that.. (so I built
2.7.2, sorry walter)

I have a dozen patches that need to be reviewed and the worthwhile ones
pushed to openwrt head at:

http://huchra.bufferbloat.net/~cero1/patches/

and another dozen tiny ones on the way, mostly involving xinetd support and
traffic classification.


Lastly:

If any members of the bloat list are in the bay area, and want to meet while
I'm here, please let me know offlist....

Blatant plug: Some old friends of mine are playing at a gig tonight at the
coffee society in campbell...

http://www.coffeesociety.com/stores.html

http://www.rebeccaparksmusic.com/events.php


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

[-- Attachment #1.2: Type: text/html, Size: 2738 bytes --]

[-- Attachment #2: Type: text/plain, Size: 158 bytes --]

_______________________________________________
Bloat-devel mailing list
Bloat-devel@lists.bufferbloat.net
https://lists.bufferbloat.net/listinfo/bloat-devel

             reply	other threads:[~2011-08-10  9:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-09 18:03 Dave Taht [this message]
2011-08-09 18:03 ` 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

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

  git send-email \
    --in-reply-to='CAA93jw5aB_=F7SSb4Doc1QEFiSXt7JFVYohT5GxqSe6wenrxTA@mail.gmail.com' \
    --to=dave.taht@gmail.com \
    --cc=bismark-devel@lists.bufferbloat.net \
    --cc=bloat-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