1 This target is only valid in the 2 .B nat 3 table, in the 4 .B PREROUTING 5 and 6 .B OUTPUT 7 chains, and user-defined chains which are only called from those 8 chains. It specifies that the destination address of the packet 9 should be modified (and all future packets in this connection will 10 also be mangled), and rules should cease being examined. It takes the 11 following options: 12 .TP 13 \fB\-\-to\-destination\fP [\fIipaddr\fP[\fB\-\fP\fIipaddr\fP]][\fB:\fP\fIport\fP[\fB\-\fP\fIport\fP]] 14 which can specify a single new destination IP address, an inclusive 15 range of IP addresses. Optionally a port range, 16 if the rule also specifies one of the following protocols: 17 \fBtcp\fP, \fBudp\fP, \fBdccp\fP or \fBsctp\fP. 18 If no port range is specified, then the destination port will never be 19 modified. If no IP address is specified then only the destination port 20 will be modified. 21 In Kernels up to 2.6.10 you can add several \-\-to\-destination options. For 22 those kernels, if you specify more than one destination address, either via an 23 address range or multiple \-\-to\-destination options, a simple round-robin (one 24 after another in cycle) load balancing takes place between these addresses. 25 Later Kernels (>= 2.6.11-rc1) don't have the ability to NAT to multiple ranges 26 anymore. 27 .TP 28 \fB\-\-random\fP 29 If option 30 \fB\-\-random\fP 31 is used then port mapping will be randomized (kernel >= 2.6.22). 32 .TP 33 \fB\-\-persistent\fP 34 Gives a client the same source-/destination-address for each connection. 35 This supersedes the SAME target. Support for persistent mappings is available 36 from 2.6.29-rc2. 37 .TP 38 IPv6 support available since Linux kernels >= 3.7. 39
