Nmap Development mailing list archives
possible issue with nmap
From: "Jérôme Guelfucci" <jerome.guelfucci () gmail com>
Date: Sun, 10 Jun 2007 16:33:51 +0200
Hello, This was reported on Launchpad : https://bugs.launchpad.net/ubuntu/+source/nmap/+bug/51975 by : https://bugs.launchpad.net/~tore-debian It happens with nmap 4.20 under Ubuntu Dapper, Edgy, Feisty and Gutsy. It copy/paste the bug report here : Dapper : [quote] root@cr1:~# nmap -sP -PI 87.238.33.0 Starting Nmap 4.03 ( http://www.insecure.org/nmap/ ) at 2006-07-05 16:33 CEST Host 87.238.33.0 seems to be a subnet broadcast address (returned 1 extra pings). Note: Host seems down. If it is really up, but blocking our ping probes, try -P0 Nmap finished: 1 IP address (0 hosts up) scanned in 2.549 seconds root@cr1:~# ip a a 1.1.1.1/32 dev vlan511 label vlan511vip root@cr1:~# nmap -sP -PI 87.238.33.0 Starting Nmap 4.03 ( http://www.insecure.org/nmap/ ) at 2006-07-05 16:34 CEST Failed to determine the netmask of vlan511vip!: No such device (19) root@cr1:~# For reference, 87.238.33.0 isn't related to VLAN 511 at all: root@cr1:~# ip r g 87.238.33.0 87.238.33.0 via 87.238.32.25 dev bond1 src 87.238.32.26 cache mtu 1500 advmss 1460 hoplimit 64 This is Dapper, on x86_64. [/quote] And Feisty : [quote] Yes. This is from a freshgutsy, i386: tore@pride :) sudo nmap -sP -PI 87.238.32.0 Starting Nmap 4.20 ( http://insecure.org ) at 2007-06-09 20:27 CEST Note: Host seems down. If it is really up, but blocking our ping probes, try -P0 Nmap finished: 1 IP address (0 hosts up) scanned in 0.164 seconds tore@pride :) sudo ip a a 172.16.0.0/32 dev eth0 label eth0foobar tore@pride :) sudo nmap -sP -PI 87.238.32.0 Starting Nmap 4.20 ( http://insecure.org ) at 2007-06-09 20:28 CEST Failed to determine the netmask of eth0foobar!: No such device (19) tore@pride :( ip a s dev eth0 2: eth0: <BROADCAST,MULTICAST,UP,10000> mtu 1500 qdisc pfifo_fast qlen 1000 link/ether 00:0c:6e:80:ab:09 brd ff:ff:ff:ff:ff:ff inet 213.145.167.26/28 brd 213.145.167.31 scope global eth0 inet 172.16.0.0/32 scope global eth0foobar inet6 fe80::20c:6eff:fe80:ab09/64 scope link valid_lft forever preferred_lft forever /[quote] I googled about this, and had a look in the mailing list but could not find anything about it. Thank you Jérôme _______________________________________________ Sent through the nmap-dev mailing list http://cgi.insecure.org/mailman/listinfo/nmap-dev Archived at http://SecLists.Org
Current thread:
- possible issue with nmap Jérôme Guelfucci (Jun 10)