Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: Rich Brown <richb.hanover@gmail.com>
Cc: cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] cerowrt 3.8.8-4 released
Date: Wed, 24 Apr 2013 22:56:14 -0700	[thread overview]
Message-ID: <CAA93jw76e3AKL_jcRJkmc2z9huwrObvpSEsrANiwfAiLU7Avog@mail.gmail.com> (raw)
In-Reply-To: <48AEAF51-9A25-4E79-969D-59CA77EBD627@gmail.com>

simplest most closely models the ns2 testing cablelabs did. By being
simpler, it has less bugs.

So if you could try that under a variety of workloads, particularly
with bittorrent I think it would be interesting... I still think the
more complex script is closer to the right thing in that case, but
lack data.

On Wed, Apr 24, 2013 at 5:06 PM, Rich Brown <richb.hanover@gmail.com> wrote:
> Folks,
>
> Good news from the (limited) testing that I do. I installed 3.8.8-4 on my WNDR3800 without incident. I also ran the two configuration scripts in the wiki to set the configuration to set the timezone, put a password on my wireless and set up the IPv6 tunnel.
>
> Thanks to Dave and Toke for adding the Network/AQM tab to the GUI. As Dave says, "No more fiddling with scripts". Any words of wisdom for choosing one of  "simple.qos" and "simplest.qos" over the other?
>
> Finally, the About… and other pages at http://gw.home.lan/cerowrt/ have been updated to talk about this release.

You know I totally forgot about that. Didn't you have a hand in that? :)

I'd meant to update the credits file on this go-round. Next time.
> Nice work, Dave, Toke, and everyone else who contributed.
>
> Rich
>
> Snag the binary at: http://snapon.lab.bufferbloat.net/~cero2/cerowrt/wndr/3.8.8-4/
> See the automated scripts at:
>         http://www.bufferbloat.net/projects/cerowrt/wiki/Automated_Configuration_of_CeroWrt
>         http://www.bufferbloat.net/projects/cerowrt/wiki/IPv6_Tunnel



-- 
Dave Täht

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

  reply	other threads:[~2013-04-25  5:56 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-24  8:55 Dave Taht
2013-04-24  8:55 ` Dave Taht
2013-04-24 14:07 ` Maciej Soltysiak
2013-04-24 15:56   ` Dave Taht
2013-04-25  0:06     ` Rich Brown
2013-04-25  5:56       ` Dave Taht [this message]
2013-04-25 14:04         ` Maciej Soltysiak
2013-04-25  7:45       ` Toke Høiland-Jørgensen
2013-06-02 18:00 ` Maciej Soltysiak
2013-06-02 18:12   ` 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=CAA93jw76e3AKL_jcRJkmc2z9huwrObvpSEsrANiwfAiLU7Avog@mail.gmail.com \
    --to=dave.taht@gmail.com \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=richb.hanover@gmail.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