From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.33) id 1BuDtL-0002Ap-Av for qemu-devel@nongnu.org; Mon, 09 Aug 2004 13:24:59 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.33) id 1BuDtI-00029a-4e for qemu-devel@nongnu.org; Mon, 09 Aug 2004 13:24:57 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1BuDtI-00029C-0T for qemu-devel@nongnu.org; Mon, 09 Aug 2004 13:24:56 -0400 Received: from [64.233.170.200] (helo=mproxy.gmail.com) by monty-python.gnu.org with esmtp (Exim 4.34) id 1BuDp1-0002Wz-Bl for qemu-devel@nongnu.org; Mon, 09 Aug 2004 13:20:31 -0400 Received: by mproxy.gmail.com with SMTP id 74so257759rnk for ; Mon, 09 Aug 2004 10:20:29 -0700 (PDT) Message-ID: <5640213304080910203d064272@mail.gmail.com> Date: Mon, 9 Aug 2004 12:20:29 -0500 From: Mike Tremoulet Subject: Re: [Qemu-devel] Networking on Win2K host In-Reply-To: <20040809153833.GC3737@cs.unibo.it> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <56402133040809075470e00759@mail.gmail.com> <20040809153833.GC3737@cs.unibo.it> Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org 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 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 >