FONNEMANN Mark, on sam. 06 mai 2017 00:33:40 +0000, wrote: > >The attached patch should be dumping the same kind of information. > > Nslookup does not produce any output in curses or in logfile (-D logfile.txt).
Uh. So qemu can't be the culprit since it doesn't receive anything :) > root@qemu:~# /initrd/bin/nslookup www.google.com > Server: 10.0.2.3 > Address 1: 10.0.2.3 > > nslookup: can't resolve 'www.google.com' So it's supposed to be using 10.0.2.3 I guess. Just to make sure, you could try /initrd/bin/nslookup www.google.com 10.0.2.3 > I know the patch was applied because when I ping 10.0.2.2 I get the following: > > root@qemu:~# ping 10.0.2.2 > PING 10.0.2.2 (10.0.2.2): 56 data bytes > 64 bytes from 10.0.2.2: icmp_seq=0 ttl=255 time=0.5 ms > [mfonnemann@localhost qemu]$ cat logfile > ip input a00020f -> a000202 1 > ip input a00020f -> a000202 1 Do you get output when pinging 10.0.2.3? (you won't get ping answers, but that's fine, qemu should still be able to see the requests coming in) Also, just to make sure: you don't have firewalling rules, do you? Samuel
