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: netfilter-devel@vger.kernel.org
Subject: Re: nftables and iptables nat coexistence
Date: Thu, 19 Oct 2017 13:30:33 +0200	[thread overview]
Message-ID: <20171019113033.GA3537@salvia> (raw)
In-Reply-To: <20171019111812.GC16796@breakpoint.cc>

On Thu, Oct 19, 2017 at 01:18:12PM +0200, Florian Westphal wrote:
> Registering implicit nat hook, making iptables_nat and nftables nat
> at the same time impossible (reject from kernel) etc. is more
> convenient as we cannot break existing setups and only prevent
> configuring a non-working/broken state rather than allowing things
> that do not work at the moment.

Yes, let's tighten things now, we can relax them later.

      reply	other threads:[~2017-10-19 11:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-18 13:56 nftables and iptables nat coexistence Florian Westphal
2017-10-19 10:15 ` Pablo Neira Ayuso
2017-10-19 10:25   ` Pablo Neira Ayuso
2017-10-19 11:18   ` Florian Westphal
2017-10-19 11:30     ` Pablo Neira Ayuso [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=20171019113033.GA3537@salvia \
    --to=pablo@netfilter.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).