Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: gypsy <gypsy@iswest.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] What is wrong here?
Date: Tue, 21 Dec 2004 04:17:14 +0000	[thread overview]
Message-ID: <41C7A3CA.98127727@iswest.com> (raw)

George Alexandru Dragoi wrote:
> 
>          Hello Everyone,
> 
> I have this weird problem. I have 2.6.10-rc2-mm3 kernel with u32
> compiled as module.  I have the cls_u32 module loaded. I have
> different binaryes of tc, the one from iproute packaged from debian
> sarge, the Kaber's one from trash.net, and also from another computer
> where u32 worked. When I run this:
> cyclops:~# /usr/local/sbin/tc filter add dev eth0 parent 6: protocol
> ip prio 4 u32  match ip src 1.1.1.1/32 classid 6:a000
>  I get
> RTNETLINK answers: Invalid argument

No, it is not a weird problem <g>.  I run it and get the same result.

The probability is that there is no "parent 6:" or that there is no
flowid/classid "6:a000".  It is also possible there is no eth0, meaning
your qdisc is on eth1.  I guess it could also be that 1.1.1.1/32 is not
a valid IP for that interface?

gypsy
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

             reply	other threads:[~2004-12-21  4:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-21  4:17 gypsy [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-11-30 11:18 [LARTC] What is wrong here? George Alexandru Dragoi

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=41C7A3CA.98127727@iswest.com \
    --to=gypsy@iswest.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox