From owner-freebsd-emulation Wed May 17 12:17:31 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from guardian.sftw.com (guardian.sftw.com [209.157.37.25]) by hub.freebsd.org (Postfix) with ESMTP id 923AF37B76D for ; Wed, 17 May 2000 12:17:28 -0700 (PDT) (envelope-from nsayer@sftw.com) Received: from yoda.sftw.com (yoda.sftw.com [209.157.37.211]) by guardian.sftw.com (8.9.3/8.9.3) with ESMTP id MAA70822 for ; Wed, 17 May 2000 12:17:28 -0700 (PDT) (envelope-from nsayer@sftw.com) Received: from sftw.com (localhost [127.0.0.1]) by yoda.sftw.com (8.9.3/8.9.3) with ESMTP id MAA13235 for ; Wed, 17 May 2000 12:17:27 -0700 (PDT) (envelope-from nsayer@sftw.com) Message-ID: <3922F047.105AF407@sftw.com> Date: Wed, 17 May 2000 12:17:27 -0700 From: Nick Sayer Reply-To: nsayer@freebsd.org X-Mailer: Mozilla 4.72 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-emulation@freebsd.org Subject: vmware networking: replace vmnet interface with /dev/tap? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org http://vtun.sourceforge.net/tun/index.html The TAP interface appears to be the solution to getting vmware bridged networking to work. Like the tun driver, tap presents a /dev/tapn device to user space. It works at the Ethernet level -- that is, you present Ethernet frames to /dev/tapn and they are given to the Ethernet input stuff. In addition, the tap driver supports bridging, which means that at long last vmware guests would have the same access to the network as their hosts. Of course, it probably wouldn't be hard to modify the vmnet module to support bridging instead. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message