From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.33) id 1BuERH-0007Ae-AH for qemu-devel@nongnu.org; Mon, 09 Aug 2004 14:00:03 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.33) id 1BuERF-0007A6-8V for qemu-devel@nongnu.org; Mon, 09 Aug 2004 14:00:02 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1BuERF-0007A3-5f for qemu-devel@nongnu.org; Mon, 09 Aug 2004 14:00:01 -0400 Received: from [130.136.1.101] (helo=lea.cs.unibo.it) by monty-python.gnu.org with esmtp (Exim 4.34) id 1BuENQ-000372-8K for qemu-devel@nongnu.org; Mon, 09 Aug 2004 13:56:04 -0400 Date: Mon, 9 Aug 2004 19:56:03 +0200 Subject: Re: RESOLVED: Re: [Qemu-devel] Networking on Win2K host Message-ID: <20040809175603.GE3737@cs.unibo.it> References: <56402133040809075470e00759@mail.gmail.com> <20040809153833.GC3737@cs.unibo.it> <5640213304080910203d064272@mail.gmail.com> <5640213304080910481e37d8a7@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5640213304080910481e37d8a7@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 12:48:28PM -0500, Mike Tremoulet wrote: > 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 true. > 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) > Strange, the slirp support has been designed to forward DNS on the address 10.0.2.3 and the internal DHCP has been designed to broadcast this info. > 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. Mike, either you use tap or user-net, these are mutually esclusive approaches. If you use user-net you use slirp and you do not need any TAP configuration or you use tap and the address must be given by a dhcp server running on your host computer or just defined statically in a consistent way. ciao renzo