[Qemu-devel] DNS reply

[Qemu-devel] DNS reply

[Rodolfo kix García]

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 reply
to 10.0.2.15 with an ICMP port unreacheable (tcpdump).

Using "nslookup" tool in linux, I get:

reply from unexpected source: 10.0.2.3#Y, expected 10.0.2.3#53 (three times).

I cannot find the problem in the sources. Any help?

Thanks.

-- 
Rodolfo García AKA kix
http://www.kix.es/
EA4ERH (@IN80ER)

Re: [Qemu-devel] DNS reply

[Mulyadi Santosa]

Hi....

On Wed, May 14, 2008 at 9:48 PM, Rodolfo kix García <kix@kix.es> 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 reply
> 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.