From owner-freebsd-emulation@FreeBSD.ORG Sat Aug 22 12:55:02 2009 Return-Path: Delivered-To: freebsd-emulation@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7A6D2106568B; Sat, 22 Aug 2009 12:55:02 +0000 (UTC) (envelope-from vbox-devel-l@jelal.kn-bremen.de) Received: from smtp.kn-bremen.de (gelbbaer.kn-bremen.de [78.46.108.116]) by mx1.freebsd.org (Postfix) with ESMTP id 3581A8FC14; Sat, 22 Aug 2009 12:55:02 +0000 (UTC) Received: by smtp.kn-bremen.de (Postfix, from userid 10) id 49C331E00345; Sat, 22 Aug 2009 14:39:45 +0200 (CEST) Received: from triton8.kn-bremen.de (noident@localhost [127.0.0.1]) by triton8.kn-bremen.de (8.14.3/8.14.3) with ESMTP id n7MCaCHV009073; Sat, 22 Aug 2009 14:36:12 +0200 (CEST) (envelope-from nox@triton8.kn-bremen.de) Received: (from nox@localhost) by triton8.kn-bremen.de (8.14.3/8.14.3/Submit) id n7MCaCXt009072; Sat, 22 Aug 2009 14:36:12 +0200 (CEST) (envelope-from nox) From: Juergen Lock Date: Sat, 22 Aug 2009 14:36:12 +0200 To: "Sean C. Farley" Message-ID: <20090822123611.GA8594@triton8.kn-bremen.de> References: <20090819185448.GA8386@triton8.kn-bremen.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.20 (2009-06-14) Cc: vbox-dev@virtualbox.org, freebsd-emulation@FreeBSD.org, Juergen Lock Subject: Re: tuntap hacks for FreeBSD vbox hosts (bandaid till vbox-net driver...) X-BeenThere: freebsd-emulation@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Development of Emulators of other operating systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 22 Aug 2009 12:55:02 -0000 On Thu, Aug 20, 2009 at 03:19:36PM -0500, Sean C. Farley wrote: > On Wed, 19 Aug 2009, Juergen Lock wrote: > > > Hi! > > > > After inquiring on the #vbox-dev channel whether the tuntap code could > > be resurrected for hosts that don't have vbox net/bridge drivers yet > > (like FreeBSD :) I now got it working - except the config gui and > > ifup/down scripts, the code for at least the latter seems to have been > > ripped out for good indeed... So for now you have to use VBoxManage > > something like this, > > VBoxManage modifyvm --nic1 bridged --bridgeadapter1 tap0 > > and manually configure your tap interface and (optionally) add it to a > > bridge before the VM starts. If you already have setup your host > > system to use tuntap networking with qemu you probably can just > > chown/chmod /dev/tap0 (or whichever one you use) to 660 root:vboxusers > > and then run your /usr/local/etc/qemu-ifup script with the same tap > > interface as arg, otherwise do something like... > > kldload if_tap if_bridge > > sysctl net.link.tap.user_open=1 > > chown root:vboxusers /dev/tap0 > > chmod 660 /dev/tap0 > > ifconfig bridge0 create > > ifconfig bridge0 addm > > ifconfig tap0 netmask > > ifconfig bridge0 addm tap0 > > and then start the guest. (You'll have to rerun the `ifconfig tap0 > > ...' each time before you start the guest again.) > > Thank you! I had started looking at the code to try to figure out why I > could not force the use of a tap device via VBoxManage. This patch > works for me with FreeBSD 7-STABLE. > > BTW, you should not need the ifconfig tap0 line above since the VM is > getting or setting its own IP. Is there a reason to do it? > I was about to explain how I needed it for the guest to be able to talk to the host here, but - turns out this was just due to me using pf on this box and the rules were a little broken. So yes it is not really necessary... > If you want it to have it look even more authenticate, you can always > rename the tap device to vboxnet0 with ifconfig. :) > Haha! :) Btw, seems my patch has reached its ultimate goal much more quickly than I expected: Motivating someone to implement `proper' FreeBSD vbox net drivers: http://lists.freebsd.org/pipermail/freebsd-emulation/2009-August/006701.html Thank you Fredrik!! :) Juergen