All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nataniel Klug <nata@cnett.com.br>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Another question (now about u32)
Date: Tue, 04 Apr 2006 18:59:16 +0000	[thread overview]
Message-ID: <4432C204.8030302@cnett.com.br> (raw)
In-Reply-To: <4432B431.7070104@cnett.com.br>

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 <nata@cnett.com.br> 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

  parent reply	other threads:[~2006-04-04 18:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-04 18:00 [LARTC] Another question (now about u32) Nataniel Klug
2006-04-04 18:52 ` Jody Shumaker
2006-04-04 18:59 ` Nataniel Klug [this message]
2006-04-04 19:06 ` Nataniel Klug

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4432C204.8030302@cnett.com.br \
    --to=nata@cnett.com.br \
    --cc=lartc@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.