iptables manpage: Update DNAT target
PATCH 1/1 iptables manpage: Update DNAT target
Hello,
this patch renames libipt_DNAT.man to libxt_DNAT.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
556c825f00023eb900093faaf9d55ba686ae0157Mon Sep 17 00:00:00 2001
From: AllKind <[email protected]>
Date: Wed, 10 Apr 2013 16:43:18 +0200
Subject: [PATCH] manpage: Rename libipt_DNAT.man to libxt_DNAT.man.
Update list of protocols valid for port mapping.
--- extensions/libipt_DNAT.man | 39 --------------------------------------- extensions/libxt_DNAT.man | 36 ++++++++++++++++++++++++++++++++++++ 2 files changed, 36 insertions(+), 39 deletions(-) delete mode 100644 extensions/libipt_DNAT.man create mode 100644 extensions/libxt_DNAT.man
extensions/libipt_DNAT.man deleted +0 -39
@@ -1,39 +0,0 @@ -This target is only valid in the -.B nat -table, in the -.B PREROUTING -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 -type of option: -.TP -\fB\-\-to\-destination\fP [\fIipaddr\fP[\fB\-\fP\fIipaddr\fP]][\fB:\fP\fIport\fP[\fB\-\fP\fIport\fP]] -which can specify a single new destination 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 the destination port will never be -modified. If no IP address is specified then only the destination port -will be modified. - -In Kernels up to 2.6.10 you can add several \-\-to\-destination options. For -those kernels, if you specify more than one destination address, either via an -address range or multiple \-\-to\-destination options, a simple round-robin (one -after another in cycle) load balancing 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.22). -.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_DNAT.man new file +36 -0
@@ -0,0 +1,36 @@ +This target is only valid in the +.B nat +table, in the +.B PREROUTING +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 the +following options: +.TP +\fB\-\-to\-destination\fP [\fIipaddr\fP[\fB\-\fP\fIipaddr\fP]][\fB:\fP\fIport\fP[\fB\-\fP\fIport\fP]] +which can specify a single new destination 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 the destination port will never be +modified. If no IP address is specified then only the destination port +will be modified. +In Kernels up to 2.6.10 you can add several \-\-to\-destination options. For +those kernels, if you specify more than one destination address, either via an +address range or multiple \-\-to\-destination options, a simple round-robin (one +after another in cycle) load balancing 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.22). +.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:30, [email protected] wrote:
Hello,
this patch renames libipt_DNAT.man to libxt_DNAT.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
556c825f00023eb900093faaf9d55ba686ae0157Mon Sep 17 00:00:00 2001
From: Mart Frauenlob <[email protected]>
Date: Wed, 10 Apr 2013 16:43:18 +0200
Subject: [PATCH] manpage: Rename libipt_DNAT.man to libxt_DNAT.man.
Update list of protocols valid for port mapping.
--- extensions/libipt_DNAT.man | 39 --------------------------------------- extensions/libxt_DNAT.man | 36 ++++++++++++++++++++++++++++++++++++ 2 files changed, 36 insertions(+), 39 deletions(-) delete mode 100644 extensions/libipt_DNAT.man create mode 100644 extensions/libxt_DNAT.man
extensions/libipt_DNAT.man deleted +0 -39
@@ -1,39 +0,0 @@ -This target is only valid in the -.B nat -table, in the -.B PREROUTING -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 -type of option: -.TP -\fB\-\-to\-destination\fP [\fIipaddr\fP[\fB\-\fP\fIipaddr\fP]][\fB:\fP\fIport\fP[\fB\-\fP\fIport\fP]] -which can specify a single new destination 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 the destination port will never be -modified. If no IP address is specified then only the destination port -will be modified. - -In Kernels up to 2.6.10 you can add several \-\-to\-destination options. For -those kernels, if you specify more than one destination address, either via an -address range or multiple \-\-to\-destination options, a simple round-robin (one -after another in cycle) load balancing 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.22). -.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_DNAT.man new file +36 -0
@@ -0,0 +1,36 @@ +This target is only valid in the +.B nat +table, in the +.B PREROUTING +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 the +following options: +.TP +\fB\-\-to\-destination\fP [\fIipaddr\fP[\fB\-\fP\fIipaddr\fP]][\fB:\fP\fIport\fP[\fB\-\fP\fIport\fP]] +which can specify a single new destination 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 the destination port will never be +modified. If no IP address is specified then only the destination port +will be modified. +In Kernels up to 2.6.10 you can add several \-\-to\-destination options. For +those kernels, if you specify more than one destination address, either via an +address range or multiple \-\-to\-destination options, a simple round-robin (one +after another in cycle) load balancing 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.22). +.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:30, [email protected] wrote:
Hello,
this patch renames libipt_DNAT.man to libxt_DNAT.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, added this to the end of the manpage:
IPv6 support available since Linux kernels >= 3.7.
Thanks.