[LARTC] can't understand strange PRIO behaviour

Andreas Klauer Andreas.Klauer@metamorpher.de
Wed Feb 2 03:50:43 CET 2005


On Wednesday 02 February 2005 04:46, Viktor Horvath wrote:
> tc qdisc add dev ppp0 root handle 1: prio bands 2 priomap 0 0 0 0 0 0 0
> 0 0 0 0 0 0 0 0 0
> # Create the two PRIO sub-qdiscs
> tc qdisc add dev ppp0 parent 1:1 handle 10: prio bands 2 priomap 0 0 0 0
> 0 0 0 0 0 0 0 0 0 0 0 0
> tc qdisc add dev ppp0 parent 1:2 handle 20: prio bands 2 priomap 0 0 0 0
> 0 0 0 0 0 0 0 0 0 0 0 0
[...]
> # catch-all
> tc filter add dev ppp0 protocol ip parent 1: prio 2 u32 match ip src
> 0.0.0.0/0 flowid 10:2

I don't know if it is a bug or whatever, but PRIO doesn't like alien 
filters. You may only put traffic into a class of the qdisc you attached 
the filter to. At least this is how it works on my machine (2.4 kernel).

So using these filter rules should work as expected:

tc filter add dev ppp0 protocol ip parent 1: prio 2 u32 match ip src 
0.0.0.0/0 flowid 1:1
tc filter add dev ppp0 protocol ip parent 10: prio 2 u32 match ip src 
0.0.0.0/0 flowid 10:2

HTH
Andreas



More information about the LARTC mailing list