From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1FcVoo-00070a-Ni for qemu-devel@nongnu.org; Sat, 06 May 2006 19:04:10 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1FcVon-0006xp-4s for qemu-devel@nongnu.org; Sat, 06 May 2006 19:04:10 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1FcVom-0006xg-UJ for qemu-devel@nongnu.org; Sat, 06 May 2006 19:04:09 -0400 Received: from [80.91.229.2] (helo=ciao.gmane.org) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA:32) (Exim 4.52) id 1FcVpG-0003W0-Hr for qemu-devel@nongnu.org; Sat, 06 May 2006 19:04:38 -0400 Received: from list by ciao.gmane.org with local (Exim 4.43) id 1FcVof-0005h0-Nz for qemu-devel@nongnu.org; Sun, 07 May 2006 01:04:01 +0200 Received: from cpe-70-116-9-243.austin.res.rr.com ([70.116.9.243]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 07 May 2006 01:04:01 +0200 Received: from anthony by cpe-70-116-9-243.austin.res.rr.com with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 07 May 2006 01:04:01 +0200 From: Anthony Liguori Date: Sat, 06 May 2006 18:03:49 -0500 Message-ID: References: <20060505215128.4171C1DC197@ravel.n2.net> <445BDBF2.9060605@gmx.de> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: news Subject: [Qemu-devel] Re: bug reports and suggestions Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org On Sat, 06 May 2006 01:12:50 +0200, Oliver Gerlich wrote: > Another interesting thing concerning networking: I use a little script to > set up a bridge between eth0 and tap0; but I have give the new bridge > interface (eg. br0) an IP address and such stuff, because eth0 doesn't > work. This is with Linux 2.6, but I read that with Linux 2.4 it was not > necessary to configure br0, as eth0 would still be accessible. Does anyone > know why this changed? I think it would be much easier if an interface > used in a bridge was still usable. My networking script creates a bridge (initially with no physical device attached). My qemu-ifup always attaches the tap device to a bridge specified by an environmental variable. I can then manage these bridges outside of qemu. So far, I've added support for three "operations" on these bridges. The bridge is initially consider a private virtual lan. You can then either NAT the virtual lan or bridge the lan to a physical interface. When NAT'ing or using a private lan, it also launches a DHCPD instance to provide local DHCP services. So far, this is the best I've been able to come up with in terms of a usuable method of managing virtual networking. I've included a pointer to the script (although please note, it probably won't work on any system other than my own) for reference. I really think that to do this properly would require another full project (especially since there's so much overlap between Xen/qemu in this area). http://qemu.codemonkey.ws/vlan-config Regards, Anthony Liguori > Thanks, > Oliver > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.2.2 (GNU/Linux) > > iD8DBQFEW9vwTFOM6DcNJ6cRApc8AJ9qYCEBHJqu/TsWilH5ztnx+PF8wACffVTp > 2AbeG8IcGxMz3lO1BUeZ3gY= > =a4mn > -----END PGP SIGNATURE-----