doc: have NOTRACK manpage point to CT instead

The module is obsolete, so point to CT --notrack instead.

Signed-off-by: Jan Engelhardt <jengelh@inai.de>

diff --git a/extensions/libxt_NOTRACK.man b/extensions/libxt_NOTRACK.man
index c2cdf5a65906bdb2534608bd0cebbddaed0bf209..633b965e6e93c0228b0cfccfe291ab10e7748a14 100644 (file)
--- a/extensions/libxt_NOTRACK.man
+++ b/extensions/libxt_NOTRACK.man
@@ -1,5 +1,3 @@
 This target disables connection tracking for all packets matching that rule.
-.PP
-It can only be used in the
-.B raw
-table.
+It is obsoleted by \-j CT \-\-notrack. Like CT, NOTRACK can only be used in
+the \fBraw\fP table.

diff --git a/extensions/libxt_conntrack.man b/extensions/libxt_conntrack.man
index c0cd24fe40eb2afff26f527ead8eab49e003f015..15fd1ddf1f6da1843a0897999b06d52b5894caa8 100644 (file)
--- a/extensions/libxt_conntrack.man
+++ b/extensions/libxt_conntrack.man
@@ -57,8 +57,8 @@ The packet is starting a new connection, but is associated with an
 existing connection, such as an FTP data transfer, or an ICMP error.
 .TP
 \fBUNTRACKED\fP
-The packet is not tracked at all, which happens if you use
-the NOTRACK target in raw table.
+The packet is not tracked at all, which happens if you explicitly untrack it
+by using \-j CT \-\-notrack in the raw table.
 .TP
 \fBSNAT\fP
 A virtual state, matching if the original source address differs from the reply