Nmap Development mailing list archives
Re: nmap / zenmap fail: "Initiating NSE"
From: Mark Ballard <markjballard () googlemail com>
Date: Sun, 9 Jun 2013 16:43:01 +0100
And I just ran zenmap again with the error reporting parameter added: sudo nmap -sS -sU -T4 -A -v -PE -PP -PS80,443 -PA3389 -PU40125 -PY -g 53 --script "default or (discovery and safe)" -d2 --stats-every 10m --log-errors -oN zenmap_root_scan_result 86.190.44.119 This time it did not get stuck after saying "initiated NSE". It finished without a problem. This suggests the problem may be with zenmap startup. If I remember correctly, the zenmap problem occured when I ran it immediately after installation this morning. mb. On 9 June 2013 13:36, Mark Ballard <markjballard () googlemail com> wrote:
Hello A bug report follows. I would be grateful if you would advise me if there is anything I can do to correct this problem. Following conditions: Slow, comprehensive scan Zenmap 6.00 Xubuntu 13.04 i686 iptables rules: output of iptables -L in attached .txt file The scan did not complete as expected. nmap reported that it has "initiated NSE" at 10:23 this morning. Nothing has happened since. It is now 13:35. Note: this was a standard installation of Xubuntu, with install-standard iptables rules. Xenmap was also simply as installed. Zenmap worked on standard pass. Failed on comprehensive. nmap -sS -sU -T4 -A -v -PE -PP -PS80,443 -PA3389 -PU40125 -PY -g 53 --script "default or (discovery and safe)" 86.190.44.119 Starting Nmap 6.00 ( http://nmap.org ) at 2013-06-09 09:35 BST NSE: Loaded 177 scripts for scanning. NSE: Script Pre-scanning. Initiating NSE at 09:35 Completed NSE at 09:35, 5.66s elapsed Pre-scan script results: | targets-asn: |_ targets-asn.asn is a mandatory parameter Initiating Ping Scan at 09:35 Scanning 86.190.44.119 [7 ports] Completed Ping Scan at 09:35, 0.00s elapsed (1 total hosts) Initiating Parallel DNS resolution of 1 host. at 09:35 Completed Parallel DNS resolution of 1 host. at 09:35, 0.01s elapsed Initiating SYN Stealth Scan at 09:35 Scanning host86-190-44-119.wlms-broadband.com (86.190.44.119) [1000 ports] sendto in send_ip_packet_sd: sendto(7, packet, 44, 0, 86.190.44.119, 16) => Operation not permitted Offending packet: TCP 192.168.1.34:53 > 86.190.44.119:8080 S ttl=55 id=49785 iplen=44 seq=1147444538 win=1024 <mss 1460> sendto in send_ip_packet_sd: sendto(7, packet, 44, 0, 86.190.44.119, 16) => Operation not permitted Offending packet: TCP 192.168.1.34:53 > 86.190.44.119:587 S ttl=55 id=60404 iplen=44 seq=1147444538 win=1024 <mss 1460> sendto in send_ip_packet_sd: sendto(7, packet, 44, 0, 86.190.44.119, 16) => Operation not permitted Offending packet: TCP 192.168.1.34:53 > 86.190.44.119:256 S ttl=53 id=25238 iplen=44 seq=1147444538 win=1024 <mss 1460> sendto in send_ip_packet_sd: sendto(7, packet, 44, 0, 86.190.44.119, 16) => Operation not permitted Offending packet: TCP 192.168.1.34:53 > 86.190.44.119:993 S ttl=50 id=20328 iplen=44 seq=1147444538 win=1024 <mss 1460> sendto in send_ip_packet_sd: sendto(7, packet, 44, 0, 86.190.44.119, 16) => Operation not permitted Offending packet: TCP 192.168.1.34:53 > 86.190.44.119:554 S ttl=59 id=46028 iplen=44 seq=1147444538 win=1024 <mss 1460> sendto in send_ip_packet_sd: sendto(7, packet, 44, 0, 86.190.44.119, 16) => Operation not permitted Offending packet: TCP 192.168.1.34:53 > 86.190.44.119:139 S ttl=40 id=44216 iplen=44 seq=1147444538 win=1024 <mss 1460> sendto in send_ip_packet_sd: sendto(7, packet, 44, 0, 86.190.44.119, 16) => Operation not permitted Offending packet: TCP 192.168.1.34:53 > 86.190.44.119:8888 S ttl=58 id=40347 iplen=44 seq=1147444538 win=1024 <mss 1460> sendto in send_ip_packet_sd: sendto(7, packet, 44, 0, 86.190.44.119, 16) => Operation not permitted Offending packet: TCP 192.168.1.34:53 > 86.190.44.119:199 S ttl=54 id=9552 iplen=44 seq=1147444538 win=1024 <mss 1460> sendto in send_ip_packet_sd: sendto(7, packet, 44, 0, 86.190.44.119, 16) => Operation not permitted Offending packet: TCP 192.168.1.34:53 > 86.190.44.119:135 S ttl=59 id=30730 iplen=44 seq=1147444538 win=1024 <mss 1460> Discovered open port 23/tcp on 86.190.44.119 Discovered open port 21/tcp on 86.190.44.119 Discovered open port 80/tcp on 86.190.44.119 sendto in send_ip_packet_sd: sendto(7, packet, 44, 0, 86.190.44.119, 16) => Operation not permitted Offending packet: TCP 192.168.1.34:53 > 86.190.44.119:113 S ttl=45 id=49532 iplen=44 seq=1147444538 win=1024 <mss 1460> Omitting future Sendto error messages now that 10 have been shown. Use -d2 if you really want to see them. Completed SYN Stealth Scan at 09:36, 4.43s elapsed (1000 total ports) Initiating UDP Scan at 09:36 Scanning host86-190-44-119.wlms-broadband.com (86.190.44.119) [1000 ports] Completed UDP Scan at 09:36, 3.96s elapsed (1000 total ports) Initiating Service scan at 09:36 Scanning 1003 services on host86-190-44-119.wlms-broadband.com (86.190.44.119) Service scan Timing: About 0.40% done Service scan Timing: About 3.39% done; ETC: 10:57 (1:18:23 remaining) Service scan Timing: About 6.38% done; ETC: 10:40 (1:00:39 remaining) Service scan Timing: About 9.37% done; ETC: 10:34 (0:53:11 remaining) Service scan Timing: About 12.36% done; ETC: 10:31 (0:48:48 remaining) Service scan Timing: About 15.35% done; ETC: 10:29 (0:45:29 remaining) Service scan Timing: About 20.94% done; ETC: 10:22 (0:36:42 remaining) Service scan Timing: About 21.34% done; ETC: 10:27 (0:40:33 remaining) Service scan Timing: About 26.82% done; ETC: 10:22 (0:34:01 remaining) Service scan Timing: About 27.32% done; ETC: 10:26 (0:36:38 remaining) Service scan Timing: About 32.80% done; ETC: 10:22 (0:31:10 remaining) Service scan Timing: About 38.78% done; ETC: 10:22 (0:28:22 remaining) Service scan Timing: About 44.77% done; ETC: 10:22 (0:25:34 remaining) Service scan Timing: About 50.75% done; ETC: 10:22 (0:22:47 remaining) Service scan Timing: About 56.73% done; ETC: 10:22 (0:20:01 remaining) Service scan Timing: About 62.71% done; ETC: 10:22 (0:17:14 remaining) Service scan Timing: About 68.59% done; ETC: 10:22 (0:14:32 remaining) Service scan Timing: About 74.58% done; ETC: 10:22 (0:11:45 remaining) Service scan Timing: About 80.56% done; ETC: 10:22 (0:08:59 remaining) Service scan Timing: About 86.04% done; ETC: 10:22 (0:06:29 remaining) Service scan Timing: About 92.02% done; ETC: 10:22 (0:03:42 remaining) Service scan Timing: About 98.01% done; ETC: 10:22 (0:00:56 remaining) Completed Service scan at 10:22, 2807.10s elapsed (1003 services on 1 host) Initiating OS detection (try #1) against host86-190-44-119.wlms-broadband.com (86.190.44.119) Initiating Traceroute at 10:22 Completed Traceroute at 10:22, 3.03s elapsed NSE: Script scanning 86.190.44.119. Initiating NSE at 10:23 -- Best regards mb.
_______________________________________________ Sent through the dev mailing list http://nmap.org/mailman/listinfo/dev Archived at http://seclists.org/nmap-dev/
Current thread:
- nmap / zenmap fail: "Initiating NSE" Mark Ballard (Jun 09)
- Re: nmap / zenmap fail: "Initiating NSE" Mark Ballard (Jun 09)
- Re: nmap / zenmap fail: "Initiating NSE" Mark Ballard (Jun 09)