Nmap Development mailing list archives

--min-rate assertion failure


From: Kris Katterjohn <katterjohn () gmail com>
Date: Fri, 18 Apr 2008 20:58:16 -0500

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hey everyone,

I've run into a --min-rate assertion failure.  Actually, it's not
- --min-rate specifically as I didn't use it, but the RateMeter stuff that
is run regardless is the culprit.

I've attached a file with the command used and all of the normal output
from the scan.

Sorry for brevity but, as I'm going out for the night and can't look
into it myself (and also not familiar with the RateMeter code), I hope
this suffices.  I just think an assertion failure is important to be let
known :)

Thanks,
Kris Katterjohn

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iQIVAwUBSAlRs/9K37xXYl36AQI6wRAAuuX7wUFrb2I7MsV4cgW3PZ2JRm7ZjumB
wZHqUQlbj6I+1wy/ZznE1mHB5M12cNoLgTB9XuxxdP3vDsHea1AGjCD41HRIT4KA
jkBJtWEzB0/hw35OLNIF8JqN0h/ol4FcwmjMOFrIyqEZo817VJqFPEtIGZkFbs1D
EW8CQwG+dhUM8EBU9mL9KTnVUAO9hdBFGYaoIFwyIpVuykhByfK7EHoFwv/+bzyE
sOWKZQK69B2mzAIevwjERP+i80YACXhiu1tn2jgq43i+d5Ud/eQdgAARbsfWyxaM
l5xU5/F1Iu2bBjzDiFdWVCboQo4r0tc4IRvPy4mYVdJQJI69WkuQsq3CDEcQGld+
8IkS1nnaoEw2AEKLtw9xrL+b5YX5k7zOw4ZwSvCYo1cPnnyaW+WGRNfRwpMjs9DL
Qe7cvx+lxU2jgcYQW9I3vOs0fvy91NzhR8Zp31uE15wIo90j6rMm/MwrB85LpBhS
/vRluynD+fu9pTGhcwxpHmCMRK/vvUOIUuxV4bxAiZSuna1sQ8N8S4sFCkYzjkNX
yfG2KWNwyToaNbym1kiXG29jce7/BQovASOb/pxeUxaikVgKJzHU2liXLXnis/ic
4mj7VGODZ+noYg5CRjLbLptqHn45wYBx8d7Xeayvx6ImfVG0lJxyNbsp1nnjdVvZ
jg5l8o5ZebM=
=pz5J
-----END PGP SIGNATURE-----
$ sudo nmap -d -T4 -sSUV -O --script all 192.168.10.1/24

