From owner-freebsd-net@FreeBSD.ORG Tue Dec 5 20:29:57 2006 Return-Path: X-Original-To: net@freebsd.org Delivered-To: freebsd-net@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id D038616A403; Tue, 5 Dec 2006 20:29:57 +0000 (UTC) (envelope-from fbsd-net@mawer.org) Received: from mail-ihug.icp-qv1-irony2.iinet.net.au (ihug-mail.icp-qv1-irony2.iinet.net.au [203.59.1.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5AB4143DB6; Tue, 5 Dec 2006 20:27:49 +0000 (GMT) (envelope-from fbsd-net@mawer.org) Received: from 203-206-173-235.perm.iinet.net.au (HELO [10.24.1.1]) ([203.206.173.235]) by mail-ihug.icp-qv1-irony2.iinet.net.au with ESMTP; 06 Dec 2006 04:28:25 +0800 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AgAAAOBkdUXLzq3r/2dsb2JhbAAN X-IronPort-AV: i="4.09,501,1157299200"; d="scan'208"; a="724819712:sNHT18747036" Message-ID: <4575D610.702@mawer.org> Date: Wed, 06 Dec 2006 07:26:56 +1100 From: Antony Mawer User-Agent: Thunderbird 1.5.0.8 (Windows/20061025) MIME-Version: 1.0 To: Gleb Smirnoff 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> In-Reply-To: <20061205104832.GD32700@cell.sick.ru> Content-Type: text/plain; charset=KOI8-R; format=flowed Content-Transfer-Encoding: 7bit Cc: net@FreeBSD.org, Ari Suutari Subject: Re: kern/104377: [carp] [patch] CARP interface doesn't go up on VmWare X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Dec 2006 20:29:57 -0000 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