From: Phil Sutter <phil@nwl.cc>
To: Arturo Borrero Gonzalez <arturo@debian.org>
Cc: Pablo Neira Ayuso <pablo@netfilter.org>,
Netfilter Development Mailing list
<netfilter-devel@vger.kernel.org>
Subject: Re: [nft PATCH 2/2] masquerade: Complain if no prerouting chain exists
Date: Fri, 28 Apr 2017 10:28:24 +0200 [thread overview]
Message-ID: <20170428082824.GJ20805@orbyte.nwl.cc> (raw)
In-Reply-To: <CAOkSjBjtJ0_xymJ_iMuKwxtqArEh_dHs=Tgjo271PnLy4K84ng@mail.gmail.com>
On Fri, Apr 28, 2017 at 10:11:51AM +0200, Arturo Borrero Gonzalez wrote:
> On 28 April 2017 at 10:05, Phil Sutter <phil@nwl.cc> wrote:
> >>
> >> This warning will be printed even in rulesets loaded with '-f'
> >> which first creates the masq rule an then the other chain.
> >
> > Hmm. I tested it with the following config and it works fine:
> >
> > | table ip nat {
> > | chain post {
> > | type nat hook postrouting priority 0; policy accept;
> > | oifname "veth2" masquerade
> > | }
> > |
> > | chain pre {
> > | type nat hook prerouting priority 0; policy accept;
> > | }
> > | }
> >
> > OK, with a config consisting of several 'add' commands, it indeed warns.
> >
> >> I think is just a matter of documenting *everywhere* that this is the
> >> expected behaviour, not a bug.
> >
> > Yeah, I should indeed have done that first, also because masquerade
> > statement is not documented at all yet.
> >
>
> The best current documentation is this:
>
> https://wiki.nftables.org/wiki-nftables/index.php/Performing_Network_Address_Translation_(NAT)
Ah, thanks for the pointer! I tend to ignore anything that's not in the
man page. :)
Cheers, Phil
next prev parent reply other threads:[~2017-04-28 8:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-27 13:24 [nft PATCH 1/2] erec: Make __stmt_binary_error a little more versatile Phil Sutter
2017-04-27 13:24 ` [nft PATCH 2/2] masquerade: Complain if no prerouting chain exists Phil Sutter
2017-04-28 7:01 ` Arturo Borrero Gonzalez
2017-04-28 8:05 ` Phil Sutter
2017-04-28 8:11 ` Arturo Borrero Gonzalez
2017-04-28 8:28 ` Phil Sutter [this message]
2017-04-28 9:02 ` Arturo Borrero Gonzalez
2017-04-28 14:58 ` Pablo Neira Ayuso
2017-04-28 15:59 ` Phil Sutter
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=20170428082824.GJ20805@orbyte.nwl.cc \
--to=phil@nwl.cc \
--cc=arturo@debian.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.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).