From: Marek Kierdelewicz <marek@piasta.pl>
To: Jorge Bastos <mysql.jorge@decimal.pt>
Cc: netfilter@vger.kernel.org
Subject: Re: help on tc with kernels >= 2.6.27
Date: Fri, 2 Jan 2009 21:53:48 +0100 [thread overview]
Message-ID: <20090102215348.7d67b8c4@catlap> (raw)
In-Reply-To: <00c301c96d17$750ea820$5f2bf860$@jorge@decimal.pt>
>My QoS rules (always were the same)
>---
>/sbin/tc qdisc del dev eth0 root
>/sbin/tc qdisc add dev eth0 root handle 1 cbq bandwidth 100Mbit avpkt
>1000 cell 8
>/sbin/tc class change dev eth0 root cbq weight 10Mbit allot 1514
Sorry, but I'm not familiar with cbq. Try the script below:
-----------------------------CUT-----------------------------
TC="/sbin/tc"
DEV="eth0"
$TC qdisc del dev $DEV root
$TC qdisc add dev $DEV root handle 1: htb default 10
$TC class add dev $DEV parent 1: classid 1:1 htb rate 100Mbit
$TC class add dev $DEV parent 1:1 classid 1:10 htb rate 90Mbit ceil \
100Mbit
$TC class add dev $DEV parent 1: classid 1:1280 htb rate \
200kbit ceil 200kbit
$TC qdisc add dev $DEV parent 1:1280 handle 1280: sfq perturb 1
$TC filter add dev $DEV parent 1:0 protocol ip prio 100 u32 match ip \
src 195.23.14.71 match ip sport 110 0xffff classid 1:1280
-----------------------------CUT-----------------------------
I hope it does the same your cbq.init did - shapes traffic to
195.23.14.71 to maximal throuput of 200kbit/s and lets the rest of the
traffic to go fullspeed.
Regards,
Marek Kierdelewicz
next prev parent reply other threads:[~2009-01-02 20:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-02 18:46 help on tc with kernels >= 2.6.27 Jorge Bastos
2009-01-02 19:49 ` Marek Kierdelewicz
2009-01-02 20:44 ` bsilva
[not found] ` <00c301c96d17$750ea820$5f2bf860$@jorge@decimal.pt>
2009-01-02 20:53 ` Marek Kierdelewicz [this message]
2009-01-02 20:57 ` LARTC (was: Re: help on tc with kernels >= 2.6.27) /dev/rob0
2009-01-03 10:11 ` help on tc with kernels >= 2.6.27 Michele Petrazzo - Unipex srl
[not found] ` <001701c96d92$43c4e600$cb4eb200$@jorge@decimal.pt>
2009-01-03 11:47 ` Michele Petrazzo - Unipex srl
[not found] ` <002701c96d9b$53a5c0e0$faf142a0$@jorge@decimal.pt>
2009-01-03 12:29 ` Michele Petrazzo - Unipex srl
[not found] ` <003101c96ddb$9d991310$d8cb3930$@jorge@decimal.pt>
2009-01-05 11:39 ` Michele Petrazzo - Unipex srl
[not found] ` <01ee01c96f3b$eee74fa0$ccb5eee0$@jorge@decimal.pt>
2009-01-05 14:21 ` Michele Petrazzo - Unipex srl
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=20090102215348.7d67b8c4@catlap \
--to=marek@piasta.pl \
--cc=mysql.jorge@decimal.pt \
--cc=netfilter@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