From: Dave Taht <dave.taht@gmail.com>
To: cerowrt-devel@lists.bufferbloat.net
Subject: [Cerowrt-devel] bug in simple_qos.sh on ingress that has been there for a long time...
Date: Mon, 7 Jan 2013 00:22:25 +0000 [thread overview]
Message-ID: <CAA93jw5=RnpFfyN_hN_rCeQ7bqv1o=km3L=9KwQ0AfU60UQO5A@mail.gmail.com> (raw)
I have been puzzled over some classification related behaviors for
quite some time. I just finally figured out that the simple_qos script
is buggy on ingress, in that it dumps most of the traffic into the
"background" bin.
Things like
netperf -Y CS1,CS1 -H snapon.lab.bufferbloat.net # ends up in
background bin (1:13)
netperf -Y CS0,CS0 -H snapon.lab.bufferbloat.net # ALSO ends up in
background bin (1:13)
tc -s qdisc show dev ifb0
So there is a bug in the "diffserv" component of that script in that
this match matches almost everything for some reason.
The offending line is:
tc filter add dev $DEV protocol ip parent 1:0 prio 6 u32 match ip tos
0x20 0xfc classid 1:13 # CS1 Bulk
On egress it uses the more "sane to express" iptables version (which
won't work on ingress) to do similar classification.
The reason for the 0xfc was to filter out ECN bits. Maybe I've got
that backwards? or these filters need to be differently masked? or?
/me has brain fail to do an and
Anyway, for those collecting data on up/down bandwidths and playing
with classification, this bug is going to mess up your world. It just
did mine, anyway.
--
Dave Täht
Fixing bufferbloat with cerowrt: http://www.teklibre.com/cerowrt/subscribe.html
reply other threads:[~2013-01-07 0:22 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='CAA93jw5=RnpFfyN_hN_rCeQ7bqv1o=km3L=9KwQ0AfU60UQO5A@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