summaryrefslogtreecommitdiffstats
path: root/extensions/libxt_SNAT.man
diff options
context:
space:
mode:
authorPhil Sutter <phil@nwl.cc>2022-01-08 13:15:20 +0100
committerPhil Sutter <phil@nwl.cc>2022-01-17 15:16:21 +0100
commit30b178b9bf11e75cd5ff7310ce0f5d9c9ace3b7a (patch)
tree22c084309bbfee0f03584db7a9be05cd00b72a83 /extensions/libxt_SNAT.man
parent7ee5b97095365383629b9c7c78ba93e09e1051d2 (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_SNAT.man')
-rw-r--r--extensions/libxt_SNAT.man6
1 files changed, 0 insertions, 6 deletions
diff --git a/extensions/libxt_SNAT.man b/extensions/libxt_SNAT.man
index 8cd0b80e..08766447 100644
--- a/extensions/libxt_SNAT.man
+++ b/extensions/libxt_SNAT.man
@@ -19,12 +19,6 @@ If no port range is specified, then source ports below 512 will be
mapped to other ports below 512: those between 512 and 1023 inclusive
will be mapped to ports below 1024, and other ports will be mapped to
1024 or above. Where possible, no port alteration will occur.
-In Kernels up to 2.6.10, you can add several \-\-to\-source options. For those
-kernels, if you specify more than one source address, either via an address
-range or multiple \-\-to\-source options, a simple round-robin (one after another
-in cycle) 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