search for: bkt

...s strange. Maybe I''m missing some options to TC? Thanks, Mindaugas # ./bin/tc -s -d filter show dev eth0 filter parent 1: protocol ip pref 1 u32 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 flowid 1:10 match d5e2b800/fffffe00 at 12 filter parent 1: protocol ip pref 1 u32 fh 800::801 order 2049 key ht 800 bkt 0 flowid 1:11 match d5e28af0/fffffff8 at 12 filter parent 1: protocol ip pref 1 u32 fh 800::802 order 2050 key ht 800 bkt 0 flowid 1:11 match d5e28af8/fffffffc at 12 filte...

...ped 0, overlimits 0) class prio 1:3 parent 1: Sent 0 bytes 0 pkts (dropped 0, overlimits 0) tc -s -d filter show dev eth0 filter parent 1: protocol ip pref 1 u32 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 flowid 1:1 (rule hit 45901 success 3595) match 00100000/00ff0000 at 0 (success 3595 ) filter parent 1: protocol ip pref 1 u32 fh 800::801 order 2049 key ht 800 bkt 0 flowid 1:1 (rule hit 42306 success 0) match 00120000/00ff0000 at 0 (success 0 ) filter parent 1: protocol ip pref 1 u32 fh 80...

...r 2 can get close to 256kbit from both networks in same time. But when I try to show filters I get: # tc filter ls dev eth0 filter parent 2: protocol ip pref 1 u32 filter parent 2: protocol ip pref 1 u32 fh 802: ht divisor 1 filter parent 2: protocol ip pref 1 u32 fh 802::800 order 2048 key ht 802 bkt 0 flowid 2:2001 match c0a80001/ffffffff at 16 filter parent 2: protocol ip pref 1 u32 fh 802::801 order 2049 key ht 802 bkt 0 flowid 2:2002 match c0a80002/ffffffff at 16 filter parent 2: protocol ip pref 1 u32 fh 801: ht divisor 1 filter parent 2: protocol ip pref 1 u32 fh 801::800 order 2048 k...

...; 1.1.1.10 flowid 1:130 The output of "tc -d filter show dev eth0" makes sense to me and looks like this: filter parent 1: protocol ip pref 130 u32 filter parent 1: protocol ip pref 130 u32 fh 800: ht divisor 1 filter parent 1: protocol ip pref 130 u32 fh 800::800 order 2048 key ht 800 bkt 0 flowid 1:130 match 0101010a/ffffffff at 16 If I add a third class and a filter for it, things start looking weird to me: # tc filter add dev eth0 protocol ip parent 1:0 prio 131 u32 match ip dst 1.1.1.11 \ > flowid 1:131 # tc class add dev eth0 parent 1: classid 1:132 htb rate 1Mbit ceil 1...

...sociated qdisc). The "empty" filter looks like this: filter parent 1: protocol ip pref 5 u32 filter parent 1: protocol ip pref 5 u32 fh 2: ht divisor 256 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: (rule hit 0 success 0) match 00000000/00000000 at 12 (success 0 ) hash mask 000000ff at 16 I''m adding the hash entries dynamically, as users get attacched to the system (this is a dynamic PPPoE access concentrator). tc filter add dev imq0 protocol ip parent 1:0 prio 5...

...xff flowid 13E:1 ##### Command show filter shows all three filters under all three priority''s -bash-2.05b# tc filter show dev eth1 parent 13E: filter protocol ip pref 1 u32 filter protocol ip pref 1 u32 fh 801: ht divisor 1 filter protocol ip pref 1 u32 fh 801::800 order 2048 key ht 801 bkt 0 flowid 13e :2 match 00020000/00ff0000 at 8 filter protocol ip pref 1 u32 fh 800: ht divisor 1 filter protocol ip pref 1 u32 fh 800::800 order 2048 key ht 800 bkt 0 flowid 13e :2 match 00010000/00ff0000 at 8 filter protocol ip pref 1 u32 fh 800::801 order 2049 key ht 800 bkt 0 flowid 13e :1...

