From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1E3NTr-0001cE-Is
	for qemu-devel@nongnu.org; Thu, 11 Aug 2005 20:33:03 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1E3NQT-0000gU-HE
	for qemu-devel@nongnu.org; Thu, 11 Aug 2005 20:29:36 -0400
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1E3NQN-0000QB-PD
	for qemu-devel@nongnu.org; Thu, 11 Aug 2005 20:29:27 -0400
Received: from [212.16.62.50] (helo=mail.13thfloor.at)
	by monty-python.gnu.org with esmtp (Exim 4.34) id 1E3NN8-0006X8-F4
	for qemu-devel@nongnu.org; Thu, 11 Aug 2005 20:26:06 -0400
Date: Fri, 12 Aug 2005 02:11:06 +0200
From: Herbert Poetzl <herbert@13thfloor.at>
Subject: Re: [Qemu-devel] Connecting vde and LAN
Message-ID: <20050812001106.GA21001@MAIL.13thfloor.at>
References: <20050710173735.GA21204@jbrown.mylinuxbox.org>
	<Pine.LNX.4.61.0508111623330.7988@filer.marasystems.com>
	<42FB7BD3.60505@gmx.de> <200508111800.14002.paul@codesourcery.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200508111800.14002.paul@codesourcery.com>
Reply-To: qemu-devel@nongnu.org
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: Paul Brook <paul@codesourcery.com>
Cc: qemu-devel@nongnu.org

On Thu, Aug 11, 2005 at 06:00:12PM +0100, Paul Brook wrote:
> > I guess this means that VDE would have to provide a kernel-layer
> > component which grabs the packets from eth0 and provides the faked eth0
> > for the Host OS...
> 
> You can do all this with the standard linux tools. Something like the 
> following(untested) script. ifrename is part of the Linus Wireless Tools. If 
> your distro doesn't have it you can download it here:
> http://www.hpl.hp.com/personal/Jean_Tourrilhes/Linux/Tools.html

and nameif is a lot older, part of net-tools and
basically installed on every machine which has
ifconfig ... hmm, scratch the last part, it is
installed on every machine :)

HTH,
Herbert

> Paul
> 
> #! /bin/sh
> # Take eth0 down so it can be renamed
> ifdown eth0
> # Rename eth0, and create a new bridge interface called eth0
> # This avoids having to change host network configuration.
> ifrename -i eth0 -n realeth0
> brctl addbr eth0
> brctl addif eth0 realeth0
> # bring realeth0 up without an IP so the bridge can use it
> ifconfig realeth0 0.0.0.0 up
> # bring the new eth0 up
> ifup eth0
> # Start vde, and add it to the bridge.
> vde_switch -t tap0
> ifconfig tap0 0.0.0.0 up
> brctl addif eth0 tap0
> 
> 
> _______________________________________________
> Qemu-devel mailing list
> Qemu-devel@nongnu.org
> http://lists.nongnu.org/mailman/listinfo/qemu-devel