From: "Jim C. Brown" <jbrown106@phreaker.net>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Question about tun/tap networking
Date: Sun, 2 May 2004 23:09:41 -0400 [thread overview]
Message-ID: <20040503030941.GA2865@jbrown.mylinuxbox.org> (raw)
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, ...)
Available here btw: http://sourceforge.net/projects/vde/
On Mon, May 03, 2004 at 11:35:32AM +1000, nhand42@tpg.com.au wrote:
> Quoting Arne Bernin <arne@alamut.de>:
>
> > Hi,
> >
> > i am trying to set up two virtual machines with qemu 0.5.4. I have them
> > running, both with 2 network cards. I am able to ping all 4 interfaces
> > from the host they are running from but am not able to ping between both
> > virtual machines...
> > If i do a tcpdump on the corrsponding tun interfaces while trying to
> > ping i see a lot of arp who-has 172.16.0.254 tell 172.16.0.1 messages
> > (172.16.0.1 is the one machine, the other is 172.16.0.254).
> > Is there something i have to do to get the arp responses right ??
> > Or am i totally wrong ?
> >
>
> You've stuck both virtual machines on the same subnet, so they think they're on the
> same physical LAN. That's why they're doing ARPs and expecting replies. But you're
> actually running two QEMU instances on two seperate TUN interfaces and they *aren't*
> bridged. So the ARP on tun0 never gets seen on tun1 (and vice-versa).
>
> Set the second TUN interface to a different subnet (eg, 172.16.1.x) and enable ipv4
> forwarding. Linux will then forward packets between tun0 and tun1.
>
> You could also muck about with proxyarp or bridging but honestly, I wouldn't bother
> with that. Routing is a lot easier to understand.
>
>
> _______________________________________________
> 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 reply other threads:[~2004-05-03 3:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-03 3:09 Jim C. Brown [this message]
2004-05-03 11:45 ` [Qemu-devel] Question about tun/tap networking 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
[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=20040503030941.GA2865@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).