All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Victor" <victor@ambra.ro>
To: lartc@vger.kernel.org
Subject: [LARTC] filter
Date: Wed, 08 Oct 2003 22:46:53 +0000	[thread overview]
Message-ID: <marc-lartc-106565321305922@msgid-missing> (raw)

The difrence betwen these 2 configurations is only the prio parameter from
the second filter, from each configutation.
(tc filter add dev eth0 parent 1: prio 5 protocol ip u32 ht 800:: match ip
src 80.97.24.0/24 hashkey mask 0x000000ff at 12 link 2:)

Configuration 1

tc qdisc add dev eth0 root handle 1: htb
tc class add dev eth0 parent 1: classid 1:1 htb rate 500Kbit prio 1
quantum 2000
tc class add dev eth0 parent 1:1 classid 1:201 htb rate 4Kbit ceil 500Kbit
prio 0 quantum 2000
tc filter add dev eth0 parent 1: prio 1 handle 2: protocol ip u32 divisor 256
tc filter add dev eth0 parent 1: prio 5 protocol ip u32 ht 800:: match ip
src 80.97.24.0/24 hashkey mask 0x000000ff at 12 link 2:
tc filter add dev eth0 prio 1 protocol ip u32 ht 2:01 match ip src
80.97.24.1 flowid 1:201

Configuration 2

tc qdisc add dev eth0 root handle 1: htb
tc class add dev eth0 parent 1: classid 1:1 htb rate 500Kbit prio 1
quantum 2000
tc class add dev eth0 parent 1:1 classid 1:201 htb rate 4Kbit ceil 500Kbit
prio 0 quantum 2000
tc filter add dev eth0 parent 1: prio 1 handle 2: protocol ip u32 divisor 256
tc filter add dev eth0 parent 1: prio 1 protocol ip u32 ht 800:: match ip
src 80.97.24.0/24 hashkey mask 0x000000ff at 12 link 2:
tc filter add dev eth0 prio 1 protocol ip u32 ht 2:01 match ip src
80.97.24.1 flowid 1:201

Configuration 1
tc filter show dev eth1
shows the next lines:
filter parent 1: protocol ip pref 1 u32
filter parent 1: protocol ip pref 1 u32 fh 801: ht divisor 1
filter parent 1: protocol ip pref 1 u32 fh 2: ht divisor 256
filter parent 1: protocol ip pref 1 u32 fh 2:1:800 order 2048 key ht 2 bkt
1 flowid 1:201
  match 50611801/ffffffff at 12
filter parent 1: protocol ip pref 1 u32 fh 800: ht divisor 1
filter parent 1: protocol ip pref 1 u32 fh 800::800 order 2048 key ht 800
bkt 0 link 2:
  match 50611800/ffffff00 at 12
    hash mask 000000ff at 12
filter parent 1: protocol ip pref 5 u32
filter parent 1: protocol ip pref 5 u32 fh 801: ht divisor 1
filter parent 1: protocol ip pref 5 u32 fh 2: ht divisor 256
filter parent 1: protocol ip pref 5 u32 fh 2:1:800 order 2048 key ht 2 bkt
1 flowid 1:201
  match 50611801/ffffffff at 12
filter parent 1: protocol ip pref 5 u32 fh 800: ht divisor 1
filter parent 1: protocol ip pref 5 u32 fh 800::800 order 2048 key ht 800
bkt 0 link 2:
  match 50611800/ffffff00 at 12
    hash mask 000000ff at 12



Configuration 1
tc filter show dev eth1
shows the next lines:

filter parent 1: protocol ip pref 1 u32
filter parent 1: protocol ip pref 1 u32 fh 2: ht divisor 256
filter parent 1: protocol ip pref 1 u32 fh 2:1:800 order 2048 key ht 2 bkt
1 flowid 1:201
  match 50611801/ffffffff at 12
filter parent 1: protocol ip pref 1 u32 fh 800: ht divisor 1
filter parent 1: protocol ip pref 1 u32 fh 800::800 order 2048 key ht 800
bkt 0 link 2:
  match 50611800/ffffff00 at 12
    hash mask 000000ff at 12

Why the configutaion1 has many filters than configuration2?
How can the prio paramenter influence this?
What is the range for the prio parameter in the filter context?
Thank you.

Victor


-----------------------------------------
This email was sent using SquirrelMail.
   "Webmail for nuts!"
http://squirrelmail.org/


Random Thought:
--------------
Integrity has no need for rules.
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

             reply	other threads:[~2003-10-08 22:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-08 22:46 Victor [this message]
2003-10-09  5:08 ` [LARTC] filter Catalin BOIE
2003-10-09 16:40 ` Stef Coene
2003-10-10  5:09 ` Catalin BOIE
2003-10-10 19:49 ` Stef Coene

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-106565321305922@msgid-missing \
    --to=victor@ambra.ro \
    --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.