CARP or similar functionality?

[Peter Seebach]

I've gotten a gig setting up a pair of routers with failover using CARP and
pfsync under OpenBSD.

This is sorta cool.

Does NetBSD have a nice simple way to have machines do automatic failover
like this?

-s

[Konrad Neuwirth]

Peter,

se...@plethora.net (Peter Seebach) writes:
> Does NetBSD have a nice simple way to have machines do automatic failover
> like this?

Theoretically, ucarp (a userland-implementation of the CARP protocol)
is in pkgsrc as net/ucarp. Practically, I haven't gotten it to work
with either -current or 2.0-BETA; I haven't had the time to debug or
upgrade the involved machines to 2.0-RC2.

Konrad

--
http://blog.fimsch.net/

[Pavel Cahyna]

I once wanted to do something similar by have two bridging firewalls (see
bridge(4) and the BRIDGE_IPF option). By using stp, only one would be
active at any time and STP (spanning-tree protocol) would take care of
failover. But I never did it (one firewall was reliable enough) so I do
not know if it works.

Bye Pavel

[Ty Sarna]

In article <200410080126....@herd.plethora.net> you write:
> This is sorta cool.
>
> Does NetBSD have a nice simple way to have machines do automatic failover
> like this?

I've used wackamole (http://www.backhand.org/wackamole/) on linux for IP
failover with good success. It also claims to run on FreeBSD, so I'd be
surprised if it was hard to get running on NetBSD.

[Werner Backes]

freeVRRPd claims to run on NetBSD. It seems interessting but
I never had time to give it a try.
See http://www.b0l.org/?idcategory=3&idsection=1 for more
information.

Werner

[Ben Collver]

On Fri, Oct 08, 2004 at 10:26:23AM -0400, Ty Sarna wrote:
> I've used wackamole (http://www.backhand.org/wackamole/) on linux for IP
> failover with good success. It also claims to run on FreeBSD, so I'd be
> surprised if it was hard to get running on NetBSD.

Just out of curiosity, do you use this with applications other than web
servers?

Ben

[Ty Sarna]

Works with LDAP too, and IIRC I even ssh'd to pool IPs for testing
(obviosuly ssh gets confused by the host key changing, etc).

Never tried it with anything other than TCP, but based on how it works I
would expect it to work fine with any IP protocol. It just adds/removes
IP aliases on interfaces, and does some ARP stuff to make sure other
machines notice the move.

It's also nice in that it's not just a "1 IP failed over from A to B"
system, it can manage a pool of M IP's over N machines, and it's OK
for M to be larger or smaller than N (or the same :-)