From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.33) id 1BuCIX-00039F-H2 for qemu-devel@nongnu.org; Mon, 09 Aug 2004 11:42:53 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.33) id 1BuCIV-000387-Kc for qemu-devel@nongnu.org; Mon, 09 Aug 2004 11:42:52 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1BuCIV-00037g-ES for qemu-devel@nongnu.org; Mon, 09 Aug 2004 11:42:51 -0400 Received: from [130.136.1.101] (helo=lea.cs.unibo.it) by monty-python.gnu.org with esmtp (Exim 4.34) id 1BuCEO-0007Oo-1v for qemu-devel@nongnu.org; Mon, 09 Aug 2004 11:38:37 -0400 Date: Mon, 9 Aug 2004 17:38:33 +0200 Subject: Re: [Qemu-devel] Networking on Win2K host Message-ID: <20040809153833.GC3737@cs.unibo.it> References: <56402133040809075470e00759@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <56402133040809075470e00759@mail.gmail.com> From: renzo@cs.unibo.it (Renzo Davoli) 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 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.