Skip to contentSkip to conversation

tc filter priority

LARTC Glaucius Djalma Pereira Junior 3 participants 3 messages Jun 9, 2005 – Jun 10, 2005

lore
Share & tools
lore
#0 lore raw

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

Signature · 6 lines
Glaucius Djalma Pereira Junior
[email protected]
_______________________________________________
LARTC mailing list
[email protected]
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
#1 lore raw

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

Quoted 27 lines · Glaucius Djalma Pereira Junior

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

Quoted 8 lines

--
Glaucius Djalma Pereira Junior
[email protected]
_______________________________________________
LARTC mailing list
[email protected]
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

_______________________________________________
LARTC mailing list
[email protected]
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

#2 lore raw
In reply to Glaucius Djalma Pereira Junior
Quoted 8 lines · Glaucius Djalma Pereira Junior

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

Quoted 6 lines

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 ?

I do believe that if you add filter by filter with the same prio to the same parent -- they'll have sequential IDs (their "fh" in "tc filter show .."). And I believe they will be passed (checked) ID by ID sequentially.

So, in the example above, first filter will filter the packet to 1:$RULE.

At least I relied upon that often and haven't been ashamed :-)

Quoted 7 lines

best regards

Signature · 2 lines
Glaucius Djalma Pereira Junior
[email protected]
Signature · 9 lines
  _,-=._              /|_/|
  `-.}   `=._,.-=-._.,  @ @._,
     `._ _,-.   )      _,.-'
        `    G.m-"^m`m'        Dmytro O. Redchuk

_______________________________________________
LARTC mailing list
[email protected]
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc