From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Andreas Schultz <aschultz@tpip.net>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: iptables nftables compat weirdness
Date: Tue, 16 Jun 2015 18:07:25 +0200 [thread overview]
Message-ID: <20150616160725.GA7165@salvia> (raw)
In-Reply-To: <1424744661.225751.1433848590972.JavaMail.zimbra@tpip.net>
On Tue, Jun 09, 2015 at 11:16:30AM +0000, Andreas Schultz wrote:
> Hi,
>
> While testing iptables-compat, I've come across some weird behavior:
>
> # iptables-compat -t mangle -N TEST
> # iptables-compat -t mangle -A PREROUTING -j TEST
>
> This works nicely, but when we put something in the TEST chain:
>
> # iptables-compat -t mangle -A TEST -j MARK --set-mark 0x80000000/0x80000000
> # iptables-compat -t mangle -A PREROUTING -j TEST
> iptables-compat: Invalid argument. Run `dmesg' for more information.
>
> dmesg does not contain any information.
>
> The same problem exists for all default chains in mangle, filter and nat.
>
> Kernel is: 4.1-rc5
> iptables: git://git.netfilter.org/iptables, branch master, commit 0bb1859e2d6dd79a0a59c3ee65f6a78cba118b86
> nftables: git://git.netfilter.org/nftables, branch next-4.1, commit a93bc1795b272174a10d90961a248f2c620bfa2c
Given that the pernet netfilter hooks are on its way to reach
mainstream (Eric Bierderman is working on that).
Could you help me diagnosing this problem? The nf_tables kernel side
is rejecting this with -EINVAL. Is this a new bug in the 4.1-rc
series?
Thank you.
next prev parent reply other threads:[~2015-06-16 16:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-09 11:16 iptables nftables compat weirdness Andreas Schultz
2015-06-16 16:07 ` Pablo Neira Ayuso [this message]
2015-06-17 10:19 ` Andreas Schultz
2015-06-17 10:28 ` Andreas Schultz
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=20150616160725.GA7165@salvia \
--to=pablo@netfilter.org \
--cc=aschultz@tpip.net \
--cc=netfilter-devel@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;
as well as URLs for NNTP newsgroup(s).