From: "Julián Muñoz" <jmunoz@telefonica.net>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] htb+tc (protocol priority)
Date: Tue, 26 Mar 2002 13:41:04 +0000 [thread overview]
Message-ID: <marc-lartc-101715025402488@msgid-missing> (raw)
In-Reply-To: <marc-lartc-101714812132563@msgid-missing>
Hi George,
I am a newbie, but not an inexpert :-)
The fact is that reading your message, I don't understand anything, you
put technical datas, while I think you ask for some help a the concept
level.
:-)
On Tue, 26 Mar 2002, George Tsuladze wrote:
> It is my tc script. I want to priorize some protocols.
> I want to do the following: in 1:1classid udp must be first then icmp
> then any other
> Also in 1:2 first udp second icmp third tcp then any other.
> How can i do it? Can u give me some examples.
>
> tc qdisc del dev eth0 root
> #eht0 rules
> tc qdisc add dev eth0 root handle 1: htb default 11
> #shape interface eth0
> tc class add dev eth0 parent 1: classid 1:1 htb rate 500kbit ceil
> 512kbit burst 2k
> tc class add dev eth0 parent 1:1 classid 1:2 htb rate 12kbit ceil
> 512kbit burst 2k
> #voip class
> tc class add dev eth0 parent 1:1 classid 1:12 htb rate 100kbit ceil
> 512kbit burst 2k
> tc class add dev eth0 parent 1:1 classid 1:14 htb rate 100kbit ceil
> 512kbit burst 2k
> tc class add dev eth0 parent 1:1 classid 1:16 htb rate 100kbit ceil
> 512kbit burst 2k
> tc class add dev eth0 parent 1:1 classid 1:18 htb rate 100kbit ceil
> 512kbit burst 2k
> tc class add dev eth0 parent 1:1 classid 1:20 htb rate 100kbit ceil
> 512kbit burst 2k
> #staff class
> tc class add dev eth0 parent 1:2 classid 1:11 htb rate 4kbit ceil
> 512kbit burst 2k
> tc class add dev eth0 parent 1:2 classid 1:13 htb rate 4kbit ceil
> 512kbit burst 2k
> tc class add dev eth0 parent 1:2 classid 1:15 htb rate 4kbit ceil
> 512kbit burst 2k
> tc class add dev eth0 parent 1:2 classid 1:17 htb rate 4kbit ceil
> 512kbit burst 2k
> #mark voip class
> tc filter add dev eth0 parent 1: protocol ip prio 1 handle 2 fw classid 1:12
> tc filter add dev eth0 parent 1: protocol ip prio 1 handle 4 fw classid 1:14
> tc filter add dev eth0 parent 1: protocol ip prio 1 handle 6 fw classid 1:16
> tc filter add dev eth0 parent 1: protocol ip prio 1 handle 8 fw classid 1:18
> tc filter add dev eth0 parent 1: protocol ip prio 1 handle 10 fw classid
> 1:20
> #mark staff class
> tc filter add dev eth0 parent 1: protocol ip prio 1 handle 1 fw classid 1:11
> tc filter add dev eth0 parent 1: protocol ip prio 1 handle 3 fw classid 1:13
> tc filter add dev eth0 parent 1: protocol ip prio 1 handle 5 fw classid 1:15
> tc filter add dev eth0 parent 1: protocol ip prio 1 handle 7 fw classid 1:17
> #add qdisc discipline voip
> tc qdisc add dev eth0 parent 1:12 handle 32: sfq perturb 10
> tc qdisc add dev eth0 parent 1:14 handle 34: sfq perturb 10
> tc qdisc add dev eth0 parent 1:16 handle 36: sfq perturb 10
> tc qdisc add dev eth0 parent 1:18 handle 38: sfq perturb 10
> tc qdisc add dev eth0 parent 1:20 handle 40: sfq perturb 10
> #add qdisc discipline staff
> tc qdisc add dev eth0 parent 1:11 handle 41: sfq perturb 10
> tc qdisc add dev eth0 parent 1:13 handle 43: sfq perturb 10
> tc qdisc add dev eth0 parent 1:15 handle 45: sfq perturb 10
> tc qdisc add dev eth0 parent 1:17 handle 47: sfq perturb 10
>
>
> _______________________________________________
> LARTC mailing list / LARTC@mailman.ds9a.nl
> http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
>
--
__o
_ \<_
(_)/(_)
Saludos de Julián
EA4ACL
-.-
Foro Wireless Madrid
http://opennetworks.rg3.net
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2002-03-26 13:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-26 13:07 [LARTC] htb+tc (protocol priority) George Tsuladze
2002-03-26 13:41 ` Julián Muñoz [this message]
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=marc-lartc-101715025402488@msgid-missing \
--to=jmunoz@telefonica.net \
--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.