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

Add advice about IP_FORWARDING=Yes to FAQ 2

Browse Source 
git-svn-id: https://shorewall.svn.sourceforge.net/svnroot/shorewall/trunk@3671 fbd18981-670d-0410-9b5c-8dc0c1a9a2bb
This commit is contained in:
teastep 2006-03-15 03:45:49 +00:00
parent 28bf7acdea
commit 9d24ac3fc0
1 changed files with 11 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
docs/FAQ.xml
View File

@ -17,7 +17,7 @@
</author>
</authorgroup>
<pubdate>2006-03-11</pubdate>
<pubdate>2006-03-14</pubdate>
<copyright>
<year>2001-2006</year>
@ -543,6 +543,15 @@ DNAT loc dmz:192.168.2.4 tcp 80 - $ETH0
restore</command></ulink>.</para>
</warning>
</section>
<section id="faq2c">
<title>(FAQ 2c) I tried to apply the answer to FAQ 2 to my external
interface and the net zone and it didn't work. Why?</title>
<para><emphasis role="bold">Answer</emphasis>: Did you set <emphasis
role="bold">IP_FORWARDING=Yes</emphasis> in
<filename>shorewall.conf</filename>?</para>
</section>
</section>
</section>
@ -1656,7 +1665,7 @@ iptables: Invalid argument
<para>Netfilter/iptables doesn't fully support IPSEC in the 2.6
Kernels prior to 2.6.16 -- kernel and iptables patches are available
and the details may be found at the <ulink
url="IPSEC-2.6.html">Shorewall IPSEC-2.6 page</ulink>. </para>
url="IPSEC-2.6.html">Shorewall IPSEC-2.6 page</ulink>.</para>
</listitem>
<listitem>