On 8/1/05, Randy B <[EMAIL PROTECTED]> wrote: > So CARP by design (and uncontrollably so) sends it's management packets > out the interface it's balancing. Seems counter-intuitive to me; it's > just multicast, so I would think you should be able to direct it > wherever need be. At least I've got pfsync on a dedicated NIC.
At layer 2 carp sends out gratuitous ARP (and replies) so that all other devices on that network know how to get to it. At layer 3, carp sends out the multicast advertisements (much like VRRP and HSRP) so that it's peers can determine if they are primary or not. Because it's designed so that the secondary machines are purely passive, it needs a way to detect if the primary goes down for reasons the primary may not be aware of (failure between two switches, partial NIC failure, etc). Any failure mechanism that relies on the primary specifically telling the secondaries that it's no longer able to service it's virtual address means creating an exhaustive list (of near infinite) failure modes to monitor and check against. --Bill --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
