From: Alexander Samad <alex@samad.com.au>
To: netfilter-devel@lists.netfilter.org
Subject: Re: MARK-Operations problems
Date: Thu, 8 Jul 2004 17:18:41 +1000 [thread overview]
Message-ID: <20040708071841.GE16285@samad.com.au> (raw)
In-Reply-To: <Pine.LNX.4.44.0407080852320.16639-100000@filer.marasystems.com>
[-- Attachment #1: Type: text/plain, Size: 1231 bytes --]
On Thu, Jul 08, 2004 at 08:57:51AM +0200, Henrik Nordstrom wrote:
> On Thu, 8 Jul 2004, Alexander Samad wrote:
>
> > Double checked this and I am pretty sure its pacthed all the right
> > modules are there (the ones that are created with the patch), the
> > strange bit is even a working command -j MARK --set-mark 0x01 fails with
> > the same error, but the unpatched iptables doesn't on the same patches
> > kernel
>
> The fact that the unpatched iptables works is a quite clear indication
> that the running kernel is not patched, at least not with the MARK
> operations patch.
>
> When iptables is built it is using the same headers as the kernel. If the
> headers used when building iptables is different from those used when
> building the running kernel then operations on matches/extensions will
> fail with size errors.
Okay will rebuild and retest!
>
> Another occation when such errors can happen is in special cases on 64-bit
> machines with split personality, with kernel running in 64-bits and
> userspace in 32-bits. This is maybe seen on SPARC-64 and Opteron I think,
> but is not very likely to be the cause of errors with the MARK operation.
>
>
> Regards
> Henrik
>
>
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2004-07-08 7:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-07 11:57 MARK-Operations problems Alexander Samad
2004-07-08 0:10 ` Henrik Nordstrom
2004-07-08 1:12 ` Maintaining MARKs on packets throughout the network sami
2004-07-08 6:37 ` Henrik Nordstrom
2004-07-08 2:18 ` MARK-Operations problems Alexander Samad
2004-07-08 6:57 ` Henrik Nordstrom
2004-07-08 7:18 ` Alexander Samad [this message]
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=20040708071841.GE16285@samad.com.au \
--to=alex@samad.com.au \
--cc=netfilter-devel@lists.netfilter.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.