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

Add FAQ 6c re: dmesg

Browse Source
This commit is contained in:
Tom Eastep 2010-03-12 12:22:39 -08:00
parent a2ac726ce9
commit 472425cc62
1 changed files with 13 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
docs/FAQ.xml
View File

@ -1186,7 +1186,8 @@ to debug/develop the newnat interface.</programlisting></para>
LOGBURST=""</programlisting> LOGBURST=""</programlisting>
<para>It is also possible to <ulink url="shorewall_logging.html">set up <para>It is also possible to <ulink url="shorewall_logging.html">set up
Shorewall to log all of its messages to a separate file</ulink>.</para> Shorewall to log all of Netfilter's messages to a separate
file</ulink>.</para>
<section id="faq6a"> <section id="faq6a">
<title>(FAQ 6a) Are there any log parsers that work with <title>(FAQ 6a) Are there any log parsers that work with
@ -1254,6 +1255,17 @@ DROP net fw udp 10619</programlisting>
- udp 10619</programlisting> - udp 10619</programlisting>
</section> </section>
<section id="faq6c">
<title>(FAQ 6c) cat /proc/sys/kernel/prink returns '4 4 1 7' and still
I get dmesg filled up</title>
<para><emphasis role="bold">Answer</emphasis>: While we would argue
that 'dmesg filled up' is not necessarily a problem, the only way to
eliminate that is to <ulink url="shorewall_logging.html">set up
Shorewall to log all of Netfilter's messages to a separate
file</ulink>.</para>
</section>
<section id="faq6d"> <section id="faq6d">
<title>(FAQ 6d) Why is the MAC address in Shorewall log messages so <title>(FAQ 6d) Why is the MAC address in Shorewall log messages so
long? I thought MAC addresses were only 6 bytes in length.</title> long? I thought MAC addresses were only 6 bytes in length.</title>