Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: Richard Brown <richard.e.brown@dartware.com>
Cc: "<cerowrt-devel@lists.bufferbloat.net>"
	<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] 3.3.2-3 available
Date: Mon, 16 Apr 2012 13:43:31 -0700	[thread overview]
Message-ID: <CAA93jw6awAgt6GFffHRMfovXXFMDbRGFZFVksjcqq8d_FwGtVA@mail.gmail.com> (raw)
In-Reply-To: <883E640C-9CDD-4F08-98C1-F7BF48B05AFD@intermapper.com>

On Mon, Apr 16, 2012 at 12:14 PM, Richard Brown
<richard.e.brown@dartware.com> wrote:
> Dave,
>
> I see you've done a lot of really good work over the weekend. Two questions:

oh, no, I was mostly just sitting back in admiration of robert....

> 1) There are two mentions of Linux kernel versions in your note below:
> should they be 3.3.x? Specifically:

yes. finger foo.

>
> ... + Linux 3.2.2 ...
> - and -
> ... I will probably update the kernel to 3.2.3 ...

3.3.2 is the current version and I figure an update to 3.3.3 will be in order
(I'm carrying 5 out of tree patches that are queued up for that version)

> If not, then I guess I'm confused, and would like a little more background
> about the kernel and patches (3.3 vs. 3.2) that are present in the 3.3.2-2
> (and other recent) releases.
>
> 2) Should I begin incorporating this new info into the Release Notes page
> with an eye toward announcing 3.3.2-3?

I know I've been hesitant about pursuing formal releases and announcements.

I would really like my last 3 major bugs to be resolved before announcing
anything more outside of this core group.

I certainly would like to start at relnotes etc. But first up is resolving the
dhcp-pd, aqm, and darn it, I forget the third issue...

>
> Thanks.
>
> Rich
>
> On Apr 16, 2012, at 3:00 PM, <cerowrt-devel-request@lists.bufferbloat.net>
>  wrote:
>
> http://huchra.bufferbloat.net/~cero1/3.3/3.3.2-3/
>
> Things of note:
>
> + ipv6 and ipv4 now have comparable forwarding performance
>
> Huge hat tip to Ketan Kulkarni and Robert Bradley for this one.
> see  http://www.bufferbloat.net/issues/360 for the gory details.
>
> This does not just improve forwarding performance, it makes
> things like tests done on the router have far more reliable
> results. There's still a ways to go on #360, but we'll get there.
>
> + Linux 3.2.2
>
> + Default firewall rules now work with web interface
> - Firewall rules still need more love and thought
> + My alternate firewall rule script works much better
> - No way to make that into a gui
> + ccnx package fixed (thx stephen walker)
> + scamper package added (thx stephen walker)
>
> http://www.wand.net.nz/scamper
> http://www.caida.org/projects/ark/
>
> + gpsd updated to final release (thx lots of people)
> + quagga updated (bugfix)
>
> + Ingress and egress aqm shaper prototypes now exist in the deBloat repo
> - Still only prototypes
> - still no working dhcp-pd
>
> At this time I consider the core features and code of cerowrt basically
> frozen.
>
> About the only things I expect to land before release are a more final
> version
> of dnsmasq, and I will probably update the kernel to 3.2.3 when it is
> released
> to reduce the number of out of tree packages.
>
>
>
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel
>



-- 
Dave Täht
SKYPE: davetaht
US Tel: 1-239-829-5608
http://www.bufferbloat.net

  reply	other threads:[~2012-04-16 20:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.2.1334602803.18157.cerowrt-devel@lists.bufferbloat.net>
2012-04-16 19:14 ` Richard Brown
2012-04-16 20:43   ` Dave Taht [this message]
2012-04-17 12:09     ` Richard Brown
2012-04-16 14: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=CAA93jw6awAgt6GFffHRMfovXXFMDbRGFZFVksjcqq8d_FwGtVA@mail.gmail.com \
    --to=dave.taht@gmail.com \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=richard.e.brown@dartware.com \
    /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