From: Dave Taht <dave.taht@gmail.com>
To: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] Three new diffserv codepoints suggested
Date: Sat, 11 Jun 2011 23:05:44 -0600 [thread overview]
Message-ID: <BANLkTikHnHkW5+or-Z_pfRmHRKb03vU+_Q@mail.gmail.com> (raw)
In-Reply-To: <BANLkTikk8Tdj6+NSQ69hfMPOO33MPUrKkA@mail.gmail.com>
So I sat down and took the fragments of various qos scripts I'd been
fiddling with, and came up with a diffserv
classifier (doesn't do qos or cope with nat yet) that matches a great
deal of traffic somewhat sanely (notably 'IT', 'mice', and ipv6). It
should work on any linux box, as well as openwrt - (but note nat & qos
caveat above)
It's in my github repo at:
https://github.com/dtaht/Diffserv
(send me your login, I'll give commit access, or you can just do a:
git clone git://github.com/dtaht/Diffserv.git
cd Diffserv/scripts
sudo ./diffserv_dbg up # to turn it on
sudo ./diffserv_dbg status # to see some statistics
Various iptables rules for ecn matches, etc, in there, too.
(the ecn match for ipv6 requires netfilter-head)
While the huge problems of classifying traffic on a large scale on the
edge seem almost tractable with crowdsourcing, still the plethora of
random sources on port 80 seem impossible to cope with.
One thing I intend to use this for is to be able to track delays
through the network. I can now filter on a given
traffic class during real traffic, during a tcp dump, with and without
qos enabled, with or without debloating techniques in place.
--
Dave Täht
SKYPE: davetaht
US Tel: 1-239-829-5608
http://the-edge.blogspot.com
next prev parent reply other threads:[~2011-06-12 4:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-11 13:15 Dave Taht
2011-06-12 5:05 ` Dave Taht [this message]
2011-06-13 14:10 ` Jonathan Morton
2011-06-13 14:35 ` 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/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=BANLkTikHnHkW5+or-Z_pfRmHRKb03vU+_Q@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=bloat@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