From: Phil Sutter Date: Tue, 18 Dec 2018 11:16:30 +0000 (+0100) Subject: extensions: TRACE: Point at xtables-monitor in documentation X-Git-Tag: v1.8.3~100 X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=9ac39888722ee9c7e97d9b8cb9eb4f33b582130a;p=thirdparty%2Fiptables.git extensions: TRACE: Point at xtables-monitor in documentation With iptables-nft, logging of trace events is different from legacy. Explain why and hint at how to receive events in this case. Signed-off-by: Phil Sutter Signed-off-by: Florian Westphal --- diff --git a/extensions/libxt_TRACE.man b/extensions/libxt_TRACE.man index 8d590a52..5187a8d2 100644 --- a/extensions/libxt_TRACE.man +++ b/extensions/libxt_TRACE.man @@ -1,13 +1,20 @@ This target marks packets so that the kernel will log every rule which match -the packets as those traverse the tables, chains, rules. +the packets as those traverse the tables, chains, rules. It can only be used in +the +.BR raw +table. .PP -A logging backend, such as ip(6)t_LOG or nfnetlink_log, must be loaded for this -to be visible. +With iptables-legacy, a logging backend, such as ip(6)t_LOG or nfnetlink_log, +must be loaded for this to be visible. The packets are logged with the string prefix: "TRACE: tablename:chainname:type:rulenum " where type can be "rule" for plain rule, "return" for implicit rule at the end of a user defined chain and "policy" for the policy of the built in chains. -.br -It can only be used in the -.BR raw -table. +.PP +With iptables-nft, the target is translated into nftables' +.B "meta nftrace" +expression. Hence the kernel sends trace events via netlink to userspace where +they may be displayed using +.B "xtables-monitor --trace" +command. For details, refer to +.BR xtables-monitor (8).