RESOLVED: Re: [Qemu-devel] Networking on Win2K host

[Mike Tremoulet <coffeemike@gmail.com>]

It's working now.

What I learned from this is that, as you said, slirp essentially set
up a NAT behind 10.0.2.2.  However, this was not resolving until I
changed the /etc/resolv.conf on the Gentoo guest to point at
192.168.0.1.  (It was originally set for 10.0.2.3)

I think that, unless slirp is doing something I don't know about, that
qemu is using the TAP-Win32 adapter on my host machine, which is set
through Windows internet connection sharing (ICS) to go through my
ethernet adapter.  I'm not seeing traffic on the TAP adapter, though,
but nothing else I know of has an IP of 192.168.0.1.

Setting the resolv.conf got me network name resolution, and a test of
wget showed connectivity to the outside world.

I will be writing this up - that was too much effort not to share. 
What is the best place for that writeup?  And are there any more
details or answers to the original questions about qemu's interaction
with a windows host?

Thanks,
-- Mike

On Mon, 9 Aug 2004 12:20:29 -0500, Mike Tremoulet <coffeemike@gmail.com> wrote:
> Renzo --
> 
> Thanks for the tip - I'm going to throw things if I spent the weekend
> sorting this out only because it doesn't forward pings... ;)
> 
> Unfortunately, resolution doesn't appear to be working now that I'm on
> my work network and not at home.  Again, I don't know how to tell
> which of three interfaces is used by slirp as the outbound side to the
> world.
> 
> Still working on it,
> -- Mike
> 
> 
> 
> On Mon, 9 Aug 2004 17:38:33 +0200, Renzo Davoli <renzo@cs.unibo.it> wrote:
> > On Mon, Aug 09, 2004 at 09:54:09AM -0500, Mike Tremoulet wrote:
> > > Qemu itself seems to run quite well and quite fast.  The only hurdle I
> > > have left is networking.  I have three interfaces on my Win2K host -
> > > an integrated Ethernet NIC, a wireless NIC, and OpenVPN 2.0beta2
> > > TAP-Win32 (installed in the process of trying everything).  When I
> > > boot in Qemu, I get an IP address of 10.*.*.* assigned.  This
> > > corresponds to nothing on my network.  I can resolve domain names, but
> > > I cannot apparently send or receive traffic. If I execute "ping
> > > google.com", the ping command comes back with an IP address for
> > > google.com but no packets received.
> > >
> > The IP address 10.0.2.15 is the default address for the slirp (user-net)
> > support integrated inside qemu.
> > slirp does not need any configuration nor external tools.
> > It does *not* forward ping (ICMP) packets but it works with TCP
> > connections as it were a NAT (masquerading) router.
> >
> > So if the guest os gets the address, it is able to resolve names, it is able
> > to ping 10.0.2.2 (the default route) everything should be okay.
> > If it resolves google.com but you cannot ping it... it is the standard
> > behavior.
> >
> > Cross your fingers and Start your browser.
> >
> > renzo
> >
> > P.s. I have my experience on qemu for linux, but for user-net netowrking
> > should behave in the same way.
> >
> > _______________________________________________
> > Qemu-devel mailing list
> > Qemu-devel@nongnu.org
> > http://lists.nongnu.org/mailman/listinfo/qemu-devel
> >
>