From owner-freebsd-questions@FreeBSD.ORG Fri Nov 27 16:39:57 2009 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D3E431065672 for ; Fri, 27 Nov 2009 16:39:57 +0000 (UTC) (envelope-from amvandemore@gmail.com) Received: from mail-px0-f190.google.com (mail-px0-f190.google.com [209.85.216.190]) by mx1.freebsd.org (Postfix) with ESMTP id A79B18FC0A for ; Fri, 27 Nov 2009 16:39:55 +0000 (UTC) Received: by pxi28 with SMTP id 28so1134799pxi.7 for ; Fri, 27 Nov 2009 08:39:55 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=weG1YXR5W2L6RZJX4WInWdeT238T29etS/0vuImxc9Y=; b=PaJFrWkddWQItCQhDZw5H3Gq1p7v3cV8z/E1/RGU8ZZz+8mgoKMMhvzls+lR3CAekb P0XzwEkLN3s/7pi0cSkLKcVBXYp0/aCTVaUx3UsNjsDObtuSHNpiHz5ZUpEUPzz3/W1X hhij5JEq0hm07Oc1knniJPgZdSoSZrr8UV8b0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=MdFpYsHwQR2VxfhIkRUe29XuhZ/timKlx0LFXy89G39PGghGx5t3Y9/vztDa8wWTEQ hGBs4xe0Bcm8LdtW2drO7v0vkRFXF9j+PTD0xEEheYnQPQWaGriDCSeKitG7jfxLl1Cc UbTm3L9PLW47JNGJ6quooIA01vAeMlQmGuEQE= MIME-Version: 1.0 Received: by 10.143.137.2 with SMTP id p2mr125437wfn.318.1259339995363; Fri, 27 Nov 2009 08:39:55 -0800 (PST) In-Reply-To: <200911270836.15146.npapke@acm.org> References: <4B0F8CA7.1080009@zedat.fu-berlin.de> <200911270836.15146.npapke@acm.org> Date: Fri, 27 Nov 2009 10:39:55 -0600 Message-ID: <6201873e0911270839l5da34701j67eb6b02b9f75ccd@mail.gmail.com> From: Adam Vande More To: Norbert Papke Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-questions@freebsd.org Subject: Re: VirtualBox: No network connectivity. Weird vboxnetflt.ko/vboxnetadp.ko behaviour X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Nov 2009 16:39:57 -0000 On Fri, Nov 27, 2009 at 10:36 AM, Norbert Papke wrote: > On November 27, 2009, O. Hartmann wrote: > > Befor going deeper into my config I will report some strange behaviour > > of needed kernel modules > > > > vboxnetflt.ko > > vboxnetadp.ko > > > > Both are needed for networking on VirtualBox and they get loaded at > > startup vi /boot/loader.conf. But to have a working network, I have to > > unload and then reload them, since if they get loaded at startup, > > networking is broken in virtual box! > > The vboxnetadp.ko is needed for the "host-only adapter" mode, I tend not to > load it. For bridged mode, you need vboxnetflt.ko. > > I have been having good luck by always loading vboxnetadp.ko manually > rather > than from loader.conf. > > > My FreeBSD-based config is simple. I have a bridged NIC (msk0), a tap0 > > device which is member of the bridge. > > I do not use a tap device. It should not be needed. I bridge the physical > device directly. > > > Has anybody similar trouble? > > The modules are a somewhat temperamental. When I follow the above, it > works > great. When I deviate, I sometimes have trouble. > > Cheers, > > Yeah I assume the issue is vboxnetflt.ko needs eth device to be loaded to actually bind to. I do this with /etc/crontab to work around: @reboot root /sbin/kldload /boot/modules/vboxnetflt.ko -- Adam Vande More