qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: bug reports and suggestions
Date: Sat, 06 May 2006 18:03:49 -0500	[thread overview]
Message-ID: <pan.2006.05.06.23.03.47.795880@codemonkey.ws> (raw)
In-Reply-To: 445BDBF2.9060605@gmx.de

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-----

  reply	other threads:[~2006-05-06 23:04 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-05 21:51 [Qemu-devel] bug reports and suggestions Don Kitchen
2006-05-05 23:12 ` Oliver Gerlich
2006-05-06 23:03   ` Anthony Liguori [this message]
2006-05-07  5:40     ` [Qemu-devel] " wangji
2006-05-08 15:58   ` [Qemu-devel] " Jim C. Brown
2006-05-08 17:05     ` Oliver Gerlich
2006-05-08 17:28       ` Jim C. Brown
2006-05-06 22:55 ` [Qemu-devel] " Anthony Liguori
2006-05-08 16:17 ` [Qemu-devel] " Jim C. Brown

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=pan.2006.05.06.23.03.47.795880@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).