[vbox-dev] tuntap hacks for FreeBSD vbox hosts (bandaid till vbox-net driver...)
vbox-devel-l at jelal.kn-bremen.de
Thu Aug 20 09:46:19 PDT 2009
In article <200908200121.49710.mlobo at digiart.art.br> you write:
>On Wednesday 19 August 2009 16:34:48 Juergen Lock wrote:
>> [Resent with proper From, sorry forgot this list is subscribed-only...]
>> ----- Forwarded message from Juergen Lock <nox at jelal.kn-bremen.de> -----
>> Date: Wed, 19 Aug 2009 20:54:48 +0200
>> From: Juergen Lock <nox at jelal.kn-bremen.de>
>> To: vbox-dev at virtualbox.org
>> Cc: freebsd-emulation at FreeBSD.org
>> Subject: tuntap hacks for FreeBSD vbox hosts (bandaid till vbox-net
>> User-Agent: Mutt/1.5.20 (2009-06-14)
>> 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 <VM name> --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 <host physical interface>
>> ifconfig tap0 <ip> netmask <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.)
>> Tested on the stable/8 FreeBSD branch with the vbox version currently
>> in ports. (which btw today seems to have hit the same FreeBSD vboxdrv
>> bug with svm and npt here while scp'ing a big file out of a guest that
>> I previously thought only plagued intel vt-x users, see this post for
>> Anyway, here comes the patch, enjoy! :)
>WoW !! Tested and it works beautifully !!!!
>You're the man, Juergen !!
Thanx, I'm glad it works for you.
>I have set up the proper patch-*.* files for the port's /files directory.
>Please let me know if you want them.
Oh I just put it in files/ as one single patch file here since it
adds one feature, also that way it'll be easier to remove once it
(or something equivalent) is committed upstream later.
>That was the only thing missing for me to use VBox the way I need it.
>Thanks many times over !
You're welcome! :)
More information about the vbox-dev