...0x28 classid 1:3 PREF 1 = PRIO 1 filter parent 1: protocol ip pref 49151 u32 PREF 49151 = PRIO 0 !! then PRIO 0 has low prio that PRIO 1. filter parent 1: protocol ip pref 49151 u32 fh 802: ht divisor 1 filter parent 1: protocol ip pref 49151 u32 fh 802::800 order 2048 key ht 802 bkt 0 flowid 1:1020 match ac100a0c/ffffffff at 12 filter parent 1: protocol ip pref 49151 u32 fh 801: ht divisor 1 filter parent 1: protocol ip pref 49151 u32 fh 801::800 order 2048 key ht 801 bkt 0 flowid 1:1010 match ac100a0b/ffffffff at 12 filter parent 1: protocol ip pref 49151 u32 fh 800: ht d...

...ed 0, overlimits 0) lended: 0 borrowed: 0 giants: 0 tokens: 18187 ctokens: 18187 Filter statistics: -------------------- filter parent 1: protocol ip pref 1 u32 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 flowid 60: match c129cb80/ffffff80 at 16 filter parent 1: protocol ip pref 1 u32 fh 800::801 order 2049 key ht 800 bkt 0 flowid 40: match c129cb2a/ffffffff at 16 filter parent 1: protocol ip pref 1 u32 fh 800::802 order 2050 key ht 800 bkt 0 flowid 10: match c129cb00/ffffffe0 at 16 filter p...

...27491 bytes 166 pkts (dropped 0, overlimits 0) -- and perhaps more interesting is tc filter show dev eth1 (eth1=upstream) filter parent 1: protocol ip pref 1 u32 filter parent 1: protocol ip pref 1 u32 fh 802: ht divisor 1 filter parent 1: protocol ip pref 1 u32 fh 802::800 order 2048 key ht 802 bkt 0 flowid 122: match 00060000/00ff0000 at 8 match 00100000/00ff0000 at nexthdr+12 match 00000000/0000ffc0 at 0 filter parent 1: protocol ip pref 1 u32 fh 801: ht divisor 1 filter parent 1: protocol ip pref 1 u32 fh 801::800 order 2048 key ht 801 bkt 0 flowid 121: match 00100000/00ff0000 at 0...

...p src <ip net> match ip protocol 50 0xff flowid 1:22 # tc -s filter show dev eth0 ---------------------------------- filter parent 1: protocol ip pref 2 u32 filter parent 1: protocol ip pref 2 u32 fh 800: ht divisor 1 filter parent 1: protocol ip pref 2 u32 fh 800::802 order 2050 key ht 800 bkt 0 flowid 1:21 (rule hit 428 success 426) match c0000000/e0000000 at 16 (success 426 ) match 00000000/00000000 at 12 (success 426 ) filter parent 1: protocol ip pref 49151 u32 filter parent 1: protocol ip pref 49151 u32 fh 803: ht divisor 1 filter parent 1: protocol ip pref 49151 u32 fh 803::80...

...ts: 0 tokens: 103424 ctokens: 103424 Also you can see below tc filter output [root@fwr router]# tc filter show dev eth0 filter parent 1: protocol ip pref 1 u32 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 flowid 1:21 match ac12054a/ffffffff at 16 filter parent 1: protocol ip pref 1 u32 fh 800::801 order 2049 key ht 800 bkt 0 flowid 1:22 match c18c3996/ffffffff at 16 filter parent 1: protocol ip pref 1 u32 fh 800::802 order 2050 key ht 800 bkt 0 flowid 1:23 match c18c395a/ffffffff at 16 fi...

...he code that you had pointed out to me and I think my thinking is wrong on this. [root@RL1 root]# tc -s filter ls dev eth0 filter parent 1: protocol ip pref 10 u32 filter parent 1: protocol ip pref 10 u32 fh 4: ht divisor 256 filter parent 1: protocol ip pref 10 u32 fh 4:ba:800 order 2048 key ht 4 bkt ba flowid 1:65 match 0a0101ba/ffffffff at 16 I would guess that my problem start here where it is not linking back to 3? maybe? filter parent 1: protocol ip pref 10 u32 fh 4:fc:800 order 2048 key ht 4 bkt fc flowid 1:65 match 0a0101fc/ffffffff at 16 filter parent 1: protocol ip pref 10 u32 fh...

