>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).
I tried it using the version installed on the root system (Busybox 1.0):
root@qemu:~# nslookup
BusyBox v1.00 (2010.04.14-20:01+0000) multi-call binary
Usage: nslookup [HOST] [SERVER]
root@qemu:~# nslookup www.google.com
*** Unknown host
nslookup: www.google.com: Unknown host
as well as the newer version installed in initrd image which is version 1.25.1:
root@qemu:~# /initrd/bin/nslookup
BusyBox v1.25.1 (2017-05-01 19:00:24 EDT) multi-call binary.
Usage: nslookup [HOST] [SERVER]
Query the nameserver for the IP address of the given HOST
optionally using a specified DNS server
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'
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
64 bytes from 10.0.2.2: icmp_seq=1 ttl=255 time=0.1 ms
64 bytes from 10.0.2.2: icmp_seq=2 ttl=255 time=0.1 ms
64 bytes from 10.0.2.2: icmp_seq=3 ttl=255 time=0.1 ms
64 bytes from 10.0.2.2: icmp_seq=4 ttl=255 time=0.2 ms
--- 10.0.2.2 ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max = 0.1/0.2/0.5 ms
[mfonnemann@localhost qemu]$ cat logfile
ip input a00020f -> a000202 1
ip input a00020f -> a000202 1
ip input a00020f -> a000202 1
ip input a00020f -> a000202 1
ip input a00020f -> a000202 1
mark.
