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

Amplify the route filtering problem in the multi-ISP document.

Browse Source 
Signed-off-by: Tom Eastep <teastep@shorewall.net>
This commit is contained in:
Tom Eastep 2014-07-13 07:45:51 -07:00
parent 53dda803e2
commit 3e6e0b4a09
1 changed files with 16 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

18
docs/MultiISP.xml
View File

@ -750,8 +750,10 @@ eth1 0.0.0.0/0 130.252.99.27</programlisting>
<title>Martians</title>
<para>One problem that often arises with Multi-ISP configuration is
'Martians'. If your Internet interfaces are configured with the
<emphasis role="bold">routefilter</emphasis> option in
'Martians'. If you set ROUTE_FILTER=Yes in
<filename>/etc/shorewall/shorewall.conf</filename> or if your Internet
interfaces are configured with the <emphasis
role="bold">routefilter</emphasis> option in
<filename>/etc/shorewall/interfaces</filename> (remember that if you set
that option, you should also select <emphasis
role="bold">logmartians</emphasis>), then things may not work correctly
@ -810,6 +812,18 @@ DROP:info net:192.168.1.0/24 all</programlisting>
<para>Be sure the above rule is added before any other rules with
<emphasis>net</emphasis> in the SOURCE column.</para>
<important>
<para>If you set ROUTE_FILTER=Yes in
<filename>/etc/shorewall/shorewall.conf</filename>, then setting
<emphasis role="bold">routefilter</emphasis>=0 in <ulink
url="manpages/shorewall-interfaces.html">shorewall-interfaces</ulink>
(5) will not disable route filtering on a given interface. You must
set ROUTE_FILTER=No in <ulink
url="manpages/shorewall-interfaces.html">shorewall-interfaces</ulink>
(5), then set the <emphasis role="bold">routefilter</emphasis> option
on those interfaces on which you want route filtering.</para>
</important>
</section>
<section id="Example1">