extern/shorewall_code
1
0
Fork 1
mirror of https://gitlab.com/shorewall/code.git synced 2025-01-08 22:58:50 +01:00
Code Issues Packages Projects Releases Wiki Activity

Add FAQ 104

Browse Source 
Signed-off-by: Tom Eastep <teastep@shorewall.net>
This commit is contained in:
Tom Eastep 2014-10-01 19:47:56 -07:00
parent 770a505cd2
commit 205dd6e250
1 changed files with 17 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

18
docs/FAQ.xml
View File

@ -2309,10 +2309,26 @@ gateway:~# </programlisting>
<title>(FAQ 103) Shorewall fails to start at boot but will start <title>(FAQ 103) Shorewall fails to start at boot but will start
immediately after</title> immediately after</title>
<para>Answer: This is usually associated with SELinux. <ulink <para><emphasis role="bold">Answer:</emphasis> This is usually
associated with SELinux. <ulink
url="https://lists.fedoraproject.org/pipermail/selinux/2010-June/012680.html">Here</ulink> url="https://lists.fedoraproject.org/pipermail/selinux/2010-June/012680.html">Here</ulink>
is an example.</para> is an example.</para>
</section> </section>
<section id="faq104">
<title>(FAQ 104) I see <emphasis>kernel</emphasis> messages in my log
when I start or restart Shorewall or Shorewall6</title>
<para>Example: </para>
<programlisting>&gt; Oct 1 13:04:39 deb kernel: [ 9570.619744] xt_addrtype: ipv6 does not support BROADCAST matching
</programlisting>
<para><emphasis role="bold">Answer:</emphasis> These are harmless.
Shorewall attempts to execute various commands to determine the
capabiities of your system. If you system doesn't support a command, it
will generally issue a kernel log message.</para>
</section>
</section> </section>
<section id="MultiISP"> <section id="MultiISP">