Scan range IP not working in FreeBSD

Hi,

I got some problem with nmap with range IP Address.
root:~# uname -msr
FreeBSD 10.4-STABLE i386

root:~# nmap -V

Nmap version 7.40 ( https://nmap.org )
Platform: i386-portbld-freebsd10.3
Compiled with: liblua-5.3.3 openssl-1.0.1s-freebsd libpcre-8.40
libpcap-1.4.0 nmap-libdnet-1.12 ipv6
Compiled without:
Available nsock engines: kqueue poll select

root:~# nmap -sn 192.168.100.23,70-71,100-102

Starting Nmap 7.40 ( https://nmap.org ) at 2018-01-04 19:23 WIB
Nmap scan report for pcbill.willsz.net (192.168.100.100)
Host is up (0.00012s latency).
MAC Address: 00:30:67:56:75:BF (Biostar Microtech Int'l)
Nmap done: 6 IP addresses (1 host up) scanned in 0.33 seconds

I tested with the same time on Debian Linux and look like normally:
root@pchome:~# uname -a
Linux pchome 4.9.0-4-amd64 #1 SMP Debian 4.9.65-3+deb9u1 (2017-12-23) x86_64
GNU/Linux

root@pchome:~# nmap -V

Nmap version 7.40 ( https://nmap.org )
Platform: x86_64-pc-linux-gnu
Compiled with: liblua-5.3.3 openssl-1.1.0c libpcre-8.39 libpcap-1.8.1
nmap-libdnet-1.12 ipv6
Compiled without:
Available nsock engines: epoll poll select

root@pchome:~# nmap -sn 192.168.100.23,70-71,100-102

Starting Nmap 7.40 ( https://nmap.org ) at 2018-01-04 19:28 WIB
Nmap scan report for pccl23.willsz.net (192.168.100.23)
Host is up (0.00021s latency).
MAC Address: 00:30:67:51:9E:09 (Biostar Microtech Int'l)
Nmap scan report for 192.168.100.70
Host is up (0.00023s latency).
MAC Address: 60:E3:27:BC:CC:76 (Tp-link Technologies)
Nmap scan report for 192.168.100.71
Host is up (0.00027s latency).
MAC Address: 10:FE:ED:94:81:A9 (Tp-link Technologies)
Nmap scan report for pcbill.willsz.net (192.168.100.100)
Host is up (0.00012s latency).
MAC Address: 00:30:67:56:75:BF (Biostar Microtech Int'l)
Nmap scan report for pcnong.willsz.net (192.168.100.102)
Host is up (0.00029s latency).
MAC Address: B8:97:5A:41:34:28 (Biostar Microtech Int'l)
Nmap scan report for pchome.willsz.net (192.168.100.101)
Host is up.
Nmap done: 6 IP addresses (6 hosts up) scanned in 0.29 seconds


Anyone have a clue for this problem?

Thank You.

_______________________________________________
Sent through the dev mailing list
https://nmap.org/mailman/listinfo/dev
Archived at http://seclists.org/nmap-dev/