On 8/15/05, Luiz Otavio Souza <[EMAIL PROTECTED]> wrote: > Why CARP not send packets with physical CARP interface address ?
Unfortunately, I do not really understand the question and/or what you're trying to accomplish. Should anyone think I'm derailing, please bring a clue-by-four. Unless I'm badly mistaken, the reason CARP does not send the physical interface's address in its packets is the same reason why CARP works at all. Something which would explain the wording within the FAQ [1]: "No matter what the IP and MAC address of the local physical interface, packets sent to the CARP address are returned with the CARP information." At layer 2, machines deal with hardware addresses. Equipment links a specific IP address to a specific hardware (MAC) address through ARP. Suppose the hardware address is no longer available due to a crash, what machine will respond? None. CARP makes sure that there is always someone to answer a call for an IP address by keeping a specific MAC address alive and active. That is what makes a failover transparent. Sounds to me you do not want to mess with that as you'd properly undo CARP. Cheers, Rogier References: 1. OpenBSD FAQ - The Common Address Redundancy Protocol (CARP) http://www.openbsd.org/faq/faq6.html#CARP > > I think there is a some good reason for that. > > This will be usefull to check packets from CARP address with tcpdump. > > thanks, > luiz > > -- If you don't know where you're going, any road will get you there.
