From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1JwT3j-0004rR-3a for qemu-devel@nongnu.org; Wed, 14 May 2008 22:19:07 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1JwT3h-0004qR-3O for qemu-devel@nongnu.org; Wed, 14 May 2008 22:19:06 -0400 Received: from [199.232.76.173] (port=57221 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JwT3h-0004qO-0S for qemu-devel@nongnu.org; Wed, 14 May 2008 22:19:05 -0400 Received: from ti-out-0910.google.com ([209.85.142.191]:3581) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1JwT3g-0007pg-RM for qemu-devel@nongnu.org; Wed, 14 May 2008 22:19:05 -0400 Received: by ti-out-0910.google.com with SMTP id y6so155231tia.18 for ; Wed, 14 May 2008 19:19:02 -0700 (PDT) Message-ID: Date: Thu, 15 May 2008 09:19:02 +0700 From: "Mulyadi Santosa" Subject: Re: [Qemu-devel] DNS reply In-Reply-To: <43331.81.47.192.163.1210776537.squirrel@webmail.kix.es> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <43331.81.47.192.163.1210776537.squirrel@webmail.kix.es> 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 Hi.... On Wed, May 14, 2008 at 9:48 PM, Rodolfo kix Garc=EDa wrote: > Hi, > > I am using qemu in Windows with Linux as guest, and I have a problem with > the DNS. I am using the qemu's default network (without -net parameters > in qemu.exe) > > If I create a new network connection (or a ping in the Linux), the linux > command reads the /etc/resolv.conf file. It has the 10.0.2.3 address. > > Send a DNS packet (UDP, source port X, destination port 53) to 10.0.2.3. > 10.0.2.3 responds (UDP, source port Y, destinatio port X) to the Linux. > > But the Y port is different than 53, then Linux drops the packet and repl= y > to 10.0.2.15 with an ICMP port unreacheable (tcpdump). Hm, no Qemu users on Linux host reported such thing before. Since Qemu windows port might have some differences than main Qemu tree...I suggest to contact Qemu windows maintainer too. To be specific, I guess it's somewhere inside slirp code..... regards, Mulyadi.