Nmap Development mailing list archives
No targets were specified error
From: Jesper Kückelhahn <dev.kyckel () gmail com>
Date: Thu, 24 Jan 2013 00:46:57 +0100
Hi list, After updating to an svn revision after 30538 I'm getting some strange errors, that might to be related to the input arguments to nmap. If I attempt to execute a basic nmap scan, I get a warning that no targets were specified. " $ nmap 192.168.1.20 Starting Nmap 6.26SVN ( http://nmap.org ) at 2013-01-24 00:35 CET WARNING: No targets were specified, so 0 hosts scanned. Nmap done: 0 IP addresses (0 hosts up) scanned in 0.06 seconds " If I add a single debugging flag I get the same error, but if I add two i get: " $ nmap -dd 192.168.1.20 Starting Nmap 6.26SVN ( http://nmap.org ) at 2013-01-24 00:37 CET Fetchfile found /usr/local/bin/../share/nmap/nmap-services PORTS: Using top 1000 ports found open (TCP:1000, UDP:0, SCTP:0) Fetchfile found /usr/local/bin/../share/nmap/nmap.xsl The max # of sockets we are using is: 0 --------------- Timing report --------------- hostgroups: min 1, max 100000 rtt-timeouts: init 1000, min 100, max 10000 max-scan-delay: TCP 1000, UDP 1000, SCTP 1000 parallelism: min 0, max 0 max-retries: 10, host-timeout: 0 min-rate: 0, max-rate: 0 --------------------------------------------- Fetchfile found /usr/local/bin/../share/nmap/nmap-payloads Initiating Ping Scan at 00:37 Scanning 192.168.1.20 [2 ports] Strange error from connect (22):Invalid argument ultrascan_host_probe_update called for machine 192.168.1.20 state UNKNOWN -> HOST_DOWN (trynum 0 time: 73) Completed Ping Scan at 00:37, 0.00s elapsed (1 total hosts) Overall sending rates: 7518.80 packets / s. mass_rdns: Using DNS server xxx.xxx.xxx.xxx mass_rdns: Using DNS server xxx.xxx.xxx.xxx Nmap scan report for 192.168.1.20 [host down, received unknown-response] Read from /usr/local/bin/../share/nmap: nmap-payloads nmap-services. Note: Host seems down. If it is really up, but blocking our ping probes, try -Pn Nmap done: 1 IP address (0 hosts up) scanned in 0.03 seconds " Adding an extra debugging flag gives: " HomerMac:nmap kyckel$ nmap -ddd 192.168.1.20 Starting Nmap 6.26SVN ( http://nmap.org ) at 2013-01-24 00:39 CET Fetchfile found /usr/local/bin/../share/nmap/nmap-services PORTS: Using top 1000 ports found open (TCP:1000, UDP:0, SCTP:0) Fetchfile found /usr/local/bin/../share/nmap/nmap.xsl The max # of sockets we are using is: 0 --------------- Timing report --------------- hostgroups: min 1, max 100000 rtt-timeouts: init 1000, min 100, max 10000 max-scan-delay: TCP 1000, UDP 1000, SCTP 1000 parallelism: min 0, max 0 max-retries: 10, host-timeout: 0 min-rate: 0, max-rate: 0 --------------------------------------------- Fetchfile found /usr/local/bin/../share/nmap/nmap-payloads Initiating Ping Scan at 00:39 Scanning 4096 hosts [2 ports/host] CONN (0.0587s) TCP localhost > 0.5.1.5:80 => Invalid argument Strange error from connect (22):Invalid argument ultrascan_host_probe_update called for machine 0.5.1.5 state UNKNOWN -> HOST_DOWN (trynum 0 time: 91) CONN (0.0588s) TCP localhost > 0.5.1.6:80 => Invalid argument ultrascan_host_probe_update called for machine 0.5.1.6 state UNKNOWN -> HOST_DOWN (trynum 0 time: 19) CONN (0.0588s) TCP localhost > 0.5.1.10:80 => Invalid argument ultrascan_host_probe_update called for machine 0.5.1.10 state UNKNOWN -> HOST_DOWN (trynum 0 time: 16) CONN (0.0588s) TCP localhost > 0.5.1.13:80 => Invalid argument ultrascan_host_probe_update called for machine 0.5.1.13 state UNKNOWN -> HOST_DOWN (trynum 0 time: 15) ….. [SNIP] ….. ultrascan_host_probe_update called for machine 0.5.1.125 state UNKNOWN -> HOST_DOWN (trynum 0 time: 15) **TIMING STATS** (0.0598s): IP, probes active/freshportsleft/retry_stack/outstanding/retranwait/onbench, cwnd/ssthresh/delay, timeout/srtt/rttvar/ Groupstats (4096/4096 incomplete): 0/*/*/*/*/* 60.00/75/* 100000/7/0 Current sending rates: 17325.02 packets / s. Overall sending rates: 17325.02 packets / s. Moving 0.5.1.5 to completed hosts list with 0 outstanding probes. Moving 0.5.1.6 to completed hosts list with 0 outstanding probes. Moving 0.5.1.10 to completed hosts list with 0 outstanding probes. Moving 0.5.1.13 to completed hosts list with 0 outstanding probes. " _______________________________________________ Sent through the dev mailing list http://nmap.org/mailman/listinfo/dev Archived at http://seclists.org/nmap-dev/
Current thread:
- No targets were specified error Jesper Kückelhahn (Jan 23)
- Re: No targets were specified error David Fifield (Jan 24)
- Re: No targets were specified error Jesper Kückelhahn (Jan 24)
- Re: No targets were specified error David Fifield (Jan 25)
- Re: No targets were specified error Jesper Kückelhahn (Jan 26)
- Re: No targets were specified error Jesper Kückelhahn (Jan 24)
- Re: No targets were specified error David Fifield (Jan 24)