Memory problem when scanning testrange

[Dieter Van der Stock <dietervds () gmail com>]

Hello everyone,

While trying to run an Nmap scan against a 10.10.0.0/17 range, the Nmap
process is automatically killed because of too much memory usage.

In syslog it says (after a whole output dump of memory stuff):
kernel: Out of memory: kill process 28648 (bash) score 8319 or a child
kernel: Killed process 28662 (nmap)

The Nmap command run was:
/usr/bin/nmap -T4 -n -p 1-65535 -oX largescan.xml 10.10.0.0/17

The version of Nmap being used: Nmap 4.85BETA9

Does anyone have any idea what can be done to prevent this?
I suppose it's not an everyday-usage scenario of Nmap, but I'm basicly
checking out how far I can push it :)

Cheers and with regards to you all,

Dieter

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