From owner-freebsd-emulation@FreeBSD.ORG  Mon Oct 19 05:10:12 2009
Return-Path: <owner-freebsd-emulation@FreeBSD.ORG>
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 1D92C106566C
	for <freebsd-emulation@freebsd.org>;
	Mon, 19 Oct 2009 05:10:12 +0000 (UTC)
	(envelope-from fli@shapeshifter.se)
Received: from mx1.h3q.net (mx1.h3q.net [IPv6:2001:16d8:ffe5:1::f1])
	by mx1.freebsd.org (Postfix) with ESMTP id D68568FC15
	for <freebsd-emulation@freebsd.org>;
	Mon, 19 Oct 2009 05:10:11 +0000 (UTC)
Received: by mx1.h3q.net (Postfix, from userid 80)
	id 9FE9133D97; Mon, 19 Oct 2009 07:10:10 +0200 (CEST)
To: Juergen Lock <nox@jelal.kn-bremen.de>
MIME-Version: 1.0
Date: Mon, 19 Oct 2009 07:10:10 +0200
From: Fredrik Lindberg <fli@shapeshifter.se>
In-Reply-To: <200910182103.n9IL36HK054641@triton8.kn-bremen.de>
References: <200910151950.26620.naylor.b.david@gmail.com>
	<200910182103.n9IL36HK054641@triton8.kn-bremen.de>
Message-ID: <9ffa951df1394cfafab170773a1c9b8d@localhost>
X-Sender: fli@shapeshifter.se
User-Agent: RoundCube Webmail/0.3-stable
Content-Transfer-Encoding: 8bit
Content-Type: text/plain; charset=UTF-8
Cc: freebsd-emulation@freebsd.org, David Naylor <naylor.b.david@gmail.com>
Subject: Re: VirtualBox: vboxnetflt related problems
X-BeenThere: freebsd-emulation@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Development of Emulators of other operating systems
	<freebsd-emulation.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-emulation>, 
	<mailto:freebsd-emulation-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-emulation>
List-Post: <mailto:freebsd-emulation@freebsd.org>
List-Help: <mailto:freebsd-emulation-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-emulation>, 
	<mailto:freebsd-emulation-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 19 Oct 2009 05:10:12 -0000


On Sun, 18 Oct 2009 23:03:06 +0200 (CEST), Juergen Lock
<nox@jelal.kn-bremen.de> wrote:
> In article <4ADB515A.4050309@shapeshifter.se> you write:
>>David Naylor wrote:
>>> 
>>> 3) bridging doesn't work when connecting to bridge0 or tap0:
>>> # netstat -w1 -I tap0
>>>             input         (tap0)           output
>>>    packets  errs      bytes    packets  errs      bytes colls
>>>          0     0          0          0     0          0     0
>>>          0     0          0          0     2        151     0
>>> ...
>>> This happen with and without giving tap0 an IP address.  
>>
>>This is because vboxnetflt uses ng_ether and the interaction between
>>ng_ether/bridge/tap/vboxnetflt doesn't work.
> 
> Hmm, would it make sense to add back the tuntap code as a special
> case for when someone selects a tap interface for `bridged'
> networking?
> 
>  I haven't looked if thats even doable easily enough with all the
> conditional compilation going on tho. (VBOX_WITH_NETFLT...)
> 

Yes, the tuntap stuff and the vboxnetflt stuff seemed to both be
controlled by VBOX_WITH_NETFLT which makes life difficult :)

I think the bridge case might be fixable, there are explicit calls to the
bridge code inside ng_ether, but somewhere, something goes wrong.

Briefly looking at if_tap.c, I see that it calls ether_attach so
ng_ether *should* pick up frames from it - I need to look at this
further.

Fredrik