Home page logo
/

nmap-dev logo Nmap Development mailing list archives

nmap 4.01 scan_engine.cc:1828: bool ultrascan_port_pspec_update(...): Assertion `0' failed.
From: "Tobias Krawutschke" <Tobias.Krawutschke () koeln de>
Date: Wed, 22 Mar 2006 10:11:35 +0100

Hello,
I compiled nmap 4.01 and 4.02Alpha2 on a redhat 9.0 machine with 

./configure --without-nmapfe --without-openssl

I skipped both fe and openssl because configure did not find some
headers/libs needed to compile. After compilation and installation
I see a strange behaviour while doing a ping scan as root:

[root () krawutschke autoupdate]# nmap -v -T3 -sP 10.0.0.0/16
Starting Nmap 4.01 ( http://www.insecure.org/nmap/ ) at 2006-03-21 
17:25 CET
Initiating ARP Ping Scan against 10.0.0.0 [1 port] at 17:25
The ARP Ping Scan took 0.23s to scan 1 total hosts.
DNS resolution of 0 IPs took 0.00s. Mode: Async [#: 2, OK: 0, NX: 0, 
DR: 0, SF: 0, TR: 0, CN: 0]
Host 10.0.0.0 appears to be down.
DNS resolution of 1 IPs took 0.00s. Mode: Async [#: 2, OK: 0, NX: 1, 
DR: 0, SF: 0, TR: 1, CN: 0]
Host 10.0.0.1 appears to be up.
Initiating ARP Ping Scan against 2048 hosts [1 port/host] at 17:25
nmap: scan_engine.cc:1828: bool 
ultrascan_port_pspec_update(UltraScanInfo*, HostScanStats*, const 
probespec*, int): Assertion `0' failed.
Aborted

I tried 4.02Alpha2 and the same but in line 1678, which is the same 
else branch.

I added the --packet-trace option and observed this error after 100 up 
to more than 1000 packets, but there is always a long pause before the 
error message:  

[root () krawutschke autoupdate]# nmap -v -n -sP --packet-trace 
10.0.0.0/16
Starting Nmap 4.02Alpha2 ( http://www.insecure.org/nmap/ ) at 2006-03-
21 18:17 CET
...
SENT (33.3640s) ARP who-has 10.0.5.68 tell 10.0.0.1
SENT (33.3650s) ARP who-has 10.0.5.69 tell 10.0.0.1
SENT (33.3650s) ARP who-has 10.0.5.70 tell 10.0.0.1
SENT (34.4190s) ARP who-has 10.0.5.72 tell 10.0.0.1  !! ~1 second pause
SENT (34.4200s) ARP who-has 10.0.5.73 tell 10.0.0.1
SENT (34.4240s) ARP who-has 10.0.5.71 tell 10.0.0.1
SENT (34.4380s) ARP who-has 10.0.5.74 tell 10.0.0.1
SENT (34.4390s) ARP who-has 10.0.5.75 tell 10.0.0.1
SENT (34.4400s) ARP who-has 10.0.5.76 tell 10.0.0.1
SENT (34.4400s) ARP who-has 10.0.5.77 tell 10.0.0.1
SENT (34.4400s) ARP who-has 10.0.5.78 tell 10.0.0.1
SENT (34.4400s) ARP who-has 10.0.5.79 tell 10.0.0.1
SENT (34.4400s) ARP who-has 10.0.5.80 tell 10.0.0.1
SENT (34.4400s) ARP who-has 10.0.5.81 tell 10.0.0.1
SENT (34.4410s) ARP who-has 10.0.5.82 tell 10.0.0.1
nmap: scan_engine.cc:1678: bool 
ultrascan_port_pspec_update(UltraScanInfo*, HostScanStats*, const 
probespec*, int): Assertion `0' failed.


I even can provoke this error when I press Ctrl+S for Suspend and wait
a short time and then continue with Ctrl+D (only in possible with --
packet-trace on) Is this behaviour expected? Should I focus on my 
network adapter why it blocks for such a long time?

Tobias


_______________________________________________
Sent through the nmap-dev mailing list
http://cgi.insecure.org/mailman/listinfo/nmap-dev


  By Date           By Thread  

Current thread:
[ Nmap | Sec Tools | Mailing Lists | Site News | About/Contact | Advertising | Privacy ]