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

Clarify that route_rules entries are perminent

Browse Source 
git-svn-id: https://shorewall.svn.sourceforge.net/svnroot/shorewall/trunk@4584 fbd18981-670d-0410-9b5c-8dc0c1a9a2bb
This commit is contained in:
teastep 2006-09-24 19:06:48 +00:00
parent 28a551a50e
commit 4dc8a252f2
1 changed files with 16 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

17
docs/MultiISP.xml
View File

@ -474,7 +474,7 @@
<filename>/etc/shorewall/tcrules</filename> and you must do that marking
in the PREROUTING chain.</para>
<warning>
<warning id="Undo">
<para>Entries in <filename>/etc/shorewall/providers</filename>
permanently alter your firewall/gateway's routing; that is, the effect
of these changes is not reversed by <command>shorewall stop</command>
@ -662,6 +662,21 @@ eth1 eth2 130.252.99.27</programlisting>
the two files is that entries in <filename>route_rules</filename> are
independent of Netfilter.</para>
<warning>
<para>Entries in <filename>/etc/shorewall/route_rules</filename>
permanently alter your firewall/gateway's routing; that is, the effect
of these changes is not reversed by <command>shorewall stop</command>
or <command>shorewall clear</command>. To restore routing to its
original 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
distribution's networking documentation.</para>
<para>Please also see the <link linkend="Undo">warning in the section
above entitled <emphasis>What an Entry in the Providers File
Does</emphasis></link>.</para>
</warning>
<section>
<title>Routing Rules</title>