| lh | 9ed821d | 2023-04-07 01:36:19 -0700 | [diff] [blame] | 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 one |
| 11 | type of option: |
| 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, and optionally, a port range (which is only |
| 16 | valid if the rule also specifies |
| 17 | \fB\-p tcp\fP |
| 18 | or |
| 19 | \fB\-p udp\fP). |
| 20 | If no port range is specified, then the destination port will never be |
| 21 | modified. If no IP address is specified then only the destination port |
| 22 | will be modified. |
| 23 | |
| 24 | In Kernels up to 2.6.10 you can add several \-\-to\-destination options. For |
| 25 | those kernels, if you specify more than one destination address, either via an |
| 26 | address range or multiple \-\-to\-destination options, a simple round-robin (one |
| 27 | after another in cycle) load balancing takes place between these addresses. |
| 28 | Later Kernels (>= 2.6.11-rc1) don't have the ability to NAT to multiple ranges |
| 29 | anymore. |
| 30 | .TP |
| 31 | \fB\-\-random\fP |
| 32 | If option |
| 33 | \fB\-\-random\fP |
| 34 | is used then port mapping will be randomized (kernel >= 2.6.22). |
| 35 | .RS |
| 36 | .PP |