From a7b57ad32c74902b617740500b22837b515195fd Mon Sep 17 00:00:00 2001 From: Tom Eastep Date: Wed, 24 Sep 2014 09:14:38 -0700 Subject: [PATCH] Clarify iptrace logging. Signed-off-by: Tom Eastep --- Shorewall/manpages/shorewall.xml | 14 +++++++++----- Shorewall6/manpages/shorewall6.xml | 14 +++++++++----- 2 files changed, 18 insertions(+), 10 deletions(-) diff --git a/Shorewall/manpages/shorewall.xml b/Shorewall/manpages/shorewall.xml index 574acf04f..9de7dbd16 100644 --- a/Shorewall/manpages/shorewall.xml +++ b/Shorewall/manpages/shorewall.xml @@ -1129,11 +1129,15 @@ be one or more matches that may appear in both the raw table OUTPUT and raw table PREROUTING chains. - The trace records are written to the kernel's log buffer with - facility = kernel and priority = warning, and they are routed from - there by your logging daemon (syslogd, rsyslog, syslog-ng, ...) -- - Shorewall has no control over where the messages go; consult your - logging daemon's documentation. + When using ipt_LOG, the trace records are written to the + kernel's log buffer with facility = kernel and priority = warning, + and they are routed from there by your logging daemon (syslogd, + rsyslog, syslog-ng, ...). When using nfnetlink_log or ipt_ULOG, the + trace records go to ulogd. + + In either case, Shorewall has no control over where the + messages are written; consult your logging daemon's + documentation. diff --git a/Shorewall6/manpages/shorewall6.xml b/Shorewall6/manpages/shorewall6.xml index f9fbfd712..df52794e4 100644 --- a/Shorewall6/manpages/shorewall6.xml +++ b/Shorewall6/manpages/shorewall6.xml @@ -1012,11 +1012,15 @@ be one or more matches that may appear in both the raw table OUTPUT and raw table PREROUTING chains. - The trace records are written to the kernel's log buffer with - facility = kernel and priority = warning, and they are routed from - there by your logging daemon (syslogd, rsyslog, syslog-ng, ...) -- - Shorewall has no control over where the messages go; consult your - logging daemon's documentation. + When using ipt6_LOG, the trace records are written to the + kernel's log buffer with facility = kernel and priority = warning, + and they are routed from there by your logging daemon (syslogd, + rsyslog, syslog-ng, ...). When using nfnetlink_log or ipt_ULOG, the + trace records go to ulogd. + + In either case, Shorewall has no control over where the + messages written; consult your logging daemon's + documentation.