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

Renumber FAQ76c to FAQ78

Browse Source 
git-svn-id: https://shorewall.svn.sourceforge.net/svnroot/shorewall/trunk@8716 fbd18981-670d-0410-9b5c-8dc0c1a9a2bb
This commit is contained in:
teastep 2008-09-15 15:13:01 +00:00
parent 229bd6516a
commit aba87edf7e
1 changed files with 13 additions and 12 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

25
docs/FAQ.xml
View File

@ -162,18 +162,6 @@
<para><emphasis role="bold">Answer:</emphasis> See <link
linkend="faq76">above</link>.</para>
</section>
<section id="faq76c">
<title>(faq 77c) After restart and bootup of my Debian firewall, all
traffic is blocked for hosts behind the firewall trying to connect out
onto the net or through the vpn (although i can reach the internal
firewall interface and obtain dumps etc). Once I issue 'shorewall
clear' followed by 'shorewall restart' it then works, despite the
config not changing</title>
<para>Answer: Set IP_FORWARDING=On in <filename><ulink
url="manpages/shorewall.conf.html">/etc/shorewall/shorewall.conf</ulink></filename>.</para>
</section>
</section>
</section>
@ -2010,6 +1998,19 @@ iptables: Invalid argument
will have mark = 1 and will be sent via ISP1. That will work whether
<emphasis role="bold">balance</emphasis> is specified or not!</para>
</section>
<section id="faq78">
<title>(FAQ 78) After restart and bootup of my Debian firewall, all
traffic is blocked for hosts behind the firewall trying to connect out
onto the net or through the vpn (although i can reach the internal
firewall interface and obtain dumps etc). Once I issue 'shorewall clear'
followed by 'shorewall restart' it then works, despite the config not
changing</title>
<para><emphasis role="bold">Answer:</emphasis> Set IP_FORWARDING=On in
<filename><ulink
url="manpages/shorewall.conf.html">/etc/shorewall/shorewall.conf</ulink></filename>.</para>
</section>
</section>
<section id="TC">