Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: cerowrt-devel@lists.bufferbloat.net
Subject: [Cerowrt-devel] pretty happy with cerowrt 3.6.9-5
Date: Mon, 10 Dec 2012 21:58:02 +0100	[thread overview]
Message-ID: <CAA93jw6MY70S7jmuH3uOJ17dx43DyKi1_uyUQ5YmBxCm0HGf9A@mail.gmail.com> (raw)

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

ok, I've pounded 3 wndr3800s flat with a variety of tests, got openvpn
working, filed a bug or two, hacked on simple_qos,
and have used it as a default gw on both wired and wifi, meshed 'em
together, and made a lot of rrul graphs, pounding the machines flat
with 6 different boxes driving it all at once and never a hitch.

Also installed openvpn today, it "just worked". I see the tun driver
dropping a ton of packets but I'm unfamiliar with the correct
behavior... polipo works... can't remember what else I tried...

Remaining minuses...

- ipv6 is mostly untested - multiple things in flux there - but it
does work and route...
- bind-latest is eating 100% of cpu (dnsmasq is the default now anyway)
- gui is largely untested
- haven't got around to fixing minidlna

upcoming in 3.6.9-6 will be:

Ketan landed a patch for httpping to support tcp fast open
the new ipv6 scripts have landed
ccnx .7
better simple_qos script

So IF you don't need the above features and are feeling daring, go
ahead and give cerowrt 3.6.9-5 a little wider testing...

I am trying to get a little analysis done on very long RTTs...

-- 
Dave Täht

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

[-- Attachment #2: rtt_fair_long_efq_codel.svg --]
[-- Type: image/svg+xml, Size: 403918 bytes --]

             reply	other threads:[~2012-12-10 20:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-10 20:58 Dave Taht [this message]
     [not found] <mailman.4534.1355173139.1742.cerowrt-devel@lists.bufferbloat.net>
2012-12-12  2:18 ` Richard Brown

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=CAA93jw6MY70S7jmuH3uOJ17dx43DyKi1_uyUQ5YmBxCm0HGf9A@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