From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Florian Westphal <fw@strlen.de>
Cc: Phil Sutter <phil@nwl.cc>, netfilter-devel@vger.kernel.org
Subject: Re: [nft PATCH] files: Move netdev-ingress.nft to /etc/nftables as well
Date: Tue, 25 Jun 2019 02:24:04 +0200 [thread overview]
Message-ID: <20190625002404.63o7novb2ett2yoo@salvia> (raw)
In-Reply-To: <20190624164941.dhcm57r35km3azbg@breakpoint.cc>
On Mon, Jun 24, 2019 at 06:49:41PM +0200, Florian Westphal wrote:
> Phil Sutter <phil@nwl.cc> wrote:
> > > Right. Do you think we should also add in inet-nat.nft example,
> > > or even replace the ipvX- ones?
> >
> > Having an inet family nat example would be wonderful! Can inet NAT
> > replace IPvX-ones completely or are there any limitations as to what is
> > possible in rules?
>
> I'm not aware of any limitations.
Only limitation is that older kernels do not support NAT for the inet
family.
next prev parent reply other threads:[~2019-06-25 0:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-24 15:12 [nft PATCH] files: Move netdev-ingress.nft to /etc/nftables as well Phil Sutter
2019-06-24 15:14 ` Florian Westphal
2019-06-24 16:24 ` Phil Sutter
2019-06-24 16:49 ` Florian Westphal
2019-06-25 0:24 ` Pablo Neira Ayuso [this message]
2019-07-03 10:56 ` Phil Sutter
2019-07-03 11:06 ` Pablo Neira Ayuso
2019-07-03 11:06 ` Pablo Neira Ayuso
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=20190625002404.63o7novb2ett2yoo@salvia \
--to=pablo@netfilter.org \
--cc=fw@strlen.de \
--cc=netfilter-devel@vger.kernel.org \
--cc=phil@nwl.cc \
/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).