Hi all, I know this isn't really a Nessus issue, but it certainly affects Nessus. Over the last 6 months or so, I have seen NMAP performance tank heavily on a number of Linux systems I administer. It is a particular problem with full NMAP scans such as 'nmap -sT -p 1-65535 target.txt'. Whereas in the past, these would complete in a reasonable amount of time (less than an hour maybe, sometimes a bit more) I am now seeing them take days, sometimes not even completing at all. It is especially problematic on Internet hosts, and doesn't seem to rear its head much on the LAN side scans. I have set up a number of scans, and have seen results range from very slow, to the process dumping mysteriously (no messages to indicate why), to "RESOURCE UNAVAILABLE" messages being generated when using 'strace' to monitor the process.
I have tried it on different systems (all Linux) and the results are similar (if erratic). I have tried it on different ISP connections, and have gotten the same results. I have tried it on different hardware, and again the same results. I'm wondering if maybe there was a change in the Linux Kernel or something. At this point, I'm just throwing this out there to see if anyone has any comments. I know that I can do a number of things such as an alternate OS, Internet connection, and limiting the number of ports scanned, etc, etc. but am more interested in hearing if anyone else has seen this. It is possible that it is limited to my locale in some way (possibly our local ISPs have something in common) Thanks, Mark Lachniet - [EMAIL PROTECTED]: general discussions about Nessus. * To unsubscribe, send a mail to [EMAIL PROTECTED] with "unsubscribe nessus" in the body.
