From: Florian Westphal <fw@strlen.de>
To: Lion Yang <lion@aosc.io>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [Documentation] SNAT in INPUT chain
Date: Tue, 26 Apr 2016 18:14:17 +0200 [thread overview]
Message-ID: <20160426161417.GA3100@strlen.de> (raw)
In-Reply-To: <670551461680277@web23j.yandex.ru>
Lion Yang <lion@aosc.io> wrote:
> netfilter after about (linux kernel) 2.4.x (or 2.6.x?) [1] can put SNAT into hook NF_IP_LOCAL_IN.
> However, official docs(including 'man') doesn't change, so far.
>
> It's hard to me to write something correctly and precisely in English.
> Would someone improve the docs please?
Is this enough?
--- a/iptables/iptables.8.in
+++ b/iptables/iptables.8.in
@@ -103,8 +103,9 @@ the built-in chains \fBINPUT\fP (for packets destined to local sockets),
.TP
\fBnat\fP:
This table is consulted when a packet that creates a new
-connection is encountered. It consists of three built-ins: \fBPREROUTING\fP
-(for altering packets as soon as they come in), \fBOUTPUT\fP
+connection is encountered. It consists of four built-ins: \fBPREROUTING\fP
+(for altering packets as soon as they come in), \fBINPUT\fP (for altering
+packets destined for local sockets), \fBOUTPUT\fP
(for altering locally-generated packets before routing), and \fBPOSTROUTING\fP
(for altering packets as they are about to go out).
IPv6 NAT support is available since kernel 3.7.
next prev parent reply other threads:[~2016-04-26 16:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-26 14:17 [Documentation] SNAT in INPUT chain Lion Yang
2016-04-26 16:14 ` Florian Westphal [this message]
2016-04-26 16:46 ` Lion Yang
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=20160426161417.GA3100@strlen.de \
--to=fw@strlen.de \
--cc=lion@aosc.io \
--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).