Hi, How can I delete an existing filter? Is it possible? I tried different combinations of tc commands but, while manage to delete an existing qdisc or class, I wasn''t able to find a way to delete an existing filter. The tc man page doesn''t even list the del command in the synopsis. tc filter [ add | change | replace ] \ dev DEV [ parent qdisc-id | root ] \

----- Original Message ----- From: Michał Joachimiak To: lartc@mailman.ds9a.nl Sent: Tuesday, July 20, 2004 3:45 PM Subject: HTB - Really Big problem Hello everybody! Since week i dig lists and www and can''t find solution for my problem. I''m using HTB 3.13 kernel 2-4-25 smp iptables 1.2.9. I''ve got situation like this: LAN------Linux Box(routing only)------- Linux

I am wondering whether the commands ''tc filter change'' and ''tc filter replace'' are working. Googling around revealed a few emails on the LARTC stating that unfoirtunately they do not work. A quick check showed that they are still not implemented (properly). Some propose a solution to build a second tree of filters and apply the 2nd one when a need for it

...so if I try to see the actual loaded filters by TC I get this: =========================================================== filter parent 1: protocol ip pref 1 u32 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 flowid 1:10 match c0a801f0/ffffffff at 12 match 00004e20/0000ffff at 20 filter parent 1: protocol ip pref 1 u32 fh 800::801 order 2049 key ht 800 bkt 0 flowid 1:11 match c0a801f0/ffffffff at 12 match 00004e21/0000ffff at 20 filter parent 1: protocol ip pref 1 u32 fh 800::802 order 2050 key ht 8...

...d 1:0x26 1. What is the precise syntax for deleting a tc filter? tc show gives me this output: [root@thor htb]# tc filter show dev eth0 parent 1:20 filter protocol ip pref 10 u32 filter protocol ip pref 10 u32 fh 801: ht divisor 1 filter protocol ip pref 10 u32 fh 801::800 order 2048 key ht 801 bkt 0 flowid 1:26 match c0a80002/ffffffff at 16 filter protocol ip pref 10 u32 fh 800: ht divisor 1 filter protocol ip pref 10 u32 fh 800::800 order 2048 key ht 800 bkt 0 flowid 1:25 match c0a80002/ffffffff at 16 How do I delete flowid 1:26 for example? Everything I tried returns an error messa...

...with the library (no error occured) but the filter is not active. If I run "tc filter show dev eth0" I get: filter parent 1: protocol ip pref 100 u32 filter parent 1: protocol ip pref 100 u32 fh 800: ht divisor 1 filter parent 1: protocol ip pref 100 u32 fh 800::800 order 2048 key ht 800 bkt 0 *flowid 1:20 match 00160000/ffff0000 at 20 filter parent 1: protocol ip pref 100 u32 fh 800::801 order 2049 key ht 800 bkt 0 *flowid 1:11 match 00160000/ffff0000 at 20 I don''t know what''s the meaning of the "*" before flowid is. Because if I add a filter with tc t...

PATCH 1 ======= On my machine tc does not parse filter "sample" for the u32 filter. Eg: tc filter add dev eth2 parent 1:0 protocol ip prio 1 u32 ht 801: \ classid 1:3 \ sample ip protocol 1 0xff match ip protocol 1 0xff Illegal "sample" The reason is a missing memset. This patch fixes it. diff -Nur iproute-20051007.keep/tc/f_u32.c iproute-20051007/tc/f_u32.c

...t "tc filter" sintax. If I give "tc -s -d filter sh dev eth0" command, then the output is like below : filter parent 1: protocol ip pref 1 u32 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 flowid 1:2 (rule hit 21553629 success 37907) match 00160000/ffff0000 at 20 (success 37907 ) ... My question is : 1. What is "fh 800:" and "fh 800::800" mean ? 2. How I change the value "800" in "fh 800::800" ? I''m guessing this is default v...