On Wed, 2007-02-07 at 23:36 -0600, Jerry Vonau wrote: > > Yup, part III is about right, that is why you need to point to a table > (main) that has the route available, that is the whole point of the > route_rules file.
Ahhh. > Now instead of adding a route to the providers table, add an "ip rule" > instead. "ip rule add to 10.75.23.0/24 pref 9999 lookup main" and > retest. Yeah, that does the trick. > That is more or less an entry that could be created with the > route_rules file. Now the example route_rules entry: # #SOURCE DEST PROVIDER PRIORITY # - 10.8.0.0/24 main 1000 make sense. It seems I can do exactly what you suggested above with the 9999 ip rule entry with that route_rules and not tie it to a provider. Thanx for helping me see that more clearly! > Working now? About to test the same route_rule as I did manually. I am sure it will work now. b. -- My other computer is your Microsoft Windows server. Brian J. Murrell
signature.asc
Description: This is a digitally signed message part
------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier. Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________ Shorewall-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/shorewall-users
