On 8/2/10 11:44 AM, Stephen Brown wrote: > I'm assuming the warning is just that, and can be safely ignored, but I > don't understand a default route not being added? I am however able to > keep traffic flowing bidirectional with eth0 being down so I can't > really figure that one out, unless it's hitting the gateway as defined > in providers (192.168.10.2 in my case) Just trying to understand how > this is working....
As I mentioned yesterday, these warnings are fine. They refer to the fact that there is now no default route defined in the main routing table. The reason that it still works is because you have specified 'fallback' for the other provider; that causes Shorewall to create a default route through that provider in the default routing table which is the 'routing table of last resort'. -Tom -- Tom Eastep \ When I die, I want to go like my Grandfather who Shoreline, \ died peacefully in his sleep. Not screaming like Washington, USA \ all of the passengers in his car http://shorewall.net \________________________________________________
signature.asc
Description: OpenPGP digital signature
------------------------------------------------------------------------------ The Palm PDK Hot Apps Program offers developers who use the Plug-In Development Kit to bring their C/C++ apps to Palm for a share of $1 Million in cash or HP Products. Visit us here for more details: http://p.sf.net/sfu/dev2dev-palm
_______________________________________________ Shorewall-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/shorewall-users
