Date: Mon, 20 Jul 2009 13:18:07 +0200 From: Max Laier <max@love2party.net> To: freebsd-net@freebsd.org Cc: Matthew Grooms <mgrooms@shrew.net>, Andrew Snow <andrew@modulus.org> Subject: Re: FreeBSD + carp on VMWare ESX Message-ID: <200907201318.08122.max@love2party.net> In-Reply-To: <3D3254E2-4E45-4C67-84D2-DB05660D768F@shrew.net> References: <4A638E76.2060706@shrew.net> <4A63A4B3.6090500@modulus.org> <3D3254E2-4E45-4C67-84D2-DB05660D768F@shrew.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Monday 20 July 2009 01:25:03 Matthew Grooms wrote: > 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. There is clearly something very wrong with how the vswitch works and it's not really FreeBSD's job to work around these issues. The patch you posted is rather intrusive and certainly not something we want in the tree. You should talk to VMWare's support to fix the obvious short-comings in the vswitch design. As for your patch - you want "IF_ADDR_[UN]LOCK(ifp);" around walking the address list. Don't forget to unlock before the return. > -Matthew > > On Jul 19, 2009, at 5:56 PM, Andrew Snow <andrew@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 > > _______________________________________________ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" > > > !DSPAM:4a63ab81519501271912576! -- /"\ Best regards, | mlaier@freebsd.org \ / Max Laier | ICQ #67774661 X http://pf4freebsd.love2party.net/ | mlaier@EFnet / \ ASCII Ribbon Campaign | Against HTML Mail and News
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200907201318.08122.max>