1 Turn on kernel logging of matching packets. When this option is set 2 for a rule, the Linux kernel will print some information on all 3 matching packets (like most IP/IPv6 header fields) via the kernel log 4 (where it can be read with 5 .I dmesg 6 or 7 .IR syslogd (8)). 8 This is a "non-terminating target", i.e. rule traversal continues at 9 the next rule. So if you want to LOG the packets you refuse, use two 10 separate rules with the same matching criteria, first using target LOG 11 then DROP (or REJECT). 12 .TP 13 \fB\-\-log\-level\fP \fIlevel\fP 14 Level of logging, which can be (system-specific) numeric or a mnemonic. 15 Possible values are (in decreasing order of priority): \fBemerg\fP, 16 \fBalert\fP, \fBcrit\fP, \fBerror\fP, \fBwarning\fP, \fBnotice\fP, \fBinfo\fP 17 or \fBdebug\fP. 18 .TP 19 \fB\-\-log\-prefix\fP \fIprefix\fP 20 Prefix log messages with the specified prefix; up to 29 letters long, 21 and useful for distinguishing messages in the logs. 22 .TP 23 \fB\-\-log\-tcp\-sequence\fP 24 Log TCP sequence numbers. This is a security risk if the log is 25 readable by users. 26 .TP 27 \fB\-\-log\-tcp\-options\fP 28 Log options from the TCP packet header. 29 .TP 30 \fB\-\-log\-ip\-options\fP 31 Log options from the IP/IPv6 packet header. 32 .TP 33 \fB\-\-log\-uid\fP 34 Log the userid of the process which generated the packet. 35
