On Tue, Feb 12, 2008 at 01:42:19PM -0500, Brian J. Murrell wrote: > That's a fair point, except that I don't know that quagga actually does > anything to solve the problem. The problem being specifically, the > management of multiple default routes on interface availability. AFAIK, > quagga will not plumb default routes via a newly available interface and > replumb routes when an interface goes away.
If you place 'static' routes in zebra.conf, thusly: ip route 10.1.0.1/32 10.1.100.2 then quagga will insert and remove them as their destinations become available and go away, for whatever reason, including link status. This does work with default routes as well. That combined with suitably crafted routing tables should be sufficient, if I've understood your problem correctly. > Quagga will also not manage > the required provider tables to ensure the symmetric routing that is > required. Indeed, you have to do that bit on your own - but it's static and quite simple. I haven't actually built one of these, but I'm fairly sure it can be done. ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Shorewall-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/shorewall-users