Starting Nmap 4.60 ( http://nmap.org ) at 2008-04-18 20:04 CDT
--------------- Timing report ---------------
  hostgroups: min 1, max 100000
  rtt-timeouts: init 500, min 100, max 1250
  max-scan-delay: TCP 10, UDP 1000
  parallelism: min 0, max 0
  max-retries: 6, host-timeout: 0
  min-rate: 0
---------------------------------------------
Initiating ARP Ping Scan at 20:04
Scanning 6 hosts [1 port/host]
Packet capture filter (device eth0): arp and ether dst host 00:0C:76:7D:90:33
Completed ARP Ping Scan at 20:04, 0.23s elapsed (6 total hosts)
Overall sending rates: 39.92 packets / s, 1676.77 bytes / s.
mass_rdns: Using DNS server 192.168.10.1
Initiating Parallel DNS resolution of 6 hosts. at 20:04
mass_rdns: 0.00s 0/2 [#: 1, OK: 0, NX: 0, DR: 0, SF: 0, TR: 2]
Completed Parallel DNS resolution of 6 hosts. at 20:04, 0.01s elapsed
DNS resolution of 2 IPs took 0.01s. Mode: Async [#: 1, OK: 2, NX: 0, DR: 0, SF: 0, TR: 2, CN: 0]
Initiating SYN Stealth Scan at 20:04
Scanning 5 hosts [1715 ports/host]
Packet capture filter (device eth0): dst host 192.168.10.6 and (icmp or (tcp and (src host 192.168.10.1 or src host 
192.168.10.2 or src host 192.168.10.3 or src host 192.168.10.4 or src host 192.168.10.5)))
Discovered open port 80/tcp on 192.168.10.5
Discovered open port 80/tcp on 192.168.10.1
Discovered open port 80/tcp on 192.168.10.2
Discovered open port 23/tcp on 192.168.10.2
Discovered open port 21/tcp on 192.168.10.2
Increased max_successful_tryno for 192.168.10.5 to 1 (packet drop)
Increased max_successful_tryno for 192.168.10.1 to 1 (packet drop)
Increased max_successful_tryno for 192.168.10.2 to 1 (packet drop)
Increasing send delay for 192.168.10.2 from 0 to 5 due to 11 out of 18 dropped probes since last increase.
Increased max_successful_tryno for 192.168.10.1 to 2 (packet drop)
Increased max_successful_tryno for 192.168.10.2 to 2 (packet drop)
Increased max_successful_tryno for 192.168.10.2 to 3 (packet drop)
Increased max_successful_tryno for 192.168.10.2 to 4 (packet drop)
Increased max_successful_tryno for 192.168.10.3 to 1 (packet drop)
Increased max_successful_tryno for 192.168.10.3 to 2 (packet drop)
Increased max_successful_tryno for 192.168.10.3 to 3 (packet drop)
Increased max_successful_tryno for 192.168.10.3 to 4 (packet drop)
Increasing send delay for 192.168.10.3 from 0 to 5 due to 19 out of 46 dropped probes since last increase.
Increased max_successful_tryno for 192.168.10.3 to 5 (packet drop)
Increasing send delay for 192.168.10.3 from 5 to 10 due to max_successful_tryno increase to 5
SYN Stealth Scan Timing: About 13.42% done; ETC: 20:08 (0:03:13 remaining)
SYN Stealth Scan Timing: About 27.70% done; ETC: 20:08 (0:02:36 remaining)
Increased max_successful_tryno for 192.168.10.2 to 5 (packet drop)
Increasing send delay for 192.168.10.2 from 5 to 10 due to max_successful_tryno increase to 5
Increased max_successful_tryno for 192.168.10.2 to 6 (packet drop)
Increased max_successful_tryno for 192.168.10.1 to 3 (packet drop)
Increased max_successful_tryno for 192.168.10.3 to 6 (packet drop)
Warning: Giving up on port early because retransmission cap hit.
SYN Stealth Scan Timing: About 36.58% done; ETC: 20:08 (0:02:36 remaining)
SYN Stealth Scan Timing: About 42.55% done; ETC: 20:09 (0:02:42 remaining)
SYN Stealth Scan Timing: About 53.73% done; ETC: 20:09 (0:02:09 remaining)
Completed SYN Stealth Scan against 192.168.10.5 in 150.91s (4 hosts left)
Completed SYN Stealth Scan against 192.168.10.4 in 151.00s (3 hosts left)
Increased max_successful_tryno for 192.168.10.1 to 4 (packet drop)
Increased max_successful_tryno for 192.168.10.1 to 5 (packet drop)
Increasing send delay for 192.168.10.1 from 0 to 5 due to max_successful_tryno increase to 5
Discovered open port 2601/tcp on 192.168.10.1
Discovered open port 5190/tcp on 192.168.10.1
Discovered open port 2602/tcp on 192.168.10.1
Completed SYN Stealth Scan against 192.168.10.1 in 160.51s (2 hosts left)
Completed SYN Stealth Scan against 192.168.10.2 in 171.40s (1 host left)
Completed SYN Stealth Scan at 20:09, 281.75s elapsed (8575 total ports)
Overall sending rates: 45.70 packets / s, 2010.68 bytes / s.
Initiating UDP Scan at 20:09
Scanning 5 hosts [1488 ports/host]
Packet capture filter (device eth0): dst host 192.168.10.6 and (icmp or (udp and (src host 192.168.10.1 or src host 
192.168.10.2 or src host 192.168.10.3 or src host 192.168.10.4 or src host 192.168.10.5)))
Increased max_successful_tryno for 192.168.10.1 to 1 (packet drop)
Increased max_successful_tryno for 192.168.10.5 to 1 (packet drop)
Increased max_successful_tryno for 192.168.10.3 to 1 (packet drop)
Increased max_successful_tryno for 192.168.10.5 to 2 (packet drop)
Increased max_successful_tryno for 192.168.10.1 to 2 (packet drop)
Increased max_successful_tryno for 192.168.10.3 to 2 (packet drop)
Increased max_successful_tryno for 192.168.10.5 to 3 (packet drop)
Increased max_successful_tryno for 192.168.10.1 to 3 (packet drop)
Increased max_successful_tryno for 192.168.10.3 to 3 (packet drop)
Increased max_successful_tryno for 192.168.10.1 to 4 (packet drop)
Increasing send delay for 192.168.10.3 from 0 to 50 due to 11 out of 18 dropped probes since last increase.
Increased max_successful_tryno for 192.168.10.3 to 4 (packet drop)
Increased max_successful_tryno for 192.168.10.5 to 4 (packet drop)
Increased max_successful_tryno for 192.168.10.1 to 5 (packet drop)
Increasing send delay for 192.168.10.1 from 0 to 50 due to max_successful_tryno increase to 5
Increased max_successful_tryno for 192.168.10.3 to 5 (packet drop)
Increasing send delay for 192.168.10.3 from 50 to 100 due to max_successful_tryno increase to 5
Increased max_successful_tryno for 192.168.10.1 to 6 (packet drop)
Increasing send delay for 192.168.10.1 from 50 to 100 due to max_successful_tryno increase to 6
Warning: Giving up on port early because retransmission cap hit.
Increased max_successful_tryno for 192.168.10.5 to 5 (packet drop)
Increasing send delay for 192.168.10.5 from 0 to 50 due to max_successful_tryno increase to 5
Increased max_successful_tryno for 192.168.10.3 to 6 (packet drop)
Increasing send delay for 192.168.10.3 from 100 to 200 due to max_successful_tryno increase to 6
Increasing send delay for 192.168.10.1 from 100 to 200 due to 11 out of 11 dropped probes since last increase.
Increased max_successful_tryno for 192.168.10.5 to 6 (packet drop)
Increasing send delay for 192.168.10.5 from 50 to 100 due to max_successful_tryno increase to 6
UDP Scan Timing: About 6.41% done; ETC: 20:17 (0:07:18 remaining)
Increasing send delay for 192.168.10.3 from 200 to 400 due to 11 out of 25 dropped probes since last increase.
Increasing send delay for 192.168.10.1 from 200 to 400 due to 11 out of 19 dropped probes since last increase.
Increasing send delay for 192.168.10.5 from 100 to 200 due to 11 out of 21 dropped probes since last increase.
Increasing send delay for 192.168.10.3 from 400 to 800 due to 11 out of 20 dropped probes since last increase.
Increasing send delay for 192.168.10.5 from 200 to 400 due to 11 out of 15 dropped probes since last increase.
UDP Scan Timing: About 12.58% done; ETC: 20:17 (0:06:57 remaining)
Increasing send delay for 192.168.10.1 from 400 to 800 due to 11 out of 26 dropped probes since last increase.
Increasing send delay for 192.168.10.5 from 400 to 800 due to 11 out of 27 dropped probes since last increase.
UDP Scan Timing: About 26.72% done; ETC: 20:14 (0:04:07 remaining)
Increasing send delay for 192.168.10.3 from 800 to 1000 due to 11 out of 15 dropped probes since last increase.
Completed UDP Scan against 192.168.10.2 in 110.51s (4 hosts left)
Completed UDP Scan against 192.168.10.4 in 113.84s (3 hosts left)
UDP Scan Timing: About 45.71% done; ETC: 20:13 (0:02:22 remaining)
UDP Scan Timing: About 46.81% done; ETC: 20:14 (0:02:51 remaining)
UDP Scan Timing: About 47.92% done; ETC: 20:15 (0:03:16 remaining)
UDP Scan Timing: About 48.92% done; ETC: 20:16 (0:03:40 remaining)
UDP Scan Timing: About 50.06% done; ETC: 20:17 (0:04:00 remaining)
UDP Scan Timing: About 51.10% done; ETC: 20:18 (0:04:19 remaining)
UDP Scan Timing: About 52.12% done; ETC: 20:18 (0:04:36 remaining)
UDP Scan Timing: About 53.07% done; ETC: 20:19 (0:04:53 remaining)
UDP Scan Timing: About 54.06% done; ETC: 20:20 (0:05:07 remaining)
UDP Scan Timing: About 54.98% done; ETC: 20:21 (0:05:20 remaining)
UDP Scan Timing: About 55.95% done; ETC: 20:21 (0:05:32 remaining)
UDP Scan Timing: About 56.87% done; ETC: 20:22 (0:05:42 remaining)
UDP Scan Timing: About 57.90% done; ETC: 20:23 (0:05:50 remaining)
UDP Scan Timing: About 58.82% done; ETC: 20:23 (0:05:58 remaining)
UDP Scan Timing: About 59.75% done; ETC: 20:24 (0:06:05 remaining)
UDP Scan Timing: About 60.84% done; ETC: 20:24 (0:06:08 remaining)
UDP Scan Timing: About 61.88% done; ETC: 20:25 (0:06:11 remaining)
UDP Scan Timing: About 62.98% done; ETC: 20:26 (0:06:11 remaining)
UDP Scan Timing: About 63.98% done; ETC: 20:26 (0:06:13 remaining)
UDP Scan Timing: About 64.98% done; ETC: 20:27 (0:06:13 remaining)
UDP Scan Timing: About 66.01% done; ETC: 20:27 (0:06:12 remaining)
UDP Scan Timing: About 67.03% done; ETC: 20:28 (0:06:10 remaining)
UDP Scan Timing: About 68.03% done; ETC: 20:28 (0:06:07 remaining)
UDP Scan Timing: About 68.99% done; ETC: 20:28 (0:06:05 remaining)
UDP Scan Timing: About 69.92% done; ETC: 20:29 (0:06:02 remaining)
UDP Scan Timing: About 70.93% done; ETC: 20:29 (0:05:57 remaining)
UDP Scan Timing: About 71.87% done; ETC: 20:30 (0:05:53 remaining)
UDP Scan Timing: About 72.84% done; ETC: 20:30 (0:05:47 remaining)
UDP Scan Timing: About 73.77% done; ETC: 20:31 (0:05:42 remaining)
UDP Scan Timing: About 74.68% done; ETC: 20:31 (0:05:37 remaining)
UDP Scan Timing: About 75.65% done; ETC: 20:31 (0:05:29 remaining)
UDP Scan Timing: About 76.58% done; ETC: 20:32 (0:05:22 remaining)
UDP Scan Timing: About 77.59% done; ETC: 20:32 (0:05:13 remaining)
UDP Scan Timing: About 78.54% done; ETC: 20:32 (0:05:04 remaining)
UDP Scan Timing: About 79.55% done; ETC: 20:33 (0:04:54 remaining)
UDP Scan Timing: About 80.54% done; ETC: 20:33 (0:04:43 remaining)
UDP Scan Timing: About 81.47% done; ETC: 20:33 (0:04:33 remaining)
UDP Scan Timing: About 82.32% done; ETC: 20:34 (0:04:25 remaining)
UDP Scan Timing: About 83.33% done; ETC: 20:34 (0:04:13 remaining)
UDP Scan Timing: About 84.24% done; ETC: 20:34 (0:04:02 remaining)
UDP Scan Timing: About 85.24% done; ETC: 20:35 (0:03:49 remaining)
UDP Scan Timing: About 86.20% done; ETC: 20:35 (0:03:36 remaining)
UDP Scan Timing: About 87.13% done; ETC: 20:35 (0:03:24 remaining)
UDP Scan Timing: About 88.05% done; ETC: 20:36 (0:03:12 remaining)
UDP Scan Timing: About 88.47% done; ETC: 20:36 (0:03:08 remaining)
UDP Scan Timing: About 88.57% done; ETC: 20:37 (0:03:10 remaining)
Completed UDP Scan against 192.168.10.5 in 1482.45s (2 hosts left)
UDP Scan Timing: About 88.67% done; ETC: 20:37 (0:03:12 remaining)
UDP Scan Timing: About 88.78% done; ETC: 20:38 (0:03:14 remaining)
Completed UDP Scan against 192.168.10.1 in 1536.13s (1 host left)
UDP Scan Timing: About 88.89% done; ETC: 20:38 (0:03:15 remaining)
UDP Scan Timing: About 89.04% done; ETC: 20:39 (0:03:16 remaining)
UDP Scan Timing: About 89.17% done; ETC: 20:39 (0:03:17 remaining)
UDP Scan Timing: About 89.28% done; ETC: 20:40 (0:03:18 remaining)
UDP Scan Timing: About 89.44% done; ETC: 20:40 (0:03:19 remaining)
UDP Scan Timing: About 89.61% done; ETC: 20:41 (0:03:19 remaining)
UDP Scan Timing: About 89.77% done; ETC: 20:41 (0:03:19 remaining)
UDP Scan Timing: About 89.94% done; ETC: 20:42 (0:03:18 remaining)
UDP Scan Timing: About 90.10% done; ETC: 20:42 (0:03:18 remaining)
UDP Scan Timing: About 90.32% done; ETC: 20:43 (0:03:16 remaining)
UDP Scan Timing: About 90.48% done; ETC: 20:43 (0:03:16 remaining)
UDP Scan Timing: About 90.64% done; ETC: 20:44 (0:03:15 remaining)
UDP Scan Timing: About 90.78% done; ETC: 20:44 (0:03:15 remaining)
UDP Scan Timing: About 90.94% done; ETC: 20:45 (0:03:14 remaining)
UDP Scan Timing: About 91.09% done; ETC: 20:45 (0:03:14 remaining)
UDP Scan Timing: About 91.22% done; ETC: 20:46 (0:03:14 remaining)
UDP Scan Timing: About 91.36% done; ETC: 20:46 (0:03:13 remaining)
UDP Scan Timing: About 91.52% done; ETC: 20:47 (0:03:12 remaining)
UDP Scan Timing: About 91.66% done; ETC: 20:47 (0:03:11 remaining)
UDP Scan Timing: About 91.76% done; ETC: 20:48 (0:03:12 remaining)
nmap: timing.cc:342: void RateMeter::update(u32, u32, const timeval*): Assertion `d >= 0' failed.
Aborted (core dumped)


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

Current thread: