Date: Wed, 06 Dec 2006 07:26:56 +1100 From: Antony Mawer <fbsd-net@mawer.org> To: Gleb Smirnoff <glebius@FreeBSD.org> Cc: net@FreeBSD.org, Ari Suutari <ari.suutari@syncrontech.com> Subject: Re: kern/104377: [carp] [patch] CARP interface doesn't go up on VmWare Message-ID: <4575D610.702@mawer.org> In-Reply-To: <20061205104832.GD32700@cell.sick.ru> References: <200612041538.kB4FcQjk073583@freefall.freebsd.org> <0eaa01c71835$f12055f0$6602a8c0@sad.syncrontech.com> <20061205100407.GB32700@cell.sick.ru> <100a01c71858$64b1efc0$6602a8c0@sad.syncrontech.com> <20061205104832.GD32700@cell.sick.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
On 5/12/2006 9:48 PM, Gleb Smirnoff wrote:
> On Tue, Dec 05, 2006 at 12:30:27PM +0200, Ari Suutari wrote:
> A> >If interface, that went down, had reported its state then CARP
> A> >would had noticed that and would had lowered its priority,
> A> >gave up mastering, and became backup. This will be redundant.
> A>
> A> Is it impossible to add link state reporting to lnc driver ?
> A> I think this would be the perfect fix and acceptable by
> A> everyone.
>
> You are 100% right :)
If you are running VMware 5.x, then you can use the em driver (Intel
Pro/1000) instead, which is far more functional than the lnc driver. To
do so:
1. Shutdown the VMware system
2. Locate the *.vmx file for your virtual machine
3. Open the *.vmx file in your favourite text editor
4. Add the following line:
ethernet0.virtualDev = "e1000"
5. Save the file, and re-open the VM in VMware
6. Enjoy a more functional NIC under VMware!
Cheers
Antony
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4575D610.702>