From 934f5d81a880a8bc175539957f23fdd94e805ae4 Mon Sep 17 00:00:00 2001
From: teastep <teastep@fbd18981-670d-0410-9b5c-8dc0c1a9a2bb>
Date: Fri, 24 Aug 2007 23:47:13 +0000
Subject: [PATCH] Add a suggestion about route_rule with SOURCE='lo'

git-svn-id: https://shorewall.svn.sourceforge.net/svnroot/shorewall/trunk@7220 fbd18981-670d-0410-9b5c-8dc0c1a9a2bb
---
 docs/MultiISP.xml | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/docs/MultiISP.xml b/docs/MultiISP.xml
index 7113112bc..067938c74 100644
--- a/docs/MultiISP.xml
+++ b/docs/MultiISP.xml
@@ -841,6 +841,12 @@ eth3             eth2              16.105.78.4</programlisting></para>
           connections on.</para>
         </listitem>
       </itemizedlist>
+
+      <para>Note that some traffic originating on the firewall doesn't have a
+      SOURCE IP address before routing. At least one Shorewall user reports
+      that an entry in <filename>/etc/shorewall/route_rules</filename> with
+      'lo' in the SOURCE column seems to be the most reliable way to direct
+      such traffic to a particular ISP.</para>
     </section>
 
     <section id="route_rules">