newer versions of libpcap bug

[ValdikSS <iam () valdikss org ru>]

Hello.
It seems like there is incompatibility between newer versions of libpcap
and nmap.
I'm running ArchLinux, nmap is built with libpcap 1.5.3, and some
scripts, like ip-forwarding, just doesn't work as expected.
Everything works fine with internal libpcap.
Who should I report this bug? Is this nmap bug, or libpcap?

% nmap --version

Nmap version 6.46 ( http://nmap.org )
Platform: x86_64-unknown-linux-gnu
Compiled with: liblua-5.2.3 openssl-1.0.1g libpcre-8.35 *libpcap-1.5.3*
nmap-libdnet-1.12 ipv6
Compiled without:
Available nsock engines: epoll poll select

% sudo nmap -sn 192.168.5.1 --script ip-forwarding
--script-args='target=8.8.8.8'

Starting Nmap 6.46 ( http://nmap.org ) at 2014-06-23 16:14 MSK
Nmap scan report for router-wdr4300.lan (192.168.5.1)
Host is up (0.0033s latency).
MAC Address: 90:F6:xx:xx:xx:xx (Tp-link Technologies CO.)

Nmap done: 1 IP address (1 host up) scanned in 5.71 seconds


and with internal one:
% nmap --version

Nmap version 6.46 ( http://nmap.org )
Platform: x86_64-unknown-linux-gnu
Compiled with: liblua-5.2.3 openssl-1.0.1h libpcre-8.35
*nmap-libpcap-1.2.1* nmap-libdnet-1.12 ipv6
Compiled without:
Available nsock engines: epoll poll select

% sudo nmap -sn 192.168.5.1 --script ip-forwarding
--script-args='target=8.8.8.8'

Starting Nmap 6.46 ( http://nmap.org ) at 2014-06-23 16:07 MSK
Nmap scan report for router.lan (192.168.5.1)
Host is up (0.0033s latency).
MAC Address: 90:F6:xx:xx:xx:xx (Tp-link Technologies CO.)

Host script results:
| ip-forwarding:
|_  The host has ip forwarding enabled, tried ping against (8.8.8.8)

Nmap done: 1 IP address (1 host up) scanned in 0.39 seconds
_______________________________________________
Sent through the dev mailing list
http://nmap.org/mailman/listinfo/dev
Archived at http://seclists.org/nmap-dev/