Fails completely if there's labeled addresses present

Bug #51975 reported by Tore Anderson
6
Affects Status Importance Assigned to Milestone
nmap (Ubuntu)
Expired
Medium
Unassigned

Bug Description

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.

Tore.

Revision history for this message
Jérôme Guelfucci (jerome-guelfucci-deactivatedaccount) wrote :

Thank you for your bug report. Do you still have this issue with the latest release of Ubuntu ?

Changed in nmap:
importance: Undecided → Medium
status: Unconfirmed → Needs Info
Revision history for this message
Tore Anderson (tore-linpro) wrote : Re: [Bug 51975] Re: Fails completely if there's labeled addresses present

* Jérôme Guelfucci

> Thank you for your bug report. Do you still have this issue with the
> latest release of Ubuntu ?

  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

--
Tore Anderson

Revision history for this message
Tore Anderson (toreanderson) wrote :

* Jérôme Guelfucci

> Thank you for your bug report. Do you still have this issue with the
> latest release of Ubuntu ?

  Yes. This is from a fresh gutsy, 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

--
Tore Anderson

Revision history for this message
Jérôme Guelfucci (jerome-guelfucci-deactivatedaccount) wrote :

Ok thank you, I reported this upstream.

Changed in nmap:
status: Needs Info → Confirmed
Changed in nmap:
status: Confirmed → Triaged
Revision history for this message
Marco Rodrigues (gothicx) wrote :

It should be fixed at version 4.52 in Hardy...

Revision history for this message
Marco Rodrigues (gothicx) wrote :

It should be fixed at version 4.53 in Hardy...

Revision history for this message
LaMont Jones (lamont) wrote :

This is still an issue in 4.60 with hardy. :-( Off to chat with upstream.

Revision history for this message
kjak (katterjohn) wrote :

I've looked into this issue: http://seclists.org/nmap-dev/2008/q2/0178.html

If I'm wrong about anything, email nmap-dev or me personally at [my last name]@gmail.com

Revision history for this message
LaMont Jones (lamont) wrote :

I'll leave the bug open here for the time being. This is either a bug in the documenation, or the implementation of iproute.

See https://bugs.launchpad.net/ubuntu/+source/iproute/+bug/225997

Revision history for this message
Dave Walker (davewalker) wrote :

Can this still be reproduced in the currently supported releases?

Marking Incomplete until someone re-confirms, as I believe this bug is now fixed.

Changed in nmap (Ubuntu):
status: Triaged → Incomplete
Revision history for this message
Tore Anderson (toreanderson) wrote :

It's still a problem, yes. It's super-easy to reproduce, too:

root@adm:~# nmap -sP -PI 4.2.2.2

Starting Nmap 5.00 ( http://nmap.org ) at 2010-07-02 10:23 CEST
Host vnsc-bak.sys.gtei.net (4.2.2.2) is up (0.030s latency).
Nmap done: 1 IP address (1 host up) scanned in 0.37 seconds
root@adm:~# ip a a 169.254.1.1/16 dev eth0 label eth0foo
root@adm:~# nmap -sP -PI 4.2.2.2

Starting Nmap 5.00 ( http://nmap.org ) at 2010-07-02 10:24 CEST
Failed to determine the netmask of eth0foo!: No such device (19)
root@adm:~# dpkg -l nmap
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Cfg-files/Unpacked/Failed-cfg/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Description
+++-==============-==============-============================================
ii nmap 5.00-3 The Network Mapper

Tore

Revision history for this message
rusivi2 (rusivi2-deactivatedaccount) wrote :

Thank you for reporting this bug.

Does this issue occur in Maverick?

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for nmap (Ubuntu) because there has been no activity for 60 days.]

Changed in nmap (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.