iptables manpage: Update LOG target
PATCH 1/1 iptables manpage: Update LOG target
Hello,
this patch on the man page unifies the IPv4 and IPv6 entries of the LOG target.
Best regards
Mart
Quoted 1 line
From
e1127e6875136ae9f0c8a721c5868b649e249c3bMon Sep 17 00:00:00 2001
From: AllKind <[email protected]>
Date: Wed, 10 Apr 2013 16:32:54 +0200
Subject: [PATCH] manpage: Rename libipt_LOG.man to libxt_LOG.man.
--- extensions/libip6t_LOG.man | 34 ---------------------------------- extensions/libipt_LOG.man | 34 ---------------------------------- extensions/libxt_LOG.man | 34 ++++++++++++++++++++++++++++++++++ 3 files changed, 34 insertions(+), 68 deletions(-) delete mode 100644 extensions/libip6t_LOG.man delete mode 100644 extensions/libipt_LOG.man create mode 100644 extensions/libxt_LOG.man
extensions/libip6t_LOG.man deleted +0 -34
@@ -1,34 +0,0 @@ -Turn on kernel logging of matching packets. When this option is set -for a rule, the Linux kernel will print some information on all -matching packets (like most IPv6 IPv6-header fields) via the kernel log -(where it can be read with -.I dmesg -or -.IR syslogd (8)). -This is a "non-terminating target", i.e. rule traversal continues at -the next rule. So if you want to LOG the packets you refuse, use two -separate rules with the same matching criteria, first using target LOG -then DROP (or REJECT). -.TP -\fB\-\-log\-level\fP \fIlevel\fP -Level of logging, which can be (system-specific) numeric or a mnemonic. -Possible values are (in decreasing order of priority): \fBemerg\fP, -\fBalert\fP, \fBcrit\fP, \fBerror\fP, \fBwarning\fP, \fBnotice\fP, \fBinfo\fP -or \fBdebug\fP. -.TP -\fB\-\-log\-prefix\fP \fIprefix\fP -Prefix log messages with the specified prefix; up to 29 letters long, -and useful for distinguishing messages in the logs. -.TP -\fB\-\-log\-tcp\-sequence\fP -Log TCP sequence numbers. This is a security risk if the log is -readable by users. -.TP -\fB\-\-log\-tcp\-options\fP -Log options from the TCP packet header. -.TP -\fB\-\-log\-ip\-options\fP -Log options from the IPv6 packet header. -.TP -\fB\-\-log\-uid\fP -Log the userid of the process which generated the packet.
extensions/libipt_LOG.man deleted +0 -34
@@ -1,34 +0,0 @@ -Turn on kernel logging of matching packets. When this option is set -for a rule, the Linux kernel will print some information on all -matching packets (like most IP header fields) via the kernel log -(where it can be read with -.I dmesg -or -.IR syslogd (8)). -This is a "non-terminating target", i.e. rule traversal continues at -the next rule. So if you want to LOG the packets you refuse, use two -separate rules with the same matching criteria, first using target LOG -then DROP (or REJECT). -.TP -\fB\-\-log\-level\fP \fIlevel\fP -Level of logging, which can be (system-specific) numeric or a mnemonic. -Possible values are (in decreasing order of priority): \fBemerg\fP, -\fBalert\fP, \fBcrit\fP, \fBerror\fP, \fBwarning\fP, \fBnotice\fP, \fBinfo\fP -or \fBdebug\fP. -.TP -\fB\-\-log\-prefix\fP \fIprefix\fP -Prefix log messages with the specified prefix; up to 29 letters long, -and useful for distinguishing messages in the logs. -.TP -\fB\-\-log\-tcp\-sequence\fP -Log TCP sequence numbers. This is a security risk if the log is -readable by users. -.TP -\fB\-\-log\-tcp\-options\fP -Log options from the TCP packet header. -.TP -\fB\-\-log\-ip\-options\fP -Log options from the IP packet header. -.TP -\fB\-\-log\-uid\fP -Log the userid of the process which generated the packet.
extensions/libxt_LOG.man new file +34 -0
@@ -0,0 +1,34 @@ +Turn on kernel logging of matching packets. When this option is set +for a rule, the Linux kernel will print some information on all +matching packets (like most IP header fields) via the kernel log +(where it can be read with +.I dmesg +or +.IR syslogd (8)). +This is a "non-terminating target", i.e. rule traversal continues at +the next rule. So if you want to LOG the packets you refuse, use two +separate rules with the same matching criteria, first using target LOG +then DROP (or REJECT). +.TP +\fB\-\-log\-level\fP \fIlevel\fP +Level of logging, which can be (system-specific) numeric or a mnemonic. +Possible values are (in decreasing order of priority): \fBemerg\fP, +\fBalert\fP, \fBcrit\fP, \fBerror\fP, \fBwarning\fP, \fBnotice\fP, \fBinfo\fP +or \fBdebug\fP. +.TP +\fB\-\-log\-prefix\fP \fIprefix\fP +Prefix log messages with the specified prefix; up to 29 letters long, +and useful for distinguishing messages in the logs. +.TP +\fB\-\-log\-tcp\-sequence\fP +Log TCP sequence numbers. This is a security risk if the log is +readable by users. +.TP +\fB\-\-log\-tcp\-options\fP +Log options from the TCP packet header. +.TP +\fB\-\-log\-ip\-options\fP +Log options from the IP packet header. +.TP +\fB\-\-log\-uid\fP +Log the userid of the process which generated the packet.
Signature · 1 line
1.7.2.5
Quoted 4 lines · On 10.04.2013 18:30, [email protected] wrote:
Hello,
this patch on the man page unifies the IPv4 and IPv6 entries of the LOG target.
I'm very sorry, I messed up the author lines, resending.
Quoted 1 line
From
e1127e6875136ae9f0c8a721c5868b649e249c3bMon Sep 17 00:00:00 2001
From: Mart Frauenlob <[email protected]>
Date: Wed, 10 Apr 2013 16:32:54 +0200
Subject: [PATCH] manpage: Rename libipt_LOG.man to libxt_LOG.man.
--- extensions/libip6t_LOG.man | 34 ---------------------------------- extensions/libipt_LOG.man | 34 ---------------------------------- extensions/libxt_LOG.man | 34 ++++++++++++++++++++++++++++++++++ 3 files changed, 34 insertions(+), 68 deletions(-) delete mode 100644 extensions/libip6t_LOG.man delete mode 100644 extensions/libipt_LOG.man create mode 100644 extensions/libxt_LOG.man
extensions/libip6t_LOG.man deleted +0 -34
@@ -1,34 +0,0 @@ -Turn on kernel logging of matching packets. When this option is set -for a rule, the Linux kernel will print some information on all -matching packets (like most IPv6 IPv6-header fields) via the kernel log -(where it can be read with -.I dmesg -or -.IR syslogd (8)). -This is a "non-terminating target", i.e. rule traversal continues at -the next rule. So if you want to LOG the packets you refuse, use two -separate rules with the same matching criteria, first using target LOG -then DROP (or REJECT). -.TP -\fB\-\-log\-level\fP \fIlevel\fP -Level of logging, which can be (system-specific) numeric or a mnemonic. -Possible values are (in decreasing order of priority): \fBemerg\fP, -\fBalert\fP, \fBcrit\fP, \fBerror\fP, \fBwarning\fP, \fBnotice\fP, \fBinfo\fP -or \fBdebug\fP. -.TP -\fB\-\-log\-prefix\fP \fIprefix\fP -Prefix log messages with the specified prefix; up to 29 letters long, -and useful for distinguishing messages in the logs. -.TP -\fB\-\-log\-tcp\-sequence\fP -Log TCP sequence numbers. This is a security risk if the log is -readable by users. -.TP -\fB\-\-log\-tcp\-options\fP -Log options from the TCP packet header. -.TP -\fB\-\-log\-ip\-options\fP -Log options from the IPv6 packet header. -.TP -\fB\-\-log\-uid\fP -Log the userid of the process which generated the packet.
extensions/libipt_LOG.man deleted +0 -34
@@ -1,34 +0,0 @@ -Turn on kernel logging of matching packets. When this option is set -for a rule, the Linux kernel will print some information on all -matching packets (like most IP header fields) via the kernel log -(where it can be read with -.I dmesg -or -.IR syslogd (8)). -This is a "non-terminating target", i.e. rule traversal continues at -the next rule. So if you want to LOG the packets you refuse, use two -separate rules with the same matching criteria, first using target LOG -then DROP (or REJECT). -.TP -\fB\-\-log\-level\fP \fIlevel\fP -Level of logging, which can be (system-specific) numeric or a mnemonic. -Possible values are (in decreasing order of priority): \fBemerg\fP, -\fBalert\fP, \fBcrit\fP, \fBerror\fP, \fBwarning\fP, \fBnotice\fP, \fBinfo\fP -or \fBdebug\fP. -.TP -\fB\-\-log\-prefix\fP \fIprefix\fP -Prefix log messages with the specified prefix; up to 29 letters long, -and useful for distinguishing messages in the logs. -.TP -\fB\-\-log\-tcp\-sequence\fP -Log TCP sequence numbers. This is a security risk if the log is -readable by users. -.TP -\fB\-\-log\-tcp\-options\fP -Log options from the TCP packet header. -.TP -\fB\-\-log\-ip\-options\fP -Log options from the IP packet header. -.TP -\fB\-\-log\-uid\fP -Log the userid of the process which generated the packet.
extensions/libxt_LOG.man new file +34 -0
@@ -0,0 +1,34 @@ +Turn on kernel logging of matching packets. When this option is set +for a rule, the Linux kernel will print some information on all +matching packets (like most IP header fields) via the kernel log +(where it can be read with +.I dmesg +or +.IR syslogd (8)). +This is a "non-terminating target", i.e. rule traversal continues at +the next rule. So if you want to LOG the packets you refuse, use two +separate rules with the same matching criteria, first using target LOG +then DROP (or REJECT). +.TP +\fB\-\-log\-level\fP \fIlevel\fP +Level of logging, which can be (system-specific) numeric or a mnemonic. +Possible values are (in decreasing order of priority): \fBemerg\fP, +\fBalert\fP, \fBcrit\fP, \fBerror\fP, \fBwarning\fP, \fBnotice\fP, \fBinfo\fP +or \fBdebug\fP. +.TP +\fB\-\-log\-prefix\fP \fIprefix\fP +Prefix log messages with the specified prefix; up to 29 letters long, +and useful for distinguishing messages in the logs. +.TP +\fB\-\-log\-tcp\-sequence\fP +Log TCP sequence numbers. This is a security risk if the log is +readable by users. +.TP +\fB\-\-log\-tcp\-options\fP +Log options from the TCP packet header. +.TP +\fB\-\-log\-ip\-options\fP +Log options from the IP packet header. +.TP +\fB\-\-log\-uid\fP +Log the userid of the process which generated the packet.
Signature · 1 line
1.7.2.5
Pablo Neira Ayuso
maintainerQuoted 5 lines · Mart Frauenlob
Quoted 4 lines · On 10.04.2013 18:30, [email protected] wrote:
Hello,
this patch on the man page unifies the IPv4 and IPv6 entries of the LOG target.
The new manpage has no more references about IPv6. It seems you have used IPv4 manpage with no mangling to also talk about IPv6. Fix this and resubmit. Thanks.