From owner-freebsd-emulation Thu Sep 7 9: 9:27 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from mother.ludd.luth.se (mother.ludd.luth.se [130.240.16.3]) by hub.freebsd.org (Postfix) with ESMTP id 3668037B422 for ; Thu, 7 Sep 2000 09:09:25 -0700 (PDT) Received: from speedy.ludd.luth.se (speedy.ludd.luth.se [130.240.16.164]) by mother.ludd.luth.se (8.9.3+Sun/8.9.3) with ESMTP id SAA07463; Thu, 7 Sep 2000 18:09:19 +0200 (MEST) Message-Id: <200009071609.SAA07463@mother.ludd.luth.se> X-Mailer: exmh version 2.1.1 10/15/1999 To: Michael Harnois Cc: "Vladimir Silyaev" , emulation@FreeBSD.ORG Subject: Re: vmware2 networking question In-Reply-To: Message from Michael Harnois of "07 Sep 2000 10:07:08 CDT." <86em2ws0kj.fsf@mharnois.workgroup.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 07 Sep 2000 18:09:19 +0200 From: Mattias Pantzare Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Yes, but you asked for a situation where vmware does not work with > bridging enabled and does work when it's not. This is such a > situation, and that *does* have to do with vmware. > > Furthermore, you can't possibly have an ip address assigned only at > one adapter. That negates the entire point of having two ethernet > cards, which is, in turn, the point of bridging. No, you do not have to have an ip adressed assigned to both adapters if you are doing bridging. You do not need to assign any ip address at all to do bridging. A normal ethernet switch is doing bridging. The problem is simply that the vmware port enables bridging among all your adapters, even if you do not use bridging normaly. That is very wrong. The vmware port shoud ask the user for the adapter that is to be used for vmware and enable bridging only between that adapter and the vmware-adapter. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message