From owner-freebsd-stable@FreeBSD.ORG Fri Oct 13 11:45:38 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C82AE16A47B for ; Fri, 13 Oct 2006 11:45:38 +0000 (UTC) (envelope-from ari@suutari.iki.fi) Received: from espresso2.syncrontech.com (sync-old.syncrontech.com [213.28.98.35]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3E2B943E14 for ; Fri, 13 Oct 2006 11:44:11 +0000 (GMT) (envelope-from ari@suutari.iki.fi) Received: from guinness.syncrontech.com (guinness.syncrontech.com [62.71.8.57]) by espresso2.syncrontech.com (8.13.1/8.13.1) with ESMTP id k9DBi4Kk049653 for ; Fri, 13 Oct 2006 14:44:04 +0300 (EEST) (envelope-from ari@suutari.iki.fi) Received: from [127.0.0.1] (coffee.syncrontech.com [192.168.5.102]) by guinness.syncrontech.com (8.13.4/8.13.4) with ESMTP id k9DBi27h012963 for ; Fri, 13 Oct 2006 14:44:04 +0300 (EEST) (envelope-from ari@suutari.iki.fi) Message-ID: <452F7BF2.5080206@suutari.iki.fi> Date: Fri, 13 Oct 2006 14:43:46 +0300 From: Ari Suutari User-Agent: Thunderbird 1.5.0.7 (Windows/20060909) MIME-Version: 1.0 To: freebsd-stable@freebsd.org References: <452E2151.80500@suutari.iki.fi> <452E27B4.2030709@tomjudge.com> <452E2AA0.4080702@suutari.iki.fi> In-Reply-To: <452E2AA0.4080702@suutari.iki.fi> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: carp0 interface goes down on 6.2-PRERELEASE X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Oct 2006 11:45:38 -0000 Hi, Ari Suutari wrote: > I have now tested with real hardware (ethernet is fxp0) and > under VmWare (ethernet is lnc0). Same problem on both. I'll have to correct this. Carp works with fxp0. Problem is only under vmware, which makes me more and more suspect that it is because lnc0 does not support link state reporting (it seems to be present on only a few drivers). Ari S.