LARTC - Aug 2006 - tc filter don''t match packets

Hi,

I have problem with this simple script:

#!/bin/bash
if [ "$1" == "del" ]; then
tc qdisc del dev eth0 root handle 1: htb default 10
exit
fi
tc qdisc add dev eth0 root handle 1: htb default 10
tc class add dev eth0 parent 1: classid 1:1 htb rate 800kbit ceil 900kbit
tc class add dev eth0 parent 1:1 classid 1:10 htb rate 300kbit ceil 600kbit
tc class add dev eth0 parent 1:1 classid 1:11 htb rate 100kbit ceil 800kbit
tc qdisc add dev eth0 parent 1:11 handle 11: pfifo limit 5
tc filter add dev eth0 parent 1:11 protocol ip prio 1 u32 match ip dport 80
0xffff flowid 1:11

unfortunaly when I start that scripts tc filter don''t match packets
with
dport 80!

Output of tc -s -d class show dev eth0 is:

class htb 1:11 parent 1:1 leaf 11: prio 0 quantum 1000 rate 10000bit ceil
100000bit burst 1605b/8 mpu 0b overhead 0b cburst 1650b/8 mpu 0b overhead 0b
level 0
 Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0)
 rate 0bit 0pps backlog 0b 0p requeues 0
 lended: 0 borrowed: 0 giants: 0
 tokens: 1284000 ctokens: 132000

class htb 1:1 root rate 800000bit ceil 900000bit burst 2000b/8 mpu 0b
overhead 0b cburst 2Kb/8 mpu 0b overhead 0b level 7
 Sent 320 bytes 5 pkt (dropped 0, overlimits 0 requeues 0)
 rate 0bit 0pps backlog 0b 0p requeues 0
 lended: 0 borrowed: 0 giants: 0
 tokens: 19360 ctokens: 17654

class htb 1:10 parent 1:1 prio 0 quantum 3750 rate 300000bit ceil 600000bit
burst 1749b/8 mpu 0b overhead 0b cburst 1899b/8 mpu 0b overhead 0b level 0
 Sent 320 bytes 5 pkt (dropped 0, overlimits 0 requeues 0)
 rate 0bit 0pps backlog 0b 0p requeues 0
 lended: 5 borrowed: 0 giants: 0
 tokens: 44960 ctokens: 24480

I use SuSE 10.1 with 2.6.16 .

Have you any sugestion?


_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

Hi,

in this simple case you must attach the filter to the root:

[...]
> tc qdisc add dev eth0 root handle 1: htb default 10 
[...]
> tc filter add dev eth0 parent 1:11 protocol ip prio 1 u32 match ip 
> dport 80 0xffff flowid 1:11
[...]

Should be:

tc filter add dev eth0 parent 1:0 protocol ip prio 1 u32 match ip dport 80 
0xffff flowid 1:11


The traffic gets enqueued traversing the filters attached to each node but 
starting at the root node. You must provide a way to arrive to a leaf.

In man tc-htb it says:

       "When enqueueing a packet, HTB starts at the root and uses various 
meth-
       ods to determine which class should receive the data.

       In the absence of uncommon configuration options, the process is 
rather
       easy.  At each node we look for an instruction,  and  then  go  to 
the
       class  the  instruction  refers  us  to. If the class found is a 
barren
       leaf-node (without children), we enqueue the packet there. If it is 
not
       yet  a  leaf  node, we do the whole thing over again starting from 
that
       node.

       The following actions are performed, in order at each  node  we 
visit,
       until one sends us to another node, or terminates the process.

       (i)    Consult filters attached to the class. If sent to a 
leafnode, we
              are done.  Otherwise, restart.

       (ii)   If none of the above returned with an  instruction,  enqueue 
 at
              this node.

       This  algorithm makes sure that a packet always ends up somewhere, 
even
       while you are busy building your configuration."


In your case, the packets arrive to the root node to get enqueed but due 
to that there is no filter attached it will get to the default 10.
I hope this helps,

Regards,
Eric Janz 

--

ADVERTENCIA LEGAL
El contenido de este correo es confidencial y dirigido unicamente a su
destinatario. Para acceder a su clausula de privacidad consulte
http://www.barceloviajes.com/privacy

LEGAL ADVISORY
This message is confidential and intended only for the person or entity to which
it is addressed. In order to read its privacy policy consult it at
http://www.barceloviajes.com/privacy


_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc