netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Florian Westphal <fw@strlen.de>
Cc: Arturo Borrero Gonzalez <arturo@debian.org>,
	Netfilter Development Mailing list
	<netfilter-devel@vger.kernel.org>
Subject: Re: using nft & iptables nat in parallel
Date: Wed, 14 Jun 2017 12:40:08 +0200	[thread overview]
Message-ID: <20170614104008.GA14452@salvia> (raw)
In-Reply-To: <20170614095803.GC10130@breakpoint.cc>

On Wed, Jun 14, 2017 at 11:58:03AM +0200, Florian Westphal wrote:
> Arturo Borrero Gonzalez <arturo@debian.org> wrote:
> > I'm curious, What is the use case of using both nftables and iptables
> > at the same time?
> > Some missing functionality in nft?
> > Perhaps some ipt->nft partial migration procedure?
> 
> Yes, partial migration.
> 
> Right now there are an awful lot of tools out there (docker, libvirt,
> kubernetes, ..) that call iptables(-restore) directly (or inject them via
> firewalld).
> 
> And unfortunately I don't see how we can magically move all of this
> to nftables.
>
> So allowing to do a step-by-step migration seems the only viable
> option.

We have iptables-compat-restore, this uses the nf_tables netlink
frontend and packet classification code, plus x_tables extensions to
run iptables code. It should allow us to schedule the x_tables core
for removal at some point.

In Montpellier, we mentioned that distro could add a iptables-restore
symlink to iptables-compat-restore so it becomes visible that we're
relying on the compat infrastructure.

This iptables-compat-restore interacts with nft via translate layer,
so if you just 'nft list ruleset' after using iptables-compat-restore,
you will get a translation (if available).

  reply	other threads:[~2017-06-14 10:40 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-14  9:24 using nft & iptables nat in parallel Florian Westphal
2017-06-14  9:37 ` Arturo Borrero Gonzalez
2017-06-14  9:58   ` Florian Westphal
2017-06-14 10:40     ` Pablo Neira Ayuso [this message]
2017-06-14 11:19       ` Florian Westphal
2017-06-14 11:29         ` Pablo Neira Ayuso
2017-06-14 11:53           ` Florian Westphal
2017-06-14 17:13             ` Pablo Neira Ayuso
2017-06-14 17:44               ` Pablo Neira Ayuso
2017-06-14 18:00               ` Florian Westphal
2017-06-14 13:22     ` Arturo Borrero Gonzalez

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=20170614104008.GA14452@salvia \
    --to=pablo@netfilter.org \
    --cc=arturo@debian.org \
    --cc=fw@strlen.de \
    --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).