Subject: Re: CARP Committed (correctly presented)
To: NetBSD Current Users <current-users@NetBSD.org>
From: Peter Eisch <firstname.lastname@example.org>
Date: 05/18/2006 11:13:35
On 5/18/06 11:03 AM, "Herb Peyerl" <email@example.com> wrote:
> On 18-May-06, at 9:57 AM, Liam J. Foy wrote:
>> CARP works by allowing a group of hosts on the same network segment to
>> share an IP address. This group of hosts is referred to as a
>> "redundancy group". The redundancy group is assigned an IP Address
>> that is shared amongst the group members. Within the group, one host
>> is designated the "master" and the rest as "backups". The master host
>> is the one that currently "holds" the shared IP; it responds to any
>> traffic or ARP requests directed towards it. Each host may belong
>> to more than one redundancy group at a time.
> Does CARP use the same gratuitous ARP method of transitioning from
> Slave to Master that keepalived uses? If so, it has the same
> weaknesses as keepalived and isn't really all that useful...
> (Many switches/routers ignore gratuitous ARP's and hence, you have to
> wait for an ARP timeout before a new Master receives any packets).
But even that is better than needing manual intervention, isn't it? If I
knew more about pfsync I could actually answer that question.
I like this addition though!