From f16fbe76f62dcb9f7395d1837ad2d056463ba55f Mon Sep 17 00:00:00 2001 From: Phil Sutter Date: Mon, 22 Jun 2020 15:07:40 +0200 Subject: doc: Document notrack statement Merely a stub, but better to mention it explicitly instead of having it appear in synproxy examples and letting users guess as to what it does. Signed-off-by: Phil Sutter Reviewed-by: Florian Westphal --- doc/statements.txt | 14 ++++++++++++++ 1 file changed, 14 insertions(+) (limited to 'doc/statements.txt') diff --git a/doc/statements.txt b/doc/statements.txt index ced311cb..607aee13 100644 --- a/doc/statements.txt +++ b/doc/statements.txt @@ -263,6 +263,20 @@ table inet raw { ct event set new,related,destroy -------------------------------------- +NOTRACK STATEMENT +~~~~~~~~~~~~~~~~~ +The notrack statement allows to disable connection tracking for certain +packets. + +[verse] +*notrack* + +Note that for this statement to be effective, it has to be applied to packets +before a conntrack lookup happens. Therefore, it needs to sit in a chain with +either prerouting or output hook and a hook priority of -300 or less. + +See SYNPROXY STATEMENT for an example usage. + META STATEMENT ~~~~~~~~~~~~~~ A meta statement sets the value of a meta expression. The existing meta fields -- cgit v1.2.3