Re: [LARTC] filter

[Catalin BOIE <util@deuroconsult.ro>]

Don't worry. It's tc fault (or maybe kernel).
The filters are once in the kernel but are showed no_of_prios_used times.

On Thu, 9 Oct 2003, Victor wrote:

> 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/
>

---
Catalin(ux) BOIE
catab@deuroconsult.ro
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/