"Fossies" - the Fresh Open Source Software Archive  

Source code changes of the file "Shorewall_and_Routing.xml" between
shorewall-docs-xml-5.2.3.6.tar.bz2 and shorewall-docs-xml-5.2.6.tar.bz2

About: Shorewall (The Shoreline Firewall) is an iptables based firewall (documentation; XML)

Shorewall_and_Routing.xml  (shorewall-docs-xml-5.2.3.6.tar.bz2):Shorewall_and_Routing.xml  (shorewall-docs-xml-5.2.6.tar.bz2)
skipping to change at line 182 skipping to change at line 182
<para>So again in this case, the only influence that Shorewall has over <para>So again in this case, the only influence that Shorewall has over
the packet destination is NAT or marking.</para> the packet destination is NAT or marking.</para>
</section> </section>
</section> </section>
<section id="RoutingTables"> <section id="RoutingTables">
<title>Alternate Routing Table Configuration</title> <title>Alternate Routing Table Configuration</title>
<para>The Shorewall 2.x <ulink <para>The Shorewall 2.x <ulink
url="http://www.shorewall.net/2.0/Shorewall_Squid_Usage.html#Local">Shorewal l url="https://shorewall.org/2.0/Shorewall_Squid_Usage.html#Local">Shorewall
Squid documentation</ulink> shows how alternate routing tables can be Squid documentation</ulink> shows how alternate routing tables can be
created and used. That documentation shows how you can use logic in created and used. That documentation shows how you can use logic in
<filename>/etc/shorewall/init</filename> to create and populate an <filename>/etc/shorewall/init</filename> to create and populate an
alternate table and to add a routing rule for its use. It is fine to use alternate table and to add a routing rule for its use. It is fine to use
that technique so long as you understand that you are basically just using that technique so long as you understand that you are basically just using
the Shorewall init script (<filename>/etc/init.d/shorewall</filename>) to the Shorewall init script (<filename>/etc/init.d/shorewall</filename>) to
configure your alternate routing table at boot time and that <emphasis configure your alternate routing table at boot time and that <emphasis
role="bold">other than as described in the previous section, there is no role="bold">other than as described in the previous section, there is no
connection between Shorewall and routing when using Shorewall versions connection between Shorewall and routing when using Shorewall versions
prior to 2.3.2.</emphasis></para> prior to 2.3.2.</emphasis></para>
 End of changes. 1 change blocks. 
1 lines changed or deleted 1 lines changed or added

Home  |  About  |  Features  |  All  |  Newest  |  Dox  |  Diffs  |  RSS Feeds  |  Screenshots  |  Comments  |  Imprint  |  Privacy  |  HTTP(S)