FreeBSD + carp on VMWare ESX

[Matthew Grooms]

The other options you mention are enabled by default. This problem  
also effects pre vSphere versions but only under certain  
circumstances. Others claim this is only an issue when NIC teaming is  
in use. However, I disabled this feature and still experience the  
problem without the patch applied.

I'll be happy to post the config when I'm back in front of the  
computer. It's not a configuration problem. I'm not new to FreeBSD or  
carp and have quite a bit of time invested trying to get this to work.

Have a look at the vmware forums. A lot of folks have reported the  
problem in great detail and, as far as I can tell, have yet to get  
this working.

-Matthew

On Jul 19, 2009, at 5:56 PM, Andrew Snow <andrew at modulus.org> wrote:

> Matthew Grooms wrote:
>> I was having problems running carp on VMWare ESX 4 and did a little  
>> investigative work to determine the cause of the problem.
>
> If have tested CARP on ESX 3.5u4 successfully with a 32-bit FreeBSD  
> guest with e1000 vNICs.
>
> As well as turning on promiscuous mode on the vSwitch, you have to  
> enable "MAC Address changes" and "Forged transmits" as CARP requires  
> these to work properly.
>
> Unless this is a vSphere-specific problem I must suspect your  
> configuration as the problem.  Do you want to post your CARP config?
>
>
> - Andrew