From: Johan Huysmans <johan.huysmans@inuits.be>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] tc doesn't shape correct {SOLVED}
Date: Wed, 19 Dec 2007 11:47:10 +0000 [thread overview]
Message-ID: <476904BE.60306@inuits.be> (raw)
My issue is solved.
Andy Furniss has mailed me a new set of rules which are doing exactly
what you expect.
For the record, here are the rules:
/sbin/tc qdisc del dev bond1 root
/sbin/tc qdisc add dev bond1 root handle 1: htb
/sbin/tc class add dev bond1 parent 1: classid 1:1 htb rate 30mbit
/sbin/tc qdisc add dev bond1 parent 1:1 handle 10: pfifo limit 300
/sbin/tc class add dev bond1 parent 1: classid 1:2 htb rate 10mbit
/sbin/tc qdisc add dev bond1 parent 1:2 handle 20: pfifo limit 100
/sbin/tc filter add dev bond1 parent 1: protocol ip prio 0 handle 1 fw
flowid 1:1
/sbin/tc filter add dev bond1 parent 1: protocol ip prio 0 handle 2 fw
flowid 1:2
Thx for helping to fix this!
Johan
Johan Huysmans wrote:
> Hi All,
>
> I'm configuring my natting-firewall to do some tc shaping. Some
> traffic has to be shaped on 30mbit, some on 10mbit all the others are
> unlimited.
> The configuring and filtering works correctly. The traffic that is
> shaped at 30mbit is correct, but the traffic that is shapped at 10mbit
> only gets to 100KB/sec.
>
> It is on a device configured with bonding (both in and out interface).
>
> Any clue why shaped traffic at 10mbit only gets to 100KB/sec and not
> faster?
>
> Thx for any response,
> Johan Huysmans
> _______________________________________________
> LARTC mailing list
> LARTC@mailman.ds9a.nl
> http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
reply other threads:[~2007-12-19 11:47 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=476904BE.60306@inuits.be \
--to=johan.huysmans@inuits.be \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox