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