From mboxrd@z Thu Jan 1 00:00:00 1970 From: Flemming Frandsen Date: Tue, 10 Jan 2006 23:19:07 +0000 Subject: Re: [LARTC] tc filter add ... fw returns RTNETLINK answers: Invalid Message-Id: <43C440EB.7010508@nrvissing.net> List-Id: References: <43C429E5.3070007@nrvissing.net> In-Reply-To: <43C429E5.3070007@nrvissing.net> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: lartc@vger.kernel.org Muthukumar S wrote: >On 1/10/06, Flemming Frandsen wrote: > > >>When I run this: >>tc filter add dev eth0 parent 1: protocol ip prio 1 handle 1 fw >> >>I get: >>RTNETLINK answers: Invalid argument >> >> > >You are missing the flowid. For example >tc filter add dec eth0 parent 1: protocol ip prio 1 handle 1 fw flowid 1:42 > > No, no I'm not, I'm using iptables like this: ... iptables -t mangle -A from-dsl-eth1 -d 10.48.6.0/24 -j MARK --set-mark 0x14806 iptables -t mangle -A from-dsl-eth1 -d 10.48.6.0/24 -j RETURN tc class add dev eth1 parent 1:1 classid 1:4806 htb rate 1200mbit burst 15k prio 10 tc qdisc add dev eth1 parent 1:4806 sfq perturb 21 ... That means that packets with --set-mark 0x14806 get put into classid 1:4806 The RETURN rule means that I can have a -j LOG at the end of my chain to figure out what didn't get matched, I just wish you could say -j MARK,RETURN in the same rule. The funny thing that I realized after sending the original mail is that the shaper works, it classifies the traffic correctly, eventhough the tc filter command moans about an invalid argument. It would be very nice to either get a usable error message or have tc shut up about the non-error. _______________________________________________ LARTC mailing list LARTC@mailman.ds9a.nl http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc