From: "Jan Coppens" <Jan.Coppens@intec.rug.ac.be>
To: lartc@vger.kernel.org
Subject: [LARTC] Ultimate Traffic Conditioner
Date: Mon, 29 Apr 2002 09:20:21 +0000 [thread overview]
Message-ID: <marc-lartc-102007215217868@msgid-missing> (raw)
[-- Attachment #1: Type: text/plain, Size: 4223 bytes --]
Hi all,
When I try to run the ultimate traffic conditioner (cbq implementation), I get this strange output:
/tc# ./ultimate
/tc# tc filter show dev eth1
filter parent 1: protocol ip pref 10 u32
filter parent 1: protocol ip pref 10 u32 fh 803: ht divisor 1
filter parent 1: protocol ip pref 10 u32 fh 803::800 order 2048 key ht 803 bkt 0 flowid 1:20
match 00000000/00000000 at 16
filter parent 1: protocol ip pref 10 u32 fh 802: ht divisor 1
filter parent 1: protocol ip pref 10 u32 fh 802::800 order 2048 key ht 802 bkt 0 flowid 1:10
match 00060000/00ff0000 at 8
match 05000000/0f00ffc0 at 0
match 00100000/00ff0000 at 32
filter parent 1: protocol ip pref 10 u32 fh 801: ht divisor 1
filter parent 1: protocol ip pref 10 u32 fh 801::800 order 2048 key ht 801 bkt 0 flowid 1:10
match 00010000/00ff0000 at 8
filter parent 1: protocol ip pref 10 u32 fh 800: ht divisor 1
filter parent 1: protocol ip pref 10 u32 fh 800::800 order 2048 key ht 800 bkt 0 flowid 1:10
match 00100000/00ff0000 at 0
filter parent 1: protocol ip pref 11 u32
filter parent 1: protocol ip pref 11 u32 fh 803: ht divisor 1
filter parent 1: protocol ip pref 11 u32 fh 803::800 order 2048 key ht 803 bkt 0 flowid 1:20
match 00000000/00000000 at 16
filter parent 1: protocol ip pref 11 u32 fh 802: ht divisor 1
filter parent 1: protocol ip pref 11 u32 fh 802::800 order 2048 key ht 802 bkt 0 flowid 1:10
match 00060000/00ff0000 at 8
match 05000000/0f00ffc0 at 0
match 00100000/00ff0000 at 32
filter parent 1: protocol ip pref 11 u32 fh 801: ht divisor 1
filter parent 1: protocol ip pref 11 u32 fh 801::800 order 2048 key ht 801 bkt 0 flowid 1:10
match 00010000/00ff0000 at 8
filter parent 1: protocol ip pref 11 u32 fh 800: ht divisor 1
filter parent 1: protocol ip pref 11 u32 fh 800::800 order 2048 key ht 800 bkt 0 flowid 1:10
match 00100000/00ff0000 at 0
filter parent 1: protocol ip pref 12 u32
filter parent 1: protocol ip pref 12 u32 fh 803: ht divisor 1
filter parent 1: protocol ip pref 12 u32 fh 803::800 order 2048 key ht 803 bkt 0 flowid 1:20
match 00000000/00000000 at 16
filter parent 1: protocol ip pref 12 u32 fh 802: ht divisor 1
filter parent 1: protocol ip pref 12 u32 fh 802::800 order 2048 key ht 802 bkt 0 flowid 1:10
match 00060000/00ff0000 at 8
match 05000000/0f00ffc0 at 0
match 00100000/00ff0000 at 32
filter parent 1: protocol ip pref 12 u32 fh 801: ht divisor 1
filter parent 1: protocol ip pref 12 u32 fh 801::800 order 2048 key ht 801 bkt 0 flowid 1:10
match 00010000/00ff0000 at 8
filter parent 1: protocol ip pref 12 u32 fh 800: ht divisor 1
filter parent 1: protocol ip pref 12 u32 fh 800::800 order 2048 key ht 800 bkt 0 flowid 1:10
match 00100000/00ff0000 at 0
filter parent 1: protocol ip pref 13 u32
filter parent 1: protocol ip pref 13 u32 fh 803: ht divisor 1
filter parent 1: protocol ip pref 13 u32 fh 803::800 order 2048 key ht 803 bkt 0 flowid 1:20
match 00000000/00000000 at 16
filter parent 1: protocol ip pref 13 u32 fh 802: ht divisor 1
filter parent 1: protocol ip pref 13 u32 fh 802::800 order 2048 key ht 802 bkt 0 flowid 1:10
match 00060000/00ff0000 at 8
match 05000000/0f00ffc0 at 0
match 00100000/00ff0000 at 32
filter parent 1: protocol ip pref 13 u32 fh 801: ht divisor 1
filter parent 1: protocol ip pref 13 u32 fh 801::800 order 2048 key ht 801 bkt 0 flowid 1:10
match 00010000/00ff0000 at 8
filter parent 1: protocol ip pref 13 u32 fh 800: ht divisor 1
filter parent 1: protocol ip pref 13 u32 fh 800::800 order 2048 key ht 800 bkt 0 flowid 1:10
match 00100000/00ff0000 at 0
/tc#
As you can see, the script adds way to many u32 filters. I did some testing, and figured out the problem has something to do with the different priorities. when I give each u32 filter the same priority, I get the right number of filters.
Is this output correct? If not, what can be the problem?
thanks,
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: 5631 bytes --]
next reply other threads:[~2002-04-29 9:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-29 9:20 Jan Coppens [this message]
2002-04-29 9:32 ` [LARTC] Ultimate Traffic Conditioner bert hubert
2002-04-29 12:28 ` Jan Coppens
2002-04-29 13:55 ` Martin Devera
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-102007215217868@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.