using the TRACE target.
.TP
\fB\-4\fP
-Restrict output to ipv4.
+Restrict output to IPv4.
.TP
\fB\-6\fP
-Restrict output to ipv6.
+Restrict output to IPv6.
.SH EXAMPLE OUTPUT
.TP
.B xtables-monitor \-\-trace
decision (the example shows accept being applied).
The fifth line shows that the packet leaves the filter INPUT chain, i.e., no rules in the filter tables
INPUT chain matched the packet.
-It then got DROPPED by the policy of the INPUT table, as hown by line six.
+It then got DROPPED by the policy of the INPUT table, as shown by line six.
The last line shows another packet arriving \-\- the packet id is different.
-When using the TRACE target, it is usally a good idea to only select packets
+When using the TRACE target, it is usually a good idea to only select packets
that are relevant, for example via
.nf
iptables \-t raw \-A PREROUTING \-p tcp \-\-dport 80 \-\-syn \-m limit \-\-limit 1/s \-j TRACE
xtables_globals.program_version);
printf("Usage: %s [ -t | -e ]\n"
" --trace -t trace ruleset traversal of packets tagged via -j TRACE rule\n"
- " --event -e show events taht modify the ruleset\n"
+ " --event -e show events that modify the ruleset\n"
"Optional arguments:\n"
- " --ipv4 -4 only monitor ipv4\n"
- " --ipv6 -6 only monitor ipv6\n"
+ " --ipv4 -4 only monitor IPv4\n"
+ " --ipv6 -6 only monitor IPv6\n"
" --counters -c show counters in rules\n"
, xtables_globals.program_name);