From 3d69eae35aa83f6f681bb94f2ca4da5b5a733c06 Mon Sep 17 00:00:00 2001 From: paulgear Date: Mon, 26 Sep 2005 22:54:59 +0000 Subject: [PATCH] Clarify the relationship between providers and tcrules git-svn-id: https://shorewall.svn.sourceforge.net/svnroot/shorewall/trunk@2733 fbd18981-670d-0410-9b5c-8dc0c1a9a2bb --- Shorewall-docs2/Shorewall_and_Routing.xml | 10 +++++++--- 1 file changed, 7 insertions(+), 3 deletions(-) diff --git a/Shorewall-docs2/Shorewall_and_Routing.xml b/Shorewall-docs2/Shorewall_and_Routing.xml index e77a0b582..77da0c3e5 100644 --- a/Shorewall-docs2/Shorewall_and_Routing.xml +++ b/Shorewall-docs2/Shorewall_and_Routing.xml @@ -245,10 +245,14 @@ specify that outgoing connections are to be load-balanced between the two ISPs. Entries in /etc/shorewall/tcrules can be used to direct particular outgoing connections to one ISP or the - other. + other. Use of /etc/shorewall/tcrules is not + required for /etc/shorewall/providers 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. - Connections from the internet are automatically routed back out of - the correct interface and through the correct ISP gateway. This works + When using /etc/shorewall/providers, + 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 routed or port-forwarded to a system behind the firewall.