qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Jim C. Brown" <jbrown106@phreaker.net>
To: Phil Rasch <pjr@ucar.edu>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Question about tun/tap networking
Date: Wed, 23 Jun 2004 13:03:25 -0400	[thread overview]
Message-ID: <20040623170325.GB22835@jbrown.mylinuxbox.org> (raw)
In-Reply-To: <200406230754.07821.pjr@ucar.edu>

On Wed, Jun 23, 2004 at 07:54:07AM -0600, Phil Rasch wrote:
> I have been running a mixture of linux and windows machines, all real machines 
> on a LAN connected to the outside world through a router, which is acting as 
> my DHCP server, DNS server, and gateway machine. 
> 
> The LAN subnet is 192.168.0.*
> 
> Now I want to connect up the virtual machine running under QEMU. I want the 
> virtual machine to be on the same subnet as the real machines, and to use 
> DHCP from the router to get all the relevant info.

That is tricky. You will need to look into bridging.

> 
> Jim suggested the following commands for somebody else on the mailing list, 
> but I think that was headed towards devising a subnet that two virtual 
> machines could use to talk to each other.
> 
> [/space/qemu/qemu-0.5.4/ $] su root
> [/space/qemu/qemu-0.5.4/ #] vde_switch -daemon -tap tap0
> [/space/qemu/qemu-0.5.4/ #] ifconfig tap0 192.168.1.254
> [/space/qemu/qemu-0.5.4/ #] chmod 777 /tmp/vde.ctl
> [/space/qemu/qemu-0.5.4/ #] exit
> [/space/qemu/qemu-0.5.4/ $] vdeq qemu -hda disk1.img

That is correct. You now have 2 subnets, 198.168.0.* for the real network
and 192.168.1.* for qemu/VDE.

> 
> The thing I dont understand is whether the above command is setting up 
> seperate subnet for the virtual machines, or whether I can also set them up 
> on the same subnet as the real machines, and let them see the DHCP server,
> etc, and if so, then how to do it.  So far, I have never needed to learn the
> subtleties of ifconfig. Am I going to have to do so now? Do you have anymore 
> advice on using VDE and QEMU together for my purpose?

Like I said, you will need to use bridging. After you have loaded vde_switch,
skip the ifconfig step, and combine eth0 and tap0 into br0. Then you will need
to set up br0 properly. If you are going to use bridging however, I recommend
you use tuntap instead of VDE. (You don't really need VDE if you are going to
to use bridging.) If you decide to go with tuntap and bridging, you should look
in the qemu archives for assistance. There are several messages that appear
to have useful information on this topic, such as this one which tells you
step-by-step:

http://lists.gnu.org/archive/html/qemu-devel/2004-05/msg00032.html

(you'll need to do a 'brctl addif br0 eth0' and a 'ifconfig br0 192.168.0.XXX'
for the machine that will be running qemu (almost certainly in one of the startup
scripts, as eth0 must not have an ip yet) but otherwise the instructions are
exactly the same.)

I am curious though, why do you require that the virtual machines be on the same
subnet as the real ones?

> 
> Thanks
> 
> Phil

-- 
Infinite complexity begets infinite beauty.
Infinite precision begets infinite perfection.

       reply	other threads:[~2004-06-23 17:07 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200406230754.07821.pjr@ucar.edu>
2004-06-23 17:03 ` Jim C. Brown [this message]
2004-06-23 17:15   ` [Qemu-devel] Question about tun/tap networking Phil Rasch
2004-06-23 17:16   ` Gianni Tedesco
2004-06-23 19:32     ` Jim C. Brown
2004-05-03  3:09 Jim C. Brown
2004-05-03 11:45 ` Arne Bernin
2004-05-03 12:59   ` Renzo Davoli
2004-05-03 13:12     ` Renzo Davoli
2004-05-03 14:05     ` Renzo Davoli
2004-05-03 20:22   ` Jim C. Brown
2004-05-03 21:31     ` Arne Bernin
  -- strict thread matches above, loose matches on Subject: below --
2004-05-03  1:13 Arne Bernin
2004-05-03  1:35 ` nhand42
2004-05-03  9:27   ` Carlos Valiente

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=20040623170325.GB22835@jbrown.mylinuxbox.org \
    --to=jbrown106@phreaker.net \
    --cc=jbrown106@swift-mail.com \
    --cc=pjr@ucar.edu \
    --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).