> That's an interesting way to mark (or should I say classify) packets with > IPTABLES. The one I'm using currently (and which I forgot to add to my > initial query) was this: > $IPTABLES -t mangle -A PREROUTING -s 192.168.200.163 -j MARK --set-mark 1 To be honest, I use the MARK target as well. I just thought the CLASSIFY option would be easier in your situation because (I think) it saves an extra tc rule to classify the packets. If you're using MARK you need a rule telling tc to classify the packets that are MARKed. I'm not sure if what you are using is correct; I use the following (you'll need to edit appropriately): tc filter add dev ifb0 parent 1:0 prio 0 protocol ip handle 10 fw \ flowid 1:10 I'm getting out of my depth here so may be wrong, but as I understand it 'handle' is the MARK, flowid is what it should be classified as. Andy _______________________________________________ LARTC mailing list LARTC@xxxxxxxxxxxxxxx http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
