From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.30)
	id 1BKZjP-0008De-Fp
	for qemu-devel@nongnu.org; Mon, 03 May 2004 05:27:23 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.30)
	id 1BKZip-0007z7-Kn
	for qemu-devel@nongnu.org; Mon, 03 May 2004 05:27:18 -0400
Received: from [62.151.20.186] (helo=mx.larebelion.net)
	by monty-python.gnu.org with esmtp (Exim 4.30) id 1BKZio-0007yN-V5
	for qemu-devel@nongnu.org; Mon, 03 May 2004 05:26:47 -0400
Received: from amavis by mx.larebelion.net with scanned-ok id 1BKZim-0001xE-00
	for qemu-devel@nongnu.org; Mon, 03 May 2004 11:26:44 +0200
Received: from [81.168.12.40] (helo=node4-ha.podcluster)
	by mx.larebelion.net with asmtp id 1BKZim-0001x6-00
	for qemu-devel@nongnu.org; Mon, 03 May 2004 11:26:44 +0200
Subject: Re: [Qemu-devel] Question about tun/tap networking
From: Carlos Valiente <lists@virutass.net>
In-Reply-To: <1083548132.4095a1e4ba072@www.postoffice.tpg.com.au>
References: <1083546791.16974.25.camel@localhost>
	<1083548132.4095a1e4ba072@www.postoffice.tpg.com.au>
Content-Type: text/plain
Message-Id: <1083576457.713.8.camel@rilke>
Mime-Version: 1.0
Date: Mon, 03 May 2004 10:27:38 +0100
Content-Transfer-Encoding: 7bit
Reply-To: qemu-devel@nongnu.org
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://mail.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://mail.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://mail.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: qemu-devel@nongnu.org

On Mon, 2004-05-03 at 02:35, nhand42@tpg.com.au wrote:
> You could also muck about with proxyarp or bridging but honestly, I wouldn't bother 
> with that. Routing is a lot easier to understand.

Bridging is not that difficult, either:

0. Get the userland bridge utils from http://bridge.sourceforge.net/ and
make sure your host Linux kernel is configured with CONFIG_BRIDGE

1. Create a bridge device (called 'br0', for instance):

# brctl addbr br0

2. Activate both TUN interfaces (but don't assign them IP addresses:
you'll do that for the bridge device instead)

# ifconfig tun0 0.0.0.0
# ifconfig tun1 0.0.0.0

3. Add both TUN interfaces to the bridge:

# brctl addif br0 tun0
# brctl addif br0 tun1

4. Set the bridge device IP address:

# ifconfig br0 172.16.1.1

C