path: root/extensions/
diff options
authorlaforge <laforge>2004-01-22 15:04:24 +0000
committerlaforge <laforge>2004-01-22 15:04:24 +0000
commite98c6ca0cd66184de43eb4c8cc34114fb72c88f6 (patch)
treea24f57a9be5a8364b53dfa102705d270f36b440a /extensions/
parent9bbaedb7f5bd564ff7f54ae87e2d344bd044ef2e (diff)
split manpages into per-extension manpage snippet (Henrik Nordstrom)
add lots of missing manpage snippets (Harald Welte)
Diffstat (limited to 'extensions/')
1 files changed, 27 insertions, 0 deletions
diff --git a/extensions/ b/extensions/
new file mode 100644
index 0000000..7579e14
--- /dev/null
+++ b/extensions/
@@ -0,0 +1,27 @@
+This target is only valid in the
+.B nat
+table, in the
+chains, and user-defined chains which are only called from those
+chains. It specifies that the destination address of the packet
+should be modified (and all future packets in this connection will
+also be mangled), and rules should cease being examined. It takes one
+type of option:
+.BR "--to-destination " "\fIipaddr\fP[-\fIipaddr\fP][:\fIport\fP-\fIport\fP]"
+which can specify a single new destination IP address, an inclusive
+range of IP addresses, and optionally, a port range (which is only
+valid if the rule also specifies
+.B "-p tcp"
+.BR "-p udp" ).
+If no port range is specified, then the destination port will never be
+You can add several --to-destination options. 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 adresses.