From: Eric Leblond <eric@regit.org>
To: jpmenil@gmail.com
Cc: netfilter@vger.kernel.org
Subject: Re: nftables compatibility
Date: Tue, 02 Dec 2014 23:15:48 +0100 [thread overview]
Message-ID: <1417558548.10146.7.camel@regit.org> (raw)
In-Reply-To: <547E38AE.6000909@gmail.com>
Hi,
On Tue, 2014-12-02 at 23:09 +0100, Jean-Philippe Menil wrote:
> Hi,
>
> while playing with nftables, i observe that my iptables masquerading do not
> work anymore:
>
> modprobe nft_nat
> modprobe nft_chain_nat_ipv4
> nft add table nat
> nft add chain nat postrouting { type nat hook postrouting priority 0 \; }
>
> ^^ iptables nat stoped work here.
>
> I'm sure i read that nftables and iptables where compatible.
>
> Can anyone point me what am i missing ?
>
> (I'm on 3.17.4)
Sadly, masquerade is requiring 3.18. Only standard NAT is implemented in
3.17.x.
BR,
--
Eric Leblond <eric@regit.org>
next prev parent reply other threads:[~2014-12-02 22:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-02 22:09 nftables compatibility Jean-Philippe Menil
2014-12-02 22:15 ` Eric Leblond [this message]
2014-12-03 7:30 ` Jean-Philippe Menil
2014-12-03 11:00 ` Pablo Neira Ayuso
2014-12-03 11:02 ` Jean-Philippe Menil
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=1417558548.10146.7.camel@regit.org \
--to=eric@regit.org \
--cc=jpmenil@gmail.com \
--cc=netfilter@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 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.