From owner-freebsd-bugs  Thu Feb  6 10:30:13 2003
Delivered-To: freebsd-bugs@hub.freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 570A037B405
	for <freebsd-bugs@hub.freebsd.org>; Thu,  6 Feb 2003 10:30:10 -0800 (PST)
Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 04E1543F75
	for <freebsd-bugs@hub.freebsd.org>; Thu,  6 Feb 2003 10:30:10 -0800 (PST)
	(envelope-from gnats@FreeBSD.org)
Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1])
	by freefall.freebsd.org (8.12.6/8.12.6) with ESMTP id h16IU9NS050921
	for <freebsd-bugs@freefall.freebsd.org>; Thu, 6 Feb 2003 10:30:09 -0800 (PST)
	(envelope-from gnats@freefall.freebsd.org)
Received: (from gnats@localhost)
	by freefall.freebsd.org (8.12.6/8.12.6/Submit) id h16IU980050920;
	Thu, 6 Feb 2003 10:30:09 -0800 (PST)
Date: Thu, 6 Feb 2003 10:30:09 -0800 (PST)
Message-Id: <200302061830.h16IU980050920@freefall.freebsd.org>
To: freebsd-bugs@FreeBSD.org
Cc: 
From: Charles Randall <cfriv@yahoo.com>
Subject: Re: kern/44126: lnc network hungup at large traffics on VMware
Reply-To: Charles Randall <cfriv@yahoo.com>
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-bugs.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-bugs>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-bugs>
X-Loop: FreeBSD.org

The following reply was made to PR kern/44126; it has been noted by GNATS.

From: Charles Randall <cfriv@yahoo.com>
To: freebsd-gnats-submit@FreeBSD.org
Cc: tam@math.kobe-u.ac.jp, karuhito@cam.hi-ho.ne.jp,
	paul@freebsd-services.com
Subject: Re: kern/44126: lnc network hungup at large traffics on VMware
Date: Thu, 6 Feb 2003 10:24:37 -0800 (PST)

 Having battled this problem many times, I finally
 opened a support incident with vmware.
 
 They've admitted that this is a bug and have assigned
 Bug #18190 to this problem.
 
 I originally repoted this with vmware 0.8 and FreeBSD
 3.2,
 
 http://groups.google.com/groups?selm=199908030045.RAA02341_dingo.cdrom.com%40ns.sol.net
 
 This workaround (which Paul says doesn't make sense)
 seems to work for FreeBSD 4.x (but fails miserably
 with 5.0),
 
 http://groups.google.com/groups?threadm=fa.kuu61sv.1imok1a%40ifi.uio.no
 
 FYI,
 -Charles
 
 
 =====
 Charles F. Randall, IV
 cfr@pobox.com (always forwarded)
 
 __________________________________________________
 Do you Yahoo!?
 Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
 http://mailplus.yahoo.com

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message