On 2008-04-10, Matthew Dempsky  wrote:

quoted text
> Assuming this is really a problem, could CARP use interface link state

> to speed up fail-over?  E.g., if the common setup is two routers with

> a direct Ethernet cable for pfsync and the common failure scenario is

> power failure (or at least something that brings down the pfsync

> device interface), when one router fails, the other could detect the

> link state change and then try to more aggressively contact the master

> before timing out and taking over.

Problem is, a carp interface is not interested in the state of the

syncdev, it is interested in the state of its own carpdev (since

multiple carp interfaces on a machine are independent). And carpdev

usually faces a switch, so it stays up.