From: Phil Oester <kernel@linuxace.com>
To: netfilter-devel@lists.netfilter.org
Subject: [PATCH] Remove use of 'mangle' from DNAT/SNAT
Date: Mon, 29 Nov 2004 17:51:53 -0800 [thread overview]
Message-ID: <20041130015153.GA3703@linuxace.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 200 bytes --]
At least one user (via bugzilla) was confused by the use of the word
mangle in the man entries for DNAT and SNAT. Might as well clarify
it...trivial patch below.
This closes bugzilla #261.
Phil
[-- Attachment #2: patch-clarifymangle --]
[-- Type: text/plain, Size: 1616 bytes --]
diff -ru ipt-orig/extensions/libipt_DNAT.man ipt-new/extensions/libipt_DNAT.man
--- ipt-orig/extensions/libipt_DNAT.man 2004-01-22 07:04:24.000000000 -0800
+++ ipt-new/extensions/libipt_DNAT.man 2004-11-29 17:43:24.793557534 -0800
@@ -5,9 +5,9 @@
and
.B OUTPUT
chains, and user-defined chains which are only called from those
-chains. It specifies that the destination address of the packet
-should be modified (and all future packets in this connection will
-also be mangled), and rules should cease being examined. It takes one
+chains. It specifies that the destination address of this packet
+(and any future packets associated with this connection) should be
+modified, and rules should cease being examined. It takes one
type of option:
.TP
.BR "--to-destination " "\fIipaddr\fP[-\fIipaddr\fP][:\fIport\fP-\fIport\fP]"
diff -ru ipt-orig/extensions/libipt_SNAT.man ipt-new/extensions/libipt_SNAT.man
--- ipt-orig/extensions/libipt_SNAT.man 2004-01-22 07:04:24.000000000 -0800
+++ ipt-new/extensions/libipt_SNAT.man 2004-11-29 17:47:58.291064181 -0800
@@ -2,9 +2,9 @@
.B nat
table, in the
.B POSTROUTING
-chain. It specifies that the source address of the packet should be
-modified (and all future packets in this connection will also be
-mangled), and rules should cease being examined. It takes one type
+chain. It specifies that the source address of this packet (and any
+future packets associated with this connection) should be modified,
+and rules should cease being examined. It takes one type
of option:
.TP
.BR "--to-source " "\fIipaddr\fP[-\fIipaddr\fP][:\fIport\fP-\fIport\fP]"
reply other threads:[~2004-11-30 1:51 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20041130015153.GA3703@linuxace.com \
--to=kernel@linuxace.com \
--cc=netfilter-devel@lists.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.