From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nataniel Klug Date: Tue, 04 Apr 2006 18:59:16 +0000 Subject: Re: [LARTC] Another question (now about u32) Message-Id: <4432C204.8030302@cnett.com.br> List-Id: References: <4432B431.7070104@cnett.com.br> In-Reply-To: <4432B431.7070104@cnett.com.br> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: lartc@vger.kernel.org Jody, Tryed, not working, same error: [root@ns1 ~]# tc filter add dev eth1 parent 1:0 protocol ip prio 1 u32 match ip sport 80 0xffff flowid 1:10 RTNETLINK answers: Invalid argument We have an error talking to the kernel Att, Nataniel Klug Jody Shumaker escreveu: > On 4/4/06, Nataniel Klug wrote: > >> Hello all, >> >> I am trying to match some conections using u32 but I tryed this: >> >> [root@ns1 ~]# tc filter add dev eth1 parent 1:0 protocol ip prio 1 u32 >> match ip src 0/0 match ip dst 0/0 match ip sport 80 0xffff flowid 1:10 >> RTNETLINK answers: Invalid argument >> We have an error talking to the kernel >> [root@ns1 ~]# >> >> > > Just a quick guess, but why are you bothering with this: match ip src > 0/0 match ip dst 0/0 > It's very likely that is causing the invalid argument error, and > doesn't seem necassary at all. Should at least try the more > simplified command: > tc filter add dev eth1 parent 1:0 protocol ip prio 1 u32 match ip > sport 80 0xffff flowid 1:10 > > - Jody > > _______________________________________________ LARTC mailing list LARTC@mailman.ds9a.nl http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc