tc filter add dev eth0 parent 1:0 protocol ip prio 1 u32 match ip dport 22 0xffff flowid 1:20
tc filter add dev eth0 parent 1:0 protocol ip prio 1 u32 match ip dport 23 0xffff flowid 1:20
tc filter add dev eth0 parent 1:20 protocol ip prio 1 u32 match ip dport 22 0xffff flowid 20:1
tc filter add dev eth0 parent 1:20 protocol ip prio 1 u32 match ip dport 23 0xffff flowid 20:3
I imagine what you actually want to do would be differently. have some set of filters that define what goes into 1:20, then you'll need a set of filters for 1:20 specifying where in that qdisc they should go.
- Jody
On 11/3/05, Andreas Klauer <Andreas.Klauer@xxxxxxxxxxxxxx> wrote:
On Thursday 03 November 2005 18:52, Michael Davidson wrote:
> tc filter add dev eth0 parent 1:0 protocol ip prio 1 u32 match ip dport
> 22 0xffff flowid 20:1
> tc filter add dev eth0 parent 1:0 protocol ip prio 1 u32 match ip dport
> 23 0xffff flowid 20:3
Do filters actually work in between different qdiscs?
I use HTB & PRIO also, but my filter puts packets from the HTB qdisc to the
HTB leaf class first, and then another filter puts packets from the PRIO
qdisc in the correct PRIO band.
HTH
Andreas
_______________________________________________
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
