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

Clarify the relationship between providers and tcrules

Browse Source 
git-svn-id: https://shorewall.svn.sourceforge.net/svnroot/shorewall/trunk@2733 fbd18981-670d-0410-9b5c-8dc0c1a9a2bb
This commit is contained in:
paulgear 2005-09-26 22:54:59 +00:00
parent 0587f6a69e
commit 3d69eae35a
1 changed files with 7 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
Shorewall-docs2/Shorewall_and_Routing.xml
View File

@ -245,10 +245,14 @@
specify that outgoing connections are to be load-balanced between the specify that outgoing connections are to be load-balanced between the
two ISPs. Entries in <filename>/etc/shorewall/tcrules</filename> can be two ISPs. Entries in <filename>/etc/shorewall/tcrules</filename> can be
used to direct particular outgoing connections to one ISP or the used to direct particular outgoing connections to one ISP or the
other.</para> other. Use of <filename>/etc/shorewall/tcrules</filename> is not
required for <filename>/etc/shorewall/providers</filename> to work, but
but you must select a unique MARK value for each provider so Shorewall
can set up the correct marking rules for you.</para>
<para>Connections from the internet are automatically routed back out of <para>When using <filename>/etc/shorewall/providers</filename>,
the correct interface and through the correct ISP gateway. This works connections from the internet are automatically routed back out of the
correct interface and through the correct ISP gateway. This works
whether the connection is handled by the firewall itself or if it is whether the connection is handled by the firewall itself or if it is
routed or port-forwarded to a system behind the firewall.</para> routed or port-forwarded to a system behind the firewall.</para>