From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1N6NTB-0004um-Aa
	for qemu-devel@nongnu.org; Fri, 06 Nov 2009 06:59:09 -0500
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1N6NT6-0004ol-0O
	for qemu-devel@nongnu.org; Fri, 06 Nov 2009 06:59:08 -0500
Received: from [199.232.76.173] (port=40359 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1N6NT5-0004oP-O3
	for qemu-devel@nongnu.org; Fri, 06 Nov 2009 06:59:03 -0500
Received: from moutng.kundenserver.de ([212.227.17.9]:51435)
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <arnd@arndb.de>) id 1N6NT5-0008Du-2L
	for qemu-devel@nongnu.org; Fri, 06 Nov 2009 06:59:03 -0500
From: Arnd Bergmann <arnd@arndb.de>
Subject: Re: [Qemu-devel] [PATCH 0/4] net-bridge: rootless bridge support for
	qemu
Date: Fri, 6 Nov 2009 12:58:51 +0100
References: <1257294485-27015-1-git-send-email-aliguori@us.ibm.com>
	<20091105082125.GB5774@redhat.com>
	<20091106020350.GH21630@shareable.org>
In-Reply-To: <20091106020350.GH21630@shareable.org>
MIME-Version: 1.0
Content-Type: Text/Plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Message-Id: <200911061258.51303.arnd@arndb.de>
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Jamie Lokier <jamie@shareable.org>
Cc: Mark McLoughlin <markmc@redhat.com>, Anthony Liguori <aliguori@us.ibm.com>, Arnd Bergmann <arndbergmann@googlemail.com>, Dustin Kirkland <kirkland@canonical.com>, Juan Quintela <quintela@redhat.com>, "Michael S. Tsirkin" <mst@redhat.com>, qemu-devel@nongnu.org

On Friday 06 November 2009, Jamie Lokier wrote:
> 
> Michael S. Tsirkin wrote:
> > On Thu, Nov 05, 2009 at 04:12:36AM +0000, Jamie Lokier wrote:
> > > I notice that if we eventually teach the kernel to have unnamed
> > > bridges (just attach interfaces to each other), only the helper
> > > commands will need changing to use it :-)
> > 
> > What do you mean by "attach interfaces to each other"?
> > Which interfaces do you want to attach to each other?
> 
> For example, attaching eth0 to tap0 without having to define br0,
> instead of the current method where you define br0 then attach eth0
> and tap0 to it, then transfer eth0's IP configuration to br0, then
> tell all the network management tools about it.

"Attaching" two network interfaces to each other does not work the
way you'd like it to. The tap device is on it's own unless you use
either a bridge or configure IP forwarding, which has another set
of problems.

I posted an experimental 'macvtap' driver a few some time ago that
would allow you to do something like that, i.e. add another logical
interface to an existing eth0 device, with a separate mac address,
and export that as a character device that is compatible with /dev/tun.

I probably need to start that one over from scratch, because I also
want to make it work with vhost-net, and to allow the guest and
the host to communicate with each other.
Note that this would be transparent to qemu, we'd only need a different
helper script to call.

	Arnd <><