All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: David Ford <david@blue-labs.org>
Cc: Netfilter Development Mailinglist
	<netfilter-devel@lists.netfilter.org>,
	Pablo Neira Ayuso <pablo@netfilter.org>
Subject: Re: [ANNOUNCE] Release of iptables 1.3.8
Date: Tue, 26 Jun 2007 11:21:58 +0200	[thread overview]
Message-ID: <4680DAB6.9000903@trash.net> (raw)
In-Reply-To: <467FCECA.5060302@blue-labs.org>

David Ford wrote:
> http://bugs.gentoo.org/show_bug.cgi?id=166201
> 
> 
> bug quote>
> 
>>I got this error after upgrading to sys-kernel/gentoo-sources-2.6.20(with
>>net-firewall/iptables-1.3.7).
>>
>># iptables --table mangle --append OUTPUT --jump MARK --set-mark 2
>>iptables: Invalid argument
>>
>>dmesg says:
>>ip_tables: MARK target: invalid size 16 != 24
>>
>>similar error occurs when using CONNMARK target, mark match and connmark match.
>>
>>I found an entry on the netfilter mailing list saying:
>>The latest -git kernel includes compatibility functions for 32 bit
>>userspace. You need to compile your iptables without the
>>KERNEL_64_USERSPACE_32 thing though (edit main Makefile).
>>
>>
>>I did so and removed -DKERNEL_64_USERSPACE_32 from the Makefile and it worked.
> 
> 
> Any comments from netfilter team on this?


Indeed, thanks for the reminder. The KERNEL_64_USERSPACE_32 stuff
needs to go.

Patches for that are welcome.

  reply	other threads:[~2007-06-26  9:21 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-25 13:21 [ANNOUNCE] Release of iptables 1.3.8 Pablo Neira Ayuso
2007-06-25 14:18 ` David Ford
2007-06-26  9:21   ` Patrick McHardy [this message]
2007-06-28 11:39     ` Yasuyuki KOZAKAI
     [not found]     ` <200706281139.l5SBduIn016853@toshiba.co.jp>
2007-06-28 11:52       ` Patrick McHardy
2007-06-28 15:46         ` Yasuyuki KOZAKAI
     [not found]         ` <200706281546.l5SFkEBG007744@toshiba.co.jp>
2007-06-28 15:51           ` Patrick McHardy
2007-06-28 16:02             ` Patrick McHardy

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=4680DAB6.9000903@trash.net \
    --to=kaber@trash.net \
    --cc=david@blue-labs.org \
    --cc=netfilter-devel@lists.netfilter.org \
    --cc=pablo@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.