From: Mike Tremoulet <coffeemike@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Networking on Win2K host
Date: Mon, 9 Aug 2004 12:20:29 -0500 [thread overview]
Message-ID: <5640213304080910203d064272@mail.gmail.com> (raw)
In-Reply-To: <20040809153833.GC3737@cs.unibo.it>
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
>
next prev parent reply other threads:[~2004-08-09 17:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-09 14:54 [Qemu-devel] Networking on Win2K host Mike Tremoulet
2004-08-09 15:38 ` Renzo Davoli
2004-08-09 17:20 ` Mike Tremoulet [this message]
2004-08-09 17:48 ` Renzo Davoli
2004-08-09 17:48 ` RESOLVED: " Mike Tremoulet
2004-08-09 17:56 ` Renzo Davoli
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=5640213304080910203d064272@mail.gmail.com \
--to=coffeemike@gmail.com \
--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).