From: George Alexandru Dragoi <waruiinu@gmail.com>
To: lartc@vger.kernel.org
Subject: [LARTC] What is wrong here?
Date: Tue, 30 Nov 2004 11:18:52 +0000 [thread overview]
Message-ID: <3063e5041130031811e3a20f@mail.gmail.com> (raw)
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
I wonder, where is the problem?
Thanks in advance
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next reply other threads:[~2004-11-30 11:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-30 11:18 George Alexandru Dragoi [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-12-21 4:17 [LARTC] What is wrong here? gypsy
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=3063e5041130031811e3a20f@mail.gmail.com \
--to=waruiinu@gmail.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