From: "Jan Coppens" <Jan.Coppens@intec.rug.ac.be>
To: lartc@vger.kernel.org
Subject: [LARTC] tcindex filter
Date: Fri, 08 Mar 2002 09:51:46 +0000 [thread overview]
Message-ID: <marc-lartc-101561724932467@msgid-missing> (raw)
[-- Attachment #1: Type: text/plain, Size: 2141 bytes --]
Hi,
Can someone explain me what this script does?
tc qdisc del dev eth1 root
tc qdisc add dev eth1 root handle 1:0 cbq bandwidth 10mbit avpkt 1000
tc class add dev eth1 parent 1:0 classid 1:39 cbq bandwidth 256kbit rate 128kbit allot 1514 maxburst 20 avpkt 1000
tc class add dev eth1 parent 1:0 classid 1:40 cbq bandwidth 256kbit rate 128kbit allot 1514 maxburst 20 avpkt 1000
tc class add dev eth1 parent 1:0 classid 1:41 cbq bandwidth 256kbit rate 128kbit allot 1514 maxburst 20 avpkt 1000
tc class add dev eth1 parent 1:0 classid 1:47 cbq bandwidth 256kbit rate 128kbit allot 1514 maxburst 20 avpkt 1000
tc class add dev eth1 parent 1:0 classid 1:48 cbq bandwidth 256kbit rate 128kbit allot 1514 maxburst 20 avpkt 1000
tc class add dev eth1 parent 1:0 classid 1:49 cbq bandwidth 256kbit rate 128kbit allot 1514 maxburst 20 avpkt 1000
tc class add dev eth1 parent 1:0 classid 1:50 cbq bandwidth 256kbit rate 128kbit allot 1514 maxburst 20 avpkt 1000
tc filter add dev eth1 parent 1:0 protocol ip prio 1 handle 0 tcindex classid 1:50
tc filter add dev eth1 parent 1:0 protocol ip prio 39 handle 39 tcindex classid 1:39
tc filter add dev eth1 parent 1:0 protocol ip prio 40 handle 40 tcindex classid 1:40
tc filter add dev eth1 parent 1:0 protocol ip prio 41 handle 41 tcindex classid 1:41
tc filter add dev eth1 parent 1:0 protocol ip prio 47 handle 47 tcindex classid 1:47
tc filter add dev eth1 parent 1:0 protocol ip prio 48 handle 48 tcindex classid 1:48
tc filter add dev eth1 parent 1:0 protocol ip prio 49 handle 49 tcindex classid 1:49
I think it will devide the traffic in the different classes according to the tcindex value. However, the script doesn't use a dsmark qdisc, so the tcindex value should be set first with an ingress qdisc, right?
thx,
Jan
---
Jan Coppens
Ghent University - IMEC
Department of Information Technology (INTEC)
Broadband Communication Networks (IBCN)
Sint-Pietersnieuwstraat, 41
B-9000, Gent
Belgium
E-mail: Jan.Coppens@intec.rug.ac.be
Phone: +32 (0)9 267 35 90
Fax: +32 (0)9 267 35 99
[-- Attachment #2: Type: text/html, Size: 3526 bytes --]
reply other threads:[~2002-03-08 9:51 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=marc-lartc-101561724932467@msgid-missing \
--to=jan.coppens@intec.rug.ac.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 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.