Re: Failover

Quoting Bryan Irvine (bryan.irvine@kingcountyjournal.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?

If you use a routing protocol, not a static (default) route, then the routing daemon will handle it. OSPF is best, RIP might be acceptable.

Routed runs fine on my Macs, all Unix and there's something on Windows, I'm sure.

For a full failover daemon, you need to have the secondary be able to "see" the primary this means heartbeats over several paths including, ideally, the inside and outside interfaces and perhaps a private interface (Veritas HA does it over SCSI when sharing SCSI disks which we never did at Fusion Systems->OpenVision, serial via SLIP or just a "talker/listener" can work).

Are you solding a problem that actually exists or theorizing one?

I had routing/filtering firewalls with proxies that were up for 200-400 days at a time. A failure you have been fixed by bringing it down all the way and doing "ifconfig $INSIDE_IF alias $otherIP" on the second firewall (which mostly just ran an HTTP proxy). E.g. I over engineered the firewalls (too cool, too much power) and they never went down.

> Or maybe I'm not thinking on the correct scale because I'm rather sleepy

Do you need help?

In addition to our free technical library, Pantek provides professional IT services to companies who utilize Open Source software: Learn more about Pantek's Technical Support offerings Place an order for 24/7/365 Technical Support here Learn more about Pantek, who we are, and what we do Chat with a Live Operator Related openbsd.org Links advocacy announce bugs ipv6 misc ports ports-changes security-announce smp source-changes tech Request more information about Pantek

> On Tue, 2003-04-29 at 19:03, Chuck Yerkes wrote:
Received on Wed Apr 30 13:11:01 2003