From owner-freebsd-emulation@FreeBSD.ORG Wed Jan 20 15:04:01 2010 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 8BC13106566C for ; Wed, 20 Jan 2010 15:04:01 +0000 (UTC) (envelope-from ws@au.dyndns.ws) Received: from ipmail03.adl2.internode.on.net (ipmail03.adl2.internode.on.net [203.16.214.135]) by mx1.freebsd.org (Postfix) with ESMTP id 1FB188FC0A for ; Wed, 20 Jan 2010 15:04:00 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AukAAFOkVkuWZWdv/2dsb2JhbAAI2EWENgQ Received: from ppp103-111.static.internode.on.net (HELO [192.168.1.144]) ([150.101.103.111]) by ipmail03.adl2.internode.on.net with ESMTP; 21 Jan 2010 01:18:38 +1030 From: Wayne Sierke To: Juergen Lock In-Reply-To: <20100107185808.GA16577@triton8.kn-bremen.de> References: <20100107185808.GA16577@triton8.kn-bremen.de> Content-Type: text/plain; charset="ASCII" Date: Thu, 21 Jan 2010 01:18:33 +1030 Message-ID: <1263998913.1862.29543.camel@predator-ii.buffyverse> Mime-Version: 1.0 X-Mailer: Evolution 2.28.2 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Cc: freebsd-emulation@freebsd.org, vbox-dev@virtualbox.org Subject: Re: vbox (and qemu) tap/vboxnetflt networking; bridging vs wifi 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: Wed, 20 Jan 2010 15:04:01 -0000 On Thu, 2010-01-07 at 19:58 +0100, Juergen Lock wrote: ... > The only downside of doing it this way is the tap interface loses > its IP when vbox closes it and the ifup/down script feature has been > removed from vbox so you need to rerun the `ifconfig tap0 ...' each > time before you start the guest again. (Maybe that can be avoided > if you set net.link.tap.up_on_open=1, put only the tap interface on > an if_bridge and give that bridge interface the IP instead, I haven't > tried.) FYI, I just tried this and it appears to work. That is, with the following: ==> /boot/loader.conf <== if_tap_load="YES" vboxdrv_load="YES" ==> /etc/sysctl.conf <== net.link.tap.user_open=1 net.link.tap.up_on_open=1 net.link.ether.inet.proxyall=1 ==> /etc/rc.conf <== cloned_interfaces="bridge0 tap0 tap1" ifconfig_bridge0="addm tap0 addm tap1 192.168.1.121/29" gateway_enable="YES" and with the VM network adapters configured as bridged to the tapX devices, the guest em0 interfaces configured with IP addresses in the bridge0's subnet and with default routes to the bridge0 ip, networking seems to come up fine in the guests. (I'm still starting the VMs manually so it hasn't been verified in fully autonomous startup.) Wayne