iptables manpage: Update SNAT target
PATCH 1/1 iptables manpage: Update SNAT target
Hello,
this patch renames libipt_SNAT.man to libxt_SNAT.man thus informing about the IPv6 version. Also the list of valid protocols for port mapping is updated to:
tcp, udp, dccp and sctp.
Best regards
Mart
Quoted 1 line
From
8136feb4b69ac27cb50d8f1db95bf2d03e9ba8a9Mon Sep 17 00:00:00 2001
From: AllKind <[email protected]>
Date: Wed, 10 Apr 2013 16:44:49 +0200
Subject: [PATCH] manpage: Rename libipt_SNAT.man to libxt_SNAT.man.
Update list of protocols valid for port mapping.
--- extensions/libipt_SNAT.man | 37 ------------------------------------- extensions/libxt_SNAT.man | 34 ++++++++++++++++++++++++++++++++++ 2 files changed, 34 insertions(+), 37 deletions(-) delete mode 100644 extensions/libipt_SNAT.man create mode 100644 extensions/libxt_SNAT.man
extensions/libipt_SNAT.man deleted +0 -37
@@ -1,37 +0,0 @@ -This target is only valid in the -.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 -of option: -.TP -\fB\-\-to\-source\fP [\fIipaddr\fP[\fB\-\fP\fIipaddr\fP]][\fB:\fP\fIport\fP[\fB\-\fP\fIport\fP]] -which can specify a single new source IP address, an inclusive range -of IP addresses, and optionally, a port range (which is only valid if -the rule also specifies -\fB\-p tcp\fP -or -\fB\-p udp\fP). -If no port range is specified, then source ports below 512 will be -mapped to other ports below 512: those between 512 and 1023 inclusive -will be mapped to ports below 1024, and other ports will be mapped to -1024 or above. Where possible, no port alteration will occur. - -In Kernels up to 2.6.10, you can add several \-\-to\-source options. For those -kernels, if you specify more than one source address, either via an address -range or multiple \-\-to\-source options, a simple round-robin (one after another -in cycle) takes place between these addresses. -Later Kernels (>= 2.6.11-rc1) don't have the ability to NAT to multiple ranges -anymore. -.TP -\fB\-\-random\fP -If option -\fB\-\-random\fP -is used then port mapping will be randomized (kernel >= 2.6.21). -.TP -\fB\-\-persistent\fP -Gives a client the same source-/destination-address for each connection. -This supersedes the SAME target. Support for persistent mappings is available -from 2.6.29-rc2.
extensions/libxt_SNAT.man new file +34 -0
@@ -0,0 +1,34 @@ +This target is only valid in the +.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 the +following options: +.TP +\fB\-\-to\-source\fP [\fIipaddr\fP[\fB\-\fP\fIipaddr\fP]][\fB:\fP\fIport\fP[\fB\-\fP\fIport\fP]] +which can specify a single new source IP address, an inclusive range +of IP addresses. Optionally a port range, +if the rule also specifies one of the following protocols: +\fBtcp\fP, \fBudp\fP, \fBdccp\fP or \fBsctp\fP. +If no port range is specified, then source ports below 512 will be +mapped to other ports below 512: those between 512 and 1023 inclusive +will be mapped to ports below 1024, and other ports will be mapped to +1024 or above. Where possible, no port alteration will occur. +In Kernels up to 2.6.10, you can add several \-\-to\-source options. For those +kernels, if you specify more than one source address, either via an address +range or multiple \-\-to\-source options, a simple round-robin (one after another +in cycle) takes place between these addresses. +Later Kernels (>= 2.6.11-rc1) don't have the ability to NAT to multiple ranges +anymore. +.TP +\fB\-\-random\fP +If option +\fB\-\-random\fP +is used then port mapping will be randomized (kernel >= 2.6.21). +.TP +\fB\-\-persistent\fP +Gives a client the same source-/destination-address for each connection. +This supersedes the SAME target. Support for persistent mappings is available +from 2.6.29-rc2.
Signature · 1 line
1.7.2.5
Quoted 6 lines · On 10.04.2013 18:32, [email protected] wrote:
Hello,
this patch renames libipt_SNAT.man to libxt_SNAT.man thus informing about the IPv6 version.
Also the list of valid protocols for port mapping is updated to:
tcp, udp, dccp and sctp.
I'm very sorry, I messed up the author lines, resending.
Quoted 1 line
From
8136feb4b69ac27cb50d8f1db95bf2d03e9ba8a9Mon Sep 17 00:00:00 2001
From: Mart Frauenlob <[email protected]>
Date: Wed, 10 Apr 2013 16:44:49 +0200
Subject: [PATCH] manpage: Rename libipt_SNAT.man to libxt_SNAT.man.
Update list of protocols valid for port mapping.
--- extensions/libipt_SNAT.man | 37 ------------------------------------- extensions/libxt_SNAT.man | 34 ++++++++++++++++++++++++++++++++++ 2 files changed, 34 insertions(+), 37 deletions(-) delete mode 100644 extensions/libipt_SNAT.man create mode 100644 extensions/libxt_SNAT.man
extensions/libipt_SNAT.man deleted +0 -37
@@ -1,37 +0,0 @@ -This target is only valid in the -.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 -of option: -.TP -\fB\-\-to\-source\fP [\fIipaddr\fP[\fB\-\fP\fIipaddr\fP]][\fB:\fP\fIport\fP[\fB\-\fP\fIport\fP]] -which can specify a single new source IP address, an inclusive range -of IP addresses, and optionally, a port range (which is only valid if -the rule also specifies -\fB\-p tcp\fP -or -\fB\-p udp\fP). -If no port range is specified, then source ports below 512 will be -mapped to other ports below 512: those between 512 and 1023 inclusive -will be mapped to ports below 1024, and other ports will be mapped to -1024 or above. Where possible, no port alteration will occur. - -In Kernels up to 2.6.10, you can add several \-\-to\-source options. For those -kernels, if you specify more than one source address, either via an address -range or multiple \-\-to\-source options, a simple round-robin (one after another -in cycle) takes place between these addresses. -Later Kernels (>= 2.6.11-rc1) don't have the ability to NAT to multiple ranges -anymore. -.TP -\fB\-\-random\fP -If option -\fB\-\-random\fP -is used then port mapping will be randomized (kernel >= 2.6.21). -.TP -\fB\-\-persistent\fP -Gives a client the same source-/destination-address for each connection. -This supersedes the SAME target. Support for persistent mappings is available -from 2.6.29-rc2.
extensions/libxt_SNAT.man new file +34 -0
@@ -0,0 +1,34 @@ +This target is only valid in the +.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 the +following options: +.TP +\fB\-\-to\-source\fP [\fIipaddr\fP[\fB\-\fP\fIipaddr\fP]][\fB:\fP\fIport\fP[\fB\-\fP\fIport\fP]] +which can specify a single new source IP address, an inclusive range +of IP addresses. Optionally a port range, +if the rule also specifies one of the following protocols: +\fBtcp\fP, \fBudp\fP, \fBdccp\fP or \fBsctp\fP. +If no port range is specified, then source ports below 512 will be +mapped to other ports below 512: those between 512 and 1023 inclusive +will be mapped to ports below 1024, and other ports will be mapped to +1024 or above. Where possible, no port alteration will occur. +In Kernels up to 2.6.10, you can add several \-\-to\-source options. For those +kernels, if you specify more than one source address, either via an address +range or multiple \-\-to\-source options, a simple round-robin (one after another +in cycle) takes place between these addresses. +Later Kernels (>= 2.6.11-rc1) don't have the ability to NAT to multiple ranges +anymore. +.TP +\fB\-\-random\fP +If option +\fB\-\-random\fP +is used then port mapping will be randomized (kernel >= 2.6.21). +.TP +\fB\-\-persistent\fP +Gives a client the same source-/destination-address for each connection. +This supersedes the SAME target. Support for persistent mappings is available +from 2.6.29-rc2.
Signature · 1 line
1.7.2.5
Quoted 7 lines · Mart Frauenlob
Quoted 6 lines · On 10.04.2013 18:32, [email protected] wrote:
Hello,
this patch renames libipt_SNAT.man to libxt_SNAT.man thus informing about the IPv6 version.
Also the list of valid protocols for port mapping is updated to:
tcp, udp, dccp and sctp.
Applied, thanks.