From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Arturo Borrero Gonzalez <arturo@debian.org>
Cc: Phil Sutter <phil@nwl.cc>,
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 16:58:01 +0200 [thread overview]
Message-ID: <20170428145801.GA10616@salvia> (raw)
In-Reply-To: <CAOkSjBi=oYsB2wDxq0-1ejaUrwrt+vRcAjCKO8f4RXv2=cqq=Q@mail.gmail.com>
On Fri, Apr 28, 2017 at 11:02:53AM +0200, Arturo Borrero Gonzalez wrote:
> On 28 April 2017 at 10:28, Phil Sutter <phil@nwl.cc> wrote:
[...]
> > Ah, thanks for the pointer! I tend to ignore anything that's not in the
> > man page. :)
>
> Well, I guess adding more info to the man page won't hurt.
>
> Things I would add:
> * some bits about NAT chains configuration (this issue)
> * info about base chains priorities
> * some bits about atomic operations
Either we update the existing documentation (manpage and wiki) as
Arturo suggest or we add some sort of transparent automatic NAT chain
registration in the kernel.
next prev parent reply other threads:[~2017-04-28 14:58 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
2017-04-28 9:02 ` Arturo Borrero Gonzalez
2017-04-28 14:58 ` Pablo Neira Ayuso [this message]
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=20170428145801.GA10616@salvia \
--to=pablo@netfilter.org \
--cc=arturo@debian.org \
--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).