extern/shorewall_code
1
0
Fork 1
mirror of https://gitlab.com/shorewall/code.git synced 2024-11-22 15:43:30 +01:00
Code Issues Packages Projects Releases Wiki Activity

Update Multi-ISP doc for 3.4

Browse Source 
git-svn-id: https://shorewall.svn.sourceforge.net/svnroot/shorewall/trunk@5247 fbd18981-670d-0410-9b5c-8dc0c1a9a2bb
This commit is contained in:
teastep 2007-01-17 20:47:00 +00:00
parent ae71fc3cc2
commit ffe74cda54
1 changed files with 17 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

25
docs/MultiISP.xml
View File

@ -91,6 +91,13 @@
<command>shorewall restart</command>). Ideally, restarting the packet <command>shorewall restart</command>). Ideally, restarting the packet
filter should have no effect on routing.</para> filter should have no effect on routing.</para>
</listitem> </listitem>
<listitem>
<para>Prior to Shorewall 3.4.0, the routes and route rules added by
this support were not completely removed during <command>shorewall
stop</command>, <command>shorewall clear</command> or
<command>shorewall restart</command>.</para>
</listitem>
</itemizedlist> </itemizedlist>
<section> <section>
@ -142,7 +149,7 @@
<para>Shorewall will set up the routing and will update the <para>Shorewall will set up the routing and will update the
<filename>/etc/iproute2/rt_tables</filename> to include the table names <filename>/etc/iproute2/rt_tables</filename> to include the table names
and number of the tables that it adds.</para> and numbers of the tables that it adds.</para>
<caution> <caution>
<para>This feature uses <ulink url="traffic_shaping.htm">packet <para>This feature uses <ulink url="traffic_shaping.htm">packet
@ -488,15 +495,17 @@
particular provider then you <emphasis>must </emphasis>mark that traffic particular provider then you <emphasis>must </emphasis>mark that traffic
with the provider's MARK value in with the provider's MARK value in
<filename>/etc/shorewall/tcrules</filename> and you must do that marking <filename>/etc/shorewall/tcrules</filename> and you must do that marking
in the PREROUTING chain.</para> in the PREROUTING chain; or, you must provide the appropriate rules in
<filename>/etc/shorewall/route_rules</filename>.</para>
<warning id="Undo"> <warning id="Undo">
<para>Entries in <filename>/etc/shorewall/providers</filename> <para>If you are running a Shorewall version prior to 3.4.0, entries
permanently alter your firewall/gateway's routing; that is, the effect in <filename>/etc/shorewall/providers</filename> permanently alter
of these changes is not reversed by <command>shorewall stop</command> your firewall/gateway's routing; that is, the effect of these changes
or <command>shorewall clear</command>. To restore routing to its is not reversed by <command>shorewall stop</command> or
original state, you may have to restart your network. This can usually <command>shorewall clear</command>. To restore routing to its original
be done by <command>/etc/init.d/network restart</command> or state, you may have to restart your network. This can usually be done
by <command>/etc/init.d/network restart</command> or
<command>/etc/init.d/networking restart</command>. Check your <command>/etc/init.d/networking restart</command>. Check your
distribution's networking documentation.</para> distribution's networking documentation.</para>