holm/shorewall_code
1
0
Fork 0
forked from extern/shorewall_code
Code Pull Requests Activity

Clarify iptrace logging.

Browse Source 
Signed-off-by: Tom Eastep <teastep@shorewall.net>
This commit is contained in:
Tom Eastep 2014-09-24 09:14:38 -07:00
parent ba7f88c912
commit a7b57ad32c
2 changed files with 18 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
Shorewall/manpages/shorewall.xml
View File

@ -1129,11 +1129,15 @@
be one or more matches that may appear in both the raw table OUTPUT
and raw table PREROUTING chains.</para>
<para>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.</para>
<para>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.</para>
<para>In either case, Shorewall has no control over where the
messages are written; consult your logging daemon's
documentation.</para>
</listitem>
</varlistentry>

14
Shorewall6/manpages/shorewall6.xml
View File

@ -1012,11 +1012,15 @@
be one or more matches that may appear in both the raw table OUTPUT
and raw table PREROUTING chains.</para>
<para>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.</para>
<para>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.</para>
<para>In either case, Shorewall has no control over where the
messages written; consult your logging daemon's
documentation.</para>
</listitem>
</varlistentry>