From: Evgeni Gechev <etg@setcom.bg>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] u32 and iptables do not work together
Date: Fri, 07 Apr 2006 19:54:43 +0000 [thread overview]
Message-ID: <4436C383.5060509@setcom.bg> (raw)
In-Reply-To: <4436AEB8.1070300@cnett.com.br>
Nataniel Klug wrote:
> Andreas,
>
> This is not the problem becouse if I disable the rules I am using, and
> use other script just with rules using fwmark them the other script
> works fine.
>
> Att,
>
> Nataniel Klug
>
> Andreas Klauer escreveu:
>> On Fri, Apr 07, 2006 at 03:26:00PM -0300, Nataniel Klug wrote:
>>
>>> RTNETLINK answers: Invalid argument
>>> We have an error talking to the kernel
>>>
>>
>> This message usually translates to: 'tc understood your syntax just
>> fine, and tried to tell the kernel about it, but the kernel did not
>> understand, most likely because it does not support this feature.'
>>
>> Do you have 'Netfilter marks support' enabled?
>> (Just a guess, may be a different setting)
>>
>> Regards
>> Andreas Klauer
>>
>>
> _______________________________________________
> LARTC mailing list
> LARTC@mailman.ds9a.nl
> http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
>
>
tc filter add dev DEVICE parent M:N protocol ip prio 100 u32 match ip
dst A.B.C.D/M match mark 0x0001 0xffff flowid P:Q
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
next prev parent reply other threads:[~2006-04-07 19:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-07 18:26 [LARTC] u32 and iptables do not work together Nataniel Klug
2006-04-07 18:45 ` Andreas Klauer
2006-04-07 19:09 ` Nataniel Klug
2006-04-07 19:54 ` Evgeni Gechev [this message]
2006-04-07 21:10 ` Jody Shumaker
2006-04-08 10:03 ` Piotr Chytla
2006-04-08 11:21 ` Nataniel Klug
2006-04-08 13:18 ` Piotr Chytla
2006-04-08 13:37 ` Andreas Klauer
2006-04-10 16:23 ` 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=4436C383.5060509@setcom.bg \
--to=etg@setcom.bg \
--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