From: jbrown106@phreaker.net (Jim C. Brown)
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Question about tun/tap networking
Date: Mon, 3 May 2004 16:22:33 -0400 [thread overview]
Message-ID: <20040503202233.GB8530@jbrown.mylinuxbox.org> (raw)
In-Reply-To: <1083584704.1931.3.camel@localhost>
On Mon, May 03, 2004 at 01:45:04PM +0200, Arne Bernin wrote:
> On Mon, 2004-05-03 at 05:09, Jim C. Brown wrote:
>
> Hi Jim,
>
> > I recommend using vde by Renzo Davoli instead of the default tuntap.
> > I am able to network 2 instances of windows 98 (in separate qemu's) and
> > minix 2.0.4 (in a hand-modified bochs). It worked without a hitch, and all
> > the machines are on the same subnet.
> >
> > You still need forwarding to let the virtual machines see the lan or the
> > internet, however. The plus with vde is that you don't need to set up routing
> > for all these different tunN devices. (I use the Shorewall firewall, and using
> > tun was a pain...vde means I just have to set up routing and masquerading
> > for tap0, instead of for tun0, tun1, tun2, ...)
> >
> may you tell me how you set up your vde network ? I downloaded vde,
> installed it, bootet 2 qemus (on the same subnet) and tried to ping each
> other... I does not work, but i can ping the host they run on using a
> tap0 device, and see the who-has... arp stuff while running tcpdump on
> tap0. So it would be very interesting how you configured your vde_switch
> qemu setup for multiple machines on the same vde_switch.
>
> thanks,
> arne
>
>
[/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
This works, not only can I ping 2 different machines on the vde, I can also
ping the LAN from the vde, and vice versa. (ifconfig seems to set up
routing automagicly. Or was it something I put into shorewall...)
Note that for teh guest OS, you need to set up 192.168.1.254 as the default gateway
for just about everything.
>
>
>
>
> _______________________________________________
> Qemu-devel mailing list
> Qemu-devel@nongnu.org
> http://mail.nongnu.org/mailman/listinfo/qemu-devel
--
Infinite complexity begets infinite beauty.
Infinite precision begets infinite perfection.
next prev parent reply other threads:[~2004-05-03 20:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-03 3:09 [Qemu-devel] Question about tun/tap networking 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 [this message]
2004-05-03 21:31 ` Arne Bernin
[not found] <200406230754.07821.pjr@ucar.edu>
2004-06-23 17:03 ` Jim C. Brown
2004-06-23 17:15 ` Phil Rasch
2004-06-23 17:16 ` Gianni Tedesco
2004-06-23 19:32 ` Jim C. Brown
-- 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=20040503202233.GB8530@jbrown.mylinuxbox.org \
--to=jbrown106@phreaker.net \
--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).