On Mon, 2008-01-14 at 14:28 -0800, Tom Eastep wrote: > Andrew Suffield wrote: > > On Mon, Jan 14, 2008 at 12:58:32PM -0800, Tom Eastep wrote:. > >> Depending on whether your providers support routing protocols on the > >> gateway routers. > > > > It works without that if the interfaces go up and down at the > > appropriate moments (ie, they're ppp interfaces or something > > similar). In that configuration it's a routing network consisting of a > > single host with no routing protocols running, which is a little > > weird, but functional. You simply give zebra a bunch of static routes > > with suitable metrics, and it inserts and removes them as the > > interfaces change state. > > Interesting.
Interesting, yes, but in my experience, the vast majority of ISP troubles are blackholes after the last mile connection. IOW, interface to the ISP stays up but nothing you send via the ISP goes anywhere. Thi s especially true of the bridged ethernet/DHCP type outfits like the Cable companies. My cable could be sliced outside my house and my interface will stay up. The news with DSL/PPPoE is a bit better. If my phone line dies the PPP interface will go down. That is only due to the keep-alive mechanism built into PPP that one can enable. Sure one could probably cobble up a keep-alive for bridged ethernet situations and fiddle with interfaces based on it but what would be more interesting though would be for quagga to have that ability built in. A lot of this goes back to Tom's past assertions that Linux needs a good/proper routing solution. I tend to agree with him. I have not really thought about requirements for such a beast but I do know that trying to manage routing and routing tables in linux is akin to programming in assembler. b.
signature.asc
Description: This is a digitally signed message part
------------------------------------------------------------------------- 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
