diff options
author | Phil Sutter <phil@nwl.cc> | 2022-01-08 13:15:20 +0100 |
---|---|---|
committer | Phil Sutter <phil@nwl.cc> | 2022-01-17 15:16:21 +0100 |
commit | 30b178b9bf11e75cd5ff7310ce0f5d9c9ace3b7a (patch) | |
tree | 22c084309bbfee0f03584db7a9be05cd00b72a83 /extensions/libxt_DNAT.man | |
parent | 7ee5b97095365383629b9c7c78ba93e09e1051d2 (diff) |
extensions: *NAT: Kill multiple IPv4 range support
It is the year of the great revolution, nobody cares about kernel
versions below 2.6.11 anymore. Time to get rid of the cruft.
While being at it, drop the explicit duplicate argument check and
instead just remove XTOPT_MULTI flag from the respective
xt_option_entry.
Signed-off-by: Phil Sutter <phil@nwl.cc>
Acked-by: Florian Westphal <fw@strlen.de>
Diffstat (limited to 'extensions/libxt_DNAT.man')
-rw-r--r-- | extensions/libxt_DNAT.man | 6 |
1 files changed, 0 insertions, 6 deletions
diff --git a/extensions/libxt_DNAT.man b/extensions/libxt_DNAT.man index 225274ff..c3daea9a 100644 --- a/extensions/libxt_DNAT.man +++ b/extensions/libxt_DNAT.man @@ -18,12 +18,6 @@ if the rule also specifies one of the following protocols: 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 |