I'm unsure on the order, it might be based on when they were added. However if you really want to be sure one gets used before the other then why don't you use different prio values? a filter with a lower prio value will get processed before ones with a higher value. If you want to guarentee one gets processed before another, then use prio as that's its whole purpose. - Jody On 6/9/05, Glaucius Djalma Pereira Junior <glaucius@xxxxxxxxx> wrote: > hi all > > friends > > has tc filter an priority of rules , like iptables, let me explain it : > > with iptables, when the packet find a rule to go, it doesnt see the > rest of rules, and how is the behavior of tc filter ?? > > see it : > > one packet from 10.10.10.1:2421 going to 11.11.11.1:110 what rule > above it will be shaped ?? > > 1 ) tc filter add dev eth0 protocol ip parent 1:0 prio 1 u32 match ip > src 10.10.10.10 match ip dst 11.11.11.1 flowid 1:$RULE > > 2 ) tc filter add dev eth0 protocol ip parent 1:0 prio 1 u32 match ip > src 10.10.10.1 match ip dport 110 0xffff flowid 1:$RULE > > the rules were created in this order : 1 and after 2 > > what rule the packet will be shaped ? > > best regards > > > -- > Glaucius Djalma Pereira Junior > glaucius@xxxxxxxxx > _______________________________________________ > LARTC mailing list > LARTC@xxxxxxxxxxxxxxx > http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc > _______________________________________________ LARTC mailing list LARTC@xxxxxxxxxxxxxxx http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
