On Fri, 2 Feb 2001, Rene 'Lynx' Pfeiffer wrote:
> On Thu, 1 Feb 2001, Arthur van Leeuwen wrote:
>
> > On Thu, 1 Feb 2001, Rene 'Lynx' Pfeiffer wrote:
> >
> > > On Thu, 1 Feb 2001, Arthur van Leeuwen wrote:
> > >
> > > > On Thu, 1 Feb 2001, bert hubert wrote:
> > > >
> > > > > Linux is supposed to have something called 'dead gateway detection'
> > > >
> > > > Which it doesn't use when there's a multipath default route. Now, that isn't
> > > > technically the case here, so that shouldn't be the problem here.
> > >
> > > Does this mean that Linux automatically detects a failed default
> > > route and takes the second one if I configure two default routes?
> >
> > No, it means the exact opposite. If you configure two default routes
> > Linux will randomly multiplex outgoing connections over the two routes.
>
> This is exactly the problem I am having. I am trying to set up a spare default
> route in case the primary route is down. The router in question is a Linux
> machine having access to three upstream connections and to the DMZ. I do not
> want to have routing daemons on the box, I simply want to change the default
> route in case the primary connection (which supplies the LAN behind the DMZ)
> is down.
> The only thing I have come up so far (I do not want to have fancy things like
> zebra, routed or gated on this machine) is a Perl script that measures the
> connectivity and takes action if it detects that the route is down.
> Does anyone have a better idea? (I am willing to to a nice and tidy ASCIIgram
> if you like ;-)
Nope. Polling for connectivity is what you're stuck with doing, unless you
want to do some kernel hacking.
Doei, Arthur. (Who is thinking about actually doing the latter... it's
*useful*, in more cases than one)
--
/\ / | arthurvl@xxxxxxxxxx | Work like you don't need the money
/__\ / | A friend is someone with whom | Love like you have never been hurt
/ \/__ | you can dare to be yourself | Dance like there's nobody watching
