From owner-freebsd-ports Thu Aug 3 8:58:56 2000 Delivered-To: freebsd-ports@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id 0410837B581; Thu, 3 Aug 2000 08:58:45 -0700 (PDT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.9.3/8.9.3) with SMTP id LAA28204; Thu, 3 Aug 2000 11:58:17 -0400 (EDT) (envelope-from robert@fledge.watson.org) Date: Thu, 3 Aug 2000 11:58:17 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: rbezuide@oskar.nanoteq.co.za Cc: freebsd-hackers@FreeBSD.ORG, ports@FreeBSD.ORG Subject: RE: vmware changes result in nasty bridging mess In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, 3 Aug 2000, Reinier Bezuidenhout wrote: > I'm using vmware2 in a different way ... I do not have bridging enabled > in the kernel. I'm using the host method although I do not have > a "legal" subnet on the other side. That was the configuration I was using also, until I upgraded my version of -STABLE, and as a result had to upgrade my vmware port. The results thus far have been a little worrying, and I'd like to see them fixed before too many people get hurt. Robert N M Watson robert@fledge.watson.org http://www.watson.org/~robert/ PGP key fingerprint: AF B5 5F FF A6 4A 79 37 ED 5F 55 E9 58 04 6A B1 TIS Labs at Network Associates, Safeport Network Services To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message