Re: Failover

[Bryan Irvine <bryan_(_dot_)_irvine_(_at_)_kingcountyjournal_(_dot_)_com>]

hmmm  I understand what you are saying, mark it as a higher metric, but
I'm hitting a wall in my brain.  Lets say all the users specify
192.168.0.1 as the default gateway, all of a sudden 192.168.0.1 dies,
how does machine 2 sitting at 192.168.0.2 know this, and assume the IP
address?

Or maybe I'm not thinking on the correct scale because I'm rather sleepy
right now.

--Bryan

On Tue, 2003-04-29 at 19:03, Chuck Yerkes wrote:
> Why not just use routing to handle this?
> Two paths out, one more expensive that the other.
> When the mainone dies, it gets marked as VERY expensive.
> 
> This is how all routing protocols work.
> 
> 
> Quoting Bryan Irvine (bryan_(_dot_)_irvine_(_at_)_kingcountyjournal_(_dot_)_com):
> > Is there something similar to mpathd for OBSD?
> > If not, how are some of you doing automatic failovers?
> > 
> > What about recovery detection?
> > 
> > Bascially I have an OBSD firewall, that is acting as a gateway for 2
> > LAN's and a DMZ with some critical apps that will be running on it.
> > 
> > I want to build a second firewall that will only come online in the
> > event of the first one failing.  I've done similar things before by
> > doing cron'd ping script, but that doesn't do very well at determining
> > if it failed at all or is just slow, or if it came back online.
> > 
> > Any ideas?
> > 
> > --Bryan