Range IP scan with option -sn show wrong result.

Willsz CS <[email protected]>
Newsgroups gmane.comp.security.nmap.devel
Message-ID <CAMby-euTCAPrDiZ91F6VbSQ_LP8XGcq1Dh5X-PSbXR3t_+r2bQ@mail.gmail.com>
Hi Folks,

I've some problem with scanning host with nmap using format:
192.168.100.70-71 or 192.168.100.70,71 or 192.168.100.70-71,100

root:~# uname -smr
FreeBSD 9.3-STABLE i386

root:~# nmap -v

Starting Nmap 7.40 ( https://nmap.org ) at 2017-07-05 12:18 WIB
Read data files from: /usr/local/share/nmap
WARNING: No targets were specified, so 0 hosts scanned.
Nmap done: 0 IP addresses (0 hosts up) scanned in 0.10 seconds
           Raw packets sent: 0 (0B) | Rcvd: 0 (0B)

Here's an example I've done:

root:~# nmap -sn 192.168.100.70-71

Starting Nmap 7.40 ( https://nmap.org ) at 2017-07-05 12:23 WIB
Nmap scan report for ip.wifi-ap1.willsz.net (192.168.100.70)
Host is up (0.00021s latency).
MAC Address: 60:E3:27:BC:CC:76 (Tp-link Technologies)
Nmap done: 2 IP addresses (1 host up) scanned in 0.33 seconds

Output nmap only resulting 1 host UP, but actualy host .70 and .71 already
UP:

root:~# nmap -sn 192.168.100.70

Starting Nmap 7.40 ( https://nmap.org ) at 2017-07-05 12:23 WIB
Nmap scan report for ip.wifi-ap1.willsz.net (192.168.100.70)
Host is up (0.00016s latency).
MAC Address: 60:E3:27:BC:CC:76 (Tp-link Technologies)
Nmap done: 1 IP address (1 host up) scanned in 0.22 seconds

root:~# nmap -sn 192.168.100.71

Starting Nmap 7.40 ( https://nmap.org ) at 2017-07-05 12:23 WIB
Nmap scan report for ip.wifi-ap2.willsz.net (192.168.100.71)
Host is up (0.00025s latency).
MAC Address: 10:FE:ED:94:81:A9 (Tp-link Technologies)
Nmap done: 1 IP address (1 host up) scanned in 0.22 seconds

This problem same with other format too:

root:~# nmap -sn 192.168.100.70-71,100

Starting Nmap 7.40 ( https://nmap.org ) at 2017-07-05 12:26 WIB
Nmap scan report for pcbill.willsz.net (192.168.100.100)
Host is up (0.000091s latency).
MAC Address: 00:30:67:56:75:BF (Biostar Microtech Int'l)
Nmap done: 3 IP addresses (1 host up) scanned in 0.33 seconds

Would you give clue to fix this bug?

Thank you.

_______________________________________________
Sent through the dev mailing list
https://nmap.org/mailman/listinfo/dev
Archived at http://seclists.org/nmap-dev/
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.