diff --git a/Shorewall-docs2/Shorewall_and_Routing.xml b/Shorewall-docs2/Shorewall_and_Routing.xml index 7a155e969..61dda4229 100644 --- a/Shorewall-docs2/Shorewall_and_Routing.xml +++ b/Shorewall-docs2/Shorewall_and_Routing.xml @@ -15,7 +15,7 @@ - 2005-09-25 + 2005-11-16 2005 @@ -244,11 +244,11 @@ Entries in /etc/shorewall/providers can 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. Use of /etc/shorewall/tcrules is not - required for /etc/shorewall/providers to work, but - you must select a unique MARK value for each provider so Shorewall can - set up the correct marking rules for you. + used to direct particular outgoing connections to one ISP or the other. + Use of /etc/shorewall/tcrules is not required for + /etc/shorewall/providers to work, but you must + select a unique MARK value for each provider so Shorewall can set up the + correct marking rules for you. When using /etc/shorewall/providers, connections from the internet are automatically routed back out of the @@ -563,6 +563,13 @@ net net DROP eth0 eth2 206.124.146.176 eth1 eth2 130.252.99.27 + + Entries in /etc/shorewall/masq have no + effect on which ISP a particular connection will be sent through. That + is rather the purpuse of entries in + /etc/shorewall/tcrules. + + Now suppose that you want to route all outgoing SMTP traffic from your local network through ISP 2. You would make this entry in /etc/shorewall/tcrules (and you would @@ -574,4 +581,4 @@ eth1 eth2 130.252.99.27 2:P <local network> 0.0.0.0/0 tcp 25 - + \ No newline at end of file