Question about performance when using Target.add()

[Raul Fuentes <ra.fuentess.sam () gmail com>]

I have been working some NSE scripts for scanning IPv6 nodes - based on
https://tools.ietf.org/id/draft-gont-opsec-ipv6-host-scanning-02.txt

But I have been seeing a behaviour of Nmap 6.40 I can't understand very
well, when I uses "nmap 2000:db8::/104" or "nmap 10.0.0.0/8"  I can see a
very big continutones flow of probes, usually like this one:
https://lh3.googleusercontent.com/FW9kOANxjsk8gHOtqRfJqHVuz3U6F7_7o6mwHV2cBzg=w680-h329-noor
this
https://lh6.googleusercontent.com/-v1rtyE2UQyo/UoV_MyYadNI/AAAAAAAABEU/dJJTWq2VMb4/w680-h329-no/Itsis-4bits.png
.

However, when I'm adding a lot of nodes using target.add(), sometimes work
like the two previous but usually send "pulses" like this:
https://lh5.googleusercontent.com/-AIlkHR_bJHc/UoV_Z46Qr7I/AAAAAAAABEk/6geZhSxkFMs/w678-h318-no/nmap_todos4bis_sudo_1.pngor
change between both behaviours.

I'm not using any  time parameter and  should be working with  default -T3
performance.

At first I thougt the reason was  the nodes  were being added by hand
instead using the core of Nmap, but   sometime the behaviour change and
return to a big continuos flow of probes and that leave me perplex. I'm not
sure if this could be the reason why  scanning 24 bits on IPv6 take me al
lot  more time than scanning 24 bits on IPv4.

Any idea about this could be very appreciate.

<https://tools.ietf.org/id/draft-gont-opsec-ipv6-host-scanning-02.txt>--
Sincerely, Eng. Raul A. Fuentes Samaniego
_______________________________________________
Sent through the dev mailing list
http://nmap.org/mailman/listinfo/dev
Archived at http://seclists.org/nmap-dev/