----- Original Message ----- From: "Stef Coene" <stef.coene@docum.org> To: "Ronan LAVIEC" <ronan.laviec@club-internet.fr>; <lartc@mailman.ds9a.nl> Sent: Wednesday, January 08, 2003 7:32 PM Subject: Re: [LARTC] Incomprehensive problem with tc filter & mangle... > > # The rules that's didn't work, and I don't now why. > > $TC filter add dev $EXT_IFACE parent 1: protocol ip prio 15 \ > > handle 10 fw classid 1:10 > > $TC filter add dev $EXT_IFACE parent 1: protocol ip prio 20 \ > > handle 15 fw classid 1:10 > I don't think it's an issue, but you can try it without a prio parameter? > > Stef > > -- > > stef.coene@docum.org > "Using Linux as bandwidth manager" > http://www.docum.org/ > #lartc @ irc.oftc.net > It's always the same thing... Only the default setting seems to work. >From yesterday, I've tried with match ip src, and this also doesn't work. ($TC filter add dev $EXT_IFACE parent 1: protocol ip prio 15 u32 match ip src $PREFERED_IP flowid 1:10) I've tried to use mangle mark to do the same thing, and as every time always the default setting seems to work. I've tried another thing : I used some rules from a script found here : http://www.linux-france.org/prj/inetdoc/i/net/guides/Advanced-routing-Howto/ Advanced-routing-Howto.v0.9-15.html#ss15.8 So I used : $TC filter add dev $EXT_IFACE parent 1:0 protocol ip prio 10 u32 \ match ip tos 0x10 0xff flowid 1:10 $TC filter add dev $EXT_IFACE parent 1:0 protocol ip prio 10 u32 \ match ip protocol 1 0xff flowid 1:10 $TC filter add dev $EXT_IFACE parent 1: protocol ip prio 10 u32 \ match ip protocol 6 0xff \ match u8 0x05 0x0f at 0 \ match u16 0x0000 0xffc0 at 2 \ match u8 0x10 0xff at 33 \ flowid 1:10 In addition to my own rules.... And these three rules work, not mine. I really understand anything. What's wrong with my rules ? Ronan.
