The USE_DEFAULT_RT=Yes seems to fix my problems it :-) A few less serious issues to deal with.
When I restarted shorewall still had a default route left in main. something like default via 69.129.223.177 dev eth1 I removed it. I think it is because I have both default routes defined in /etc/network/interfaces. It was always there before but caused no harm as it was after the correct default route. I have not rebooted yet but suspect it will come back. Should I remove one of the gateways out of interfaces? Really should have asked this first but in http://www.shorewall.net/MultiISP.html has For most routing applications, Quagga <http://www.quagga.net/> is a better solution. I'm already running quagga and if it can be done I'm interested. I have a t1 (TDS) and a cable modem ( Charter ) , Particularly with the cable modem wouldn't think I would have sufficient a access to a routing protocol with the isp. Is it possible to be able to use quagga for this? When a isp is down need to temporarily disable it. I have done a could different methods. I have commented out providers and made scripts to change the default route. Is there a shorewall way to do it? John Thanks John John McMonagle wrote: > ospf doesn't touch the default route or local interface 192.168.2.0/23 > I'll try USE_DEFAULT_RT=Yes this weekend and see what happens. > > > Thanks for the input. > > > John > > -- John McMonagle IT Manager Advocap Inc. ------------------------------------------------------------------------------ This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword _______________________________________________ Shorewall-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/shorewall-users
