DragonFly users List (threaded) for 2008-12
Re: Rework carp ipv4 support
On Sat, Dec 13, 2008 at 2:06 AM, Petr Janda
>> Configure inet address to carp(4) interface is no longer supported;
> Hi Sephe,
> May I ask what is the reason for this change?
Why do you need it? The route added by the inet address will never be
used, while the inet address will never be the source address of the
outgoing packets (you always need a backing inet address in other
The original inet address are just used to do following mapping:
target inet address (in arp) -> ether address (generated from vhid)
Mixing the carp inet address into the global inet address list and
hash table introduce great mess (take a look at how they generated
sha1 hash on the inet addresses, and various workaround added to
in_control) and actually do you no good.
Live Free or Die