I had a similar problem. My conclusion was that u32 match ip dst does not work in 2.4.22.
Do you use 2.4.22? If so, try upgrade to 2.4.23-rc1 if you can..
raptor wrote:
Hi,
I have config like this ,... but all traffic goes to the default class 1:4, WHY ? What I' doing wrong... filters are attached to the root !
tc qdisc add dev eth0 handle 1:0 root htb default 4
tc class add dev eth0 parent 1:0 classid 1:4 htb rate 55kbit ceil 55kbit prio 7 <--default class
tc class add dev eth0 parent 1:0 classid 1:1 htb rate 20Mbit tc qdisc add dev eth0 handle 2:0 parent 1:1 htb
tc class add dev eth0 parent 2:0 classid 2:3 htb rate 30kbit ceil 30kbit tc qdisc add dev eth0 handle 3:0 parent 2:3 sfq tc filter add dev eth0 parent 1:0 protocol ip prio 2 u32 match ip dst x.x.x.X classid 2:3
tc class add dev eth0 parent 2:0 classid 2:5 htb rate 30kbit ceil 30kbit tc qdisc add dev eth0 handle 4:0 parent 2:5 sfq tc filter add dev eth0 parent 1:0 protocol ip prio 2 u32 match ip dst x.x.x.X classid 2:5 tc filter add dev eth0 parent 1:0 protocol ip prio 2 u32 match ip dst x.x.x.X classid 2:5
...... and many like this
_______________________________________________
LARTC mailing list / LARTC@xxxxxxxxxxxxxxx
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
_______________________________________________ LARTC mailing list / LARTC@xxxxxxxxxxxxxxx http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
