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

Remove 'detectnets' recommendation from the FAQ

Browse Source 
git-svn-id: https://shorewall.svn.sourceforge.net/svnroot/shorewall/trunk@7378 fbd18981-670d-0410-9b5c-8dc0c1a9a2bb
This commit is contained in:
teastep 2007-09-21 17:29:28 +00:00
parent 808b7fc0a1
commit fddd1835e9
1 changed files with 7 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
docs/FAQ.xml
View File

@ -1627,13 +1627,13 @@ Creating input Chains...
<para><emphasis role="bold">Answer:</emphasis> The above output is
perfectly normal. The Net zone is defined as all hosts that are
connected through eth0 and the local zone is defined as all hosts
connected through <filename class="devicefile">eth1</filename>. If you
are running Shorewall 1.4.10 or later, you can consider setting the
<ulink url="manpages/shorewall-interfaces.html"> <emphasis
role="bold">detectnets</emphasis> interface option</ulink> on your local
interface (<filename class="devicefile">eth1</filename> in the above
example). That will cause Shorewall to restrict the local zone to only
those networks routed through that interface.</para>
connected through <filename class="devicefile">eth1</filename>. You can
set the <emphasis role="bold">routefilter</emphasis> option on an
internal interface if you wish to guard against
'<firstterm>Martians</firstterm>' (a Martian is a packet with a source
IP address that is not routed out of the interface on which the packet
was received). If you do that, it is a good idea to also set the
<emphasis role="bold">logmartians</emphasis> option.</para>
</section>
<section id="faq22">