From: Andrew Beverley <andy@andybev.com>
To: lartc@vger.kernel.org
Subject: Re: prio queue not working as expected?
Date: Thu, 20 Jun 2013 07:25:56 +0000 [thread overview]
Message-ID: <1371713156.2002.406.camel@andrew-desktop> (raw)
In-Reply-To: <DA9CFCDD-0EDA-4CDC-966E-33B6E40838C0@wogri.com>
On Wed, 2013-06-19 at 15:15 +0200, Wolfgang Hennerbichler wrote:
> hi tc folks,
>
> I'm trying to set up a bridged traffic shaper, and I am experimenting with the prio qdisc.
> I've take the example from www.lartc.org:
>
> tc qdisc add dev wan0 root handle 1: prio
> tc qdisc add dev wan0 parent 1:1 handle 10: sfq
> tc qdisc add dev wan0 parent 1:2 handle 20: tbf rate 20kbit buffer 1600 limit 3000
> tc qdisc add dev wan0 parent 1:3 handle 30: sfq
>
> unfortunately, it seems as if it doesn't detect the TOS of my scp
> traffic. when I do a scp from a box behind the bridge, only qdisc 20:
> increases it's counters,
For an scp command, it should be the 20: or 30: counters that increase,
as it's bulk traffic.
> I can't create counter values in 10: or 30: by issuing telnet or ssh
> commands or whatever.
But normal ssh commands should, of course, be in 10:
I don't know why it is not working for you, but I've just tried the
above commands myself and it works for me, so at least you know that the
example is correct.
> The system is running within a VM on linux kernel 3.7.10.
> I can't figure out what's wrong here. Any help is really appreciated.
My test was with Linux 3.0.0, not inside a VM.
You could maybe use some iptables logging to see if the packets have the
TOS value that you expect? You could also try setting some TOS values
with iptables and see if that works.
Andy
next prev parent reply other threads:[~2013-06-20 7:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-19 13:15 prio queue not working as expected? Wolfgang Hennerbichler
2013-06-20 7:25 ` Andrew Beverley [this message]
2013-06-20 18:35 ` Wolfgang Hennerbichler
2013-06-21 5:42 ` Wolfgang Hennerbichler
2013-06-21 9:09 ` Wolfgang Hennerbichler
2013-06-21 11:46 ` Remy Mudingay
2013-06-24 7:47 ` Wolfgang Hennerbichler
2013-06-24 10:15 ` Remy Mudingay
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1371713156.2002.406.camel@andrew-desktop \
--to=andy@andybev.com \
--cc=lartc@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.