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] cerowrt 3.6.9-5
Date: Sun, 9 Dec 2012 08:28:21 +0100	[thread overview]
Message-ID: <CAA93jw5iuEX7sAj2OP1MBTA=DfDy3Te79zp6xY77y-=JKdbiDA@mail.gmail.com> (raw)

Under absolutely no circumstances install this on your default gateway.

http://snapon.lab.bufferbloat.net/~cero2/cerowrt/3.6/3.6.9-5/

* IPtables moved forward to 1.4.16.3 (thx swalker)
* IPv6 instruction traps eliminated (Thx robert bradley) * wow! big difference!
* Enabled (the old, non signed) opkg (thx murphy)

I would, however, now that opkg works again, like people to take a
look at their favorite packages, and see what broke. (and what's
missing!)

I'm pretty sure samba's default config is wrong... there's a new
dhcpv6 client daemon totally untested... I haven't folded in the upnp
fixes.... didn't try mesh networking....

Probably one of the biggest things that concerns me is vpn behavior
under fq_codel, and in the three bin classification scheme the
simple_qos.sh script uses. (openvpn is installed by default,
strongswan as an option)

And:

Given how successful that script has been at actually using
classification I've been toying with the idea of boiling the core
ideas of simple_qos, into pure C in the the nfq_codel version of
fq_codel, so that htb would not be required to do it (in other words,
it would "just work" in variable rate scenarios)

Partial syntax idea:

tc qdisc add dev whatever root nfq_codel bgweight 20 # Background
traffic would get 5% of the sent packets

Regrettably I can't come up with a mental way to express a "capped
weight" for priority traffic...

That said, merely having a background class may well be good enough,
as fq_codel does such a great job already in taking light traffic that
should be high priority and making it so.

I go back, however, to worrying about encapsulated traffic (such as
vpn) that might need to ignore classification in order to preserve the
stream boundries....



-- 
Dave Täht

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

             reply	other threads:[~2012-12-09  7:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-09  7:28 Dave Taht [this message]
2012-12-10  0:00 ` Michael Richardson
2012-12-10  7:39   ` Dave Taht
2012-12-10 14:22     ` Michael Richardson

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='CAA93jw5iuEX7sAj2OP1MBTA=DfDy3Te79zp6xY77y-=JKdbiDA@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