[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- To: misc_(_at_)_openbsd_(_dot_)_org
- Subject: Re: Failover
- From: Chuck Yerkes <chuck+obsd_(_at_)_2003_(_dot_)_snew_(_dot_)_com>
- Date: Tue, 29 Apr 2003 22:03:03 -0400
- Mail-followup-to: Chuck Yerkes <chuck+obsd_(_at_)_2003_(_dot_)_snew_(_dot_)_com>, misc_(_at_)_openbsd_(_dot_)_org
- Reply-to: misc_(_at_)_openbsd_(_dot_)_org
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?
Visit your host, monkey.org