Ethical Hacking Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package. | Computer Forensics Training at InfoSec Institute Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors. |

| Subject: | Large lists of target ip addresses in a file |
|---|---|
| Date: | Mon, 24 Jul 2006 16:07:33 -0400 |
Hello again, I have another question for the mailing list.
I have installed Nessus 3.0.3 on FC5, and it's working pretty well. I have it set up to do an ARP and TCP ping to detect if hosts are dead or alive, TCP syn port scan, and reading the target ip addresses from a file. checks_read_timeout is set to 4, plugins_timeout is set to 320.
The problem lies in Nessus not scanning properly when I increase the number of IP addresses in the target list. An example, using the same configuration for all:
Scanning 192.168.0.1 to 192.168.0.254 produces Hosts which were alive and responding during test 19 Number of security holes found 12 Number of security warnings found 29
Scanning 192.168.1.1 to 192.168.1.254 produces Hosts which were alive and responding during test 34 Number of security holes found 27 Number of security warnings found 73
Finally, the mystery. Putting the two lists of IP addresses together, and scanning 192.168.0.1 to 192.168.1.254 produces Hosts which were alive and responding during test 21 Number of security holes found 13 Number of security warnings found 32 I've run these multiple times, and they always produce the same results: the larger list of IPs produces inferior results compared to the subsets. Can anyone shine some light on this matter? I can provide configuration options as needed.
Thanks,
_______________________________________________ Nessus mailing list Nessus@list.nessus.org http://mail.nessus.org/mailman/listinfo/nessus
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | nessus Wifi Device detection, Federico Bolivar |
|---|---|
| Next by Date: | [SOLVED] Large lists of target ip addresses in a file, Andrew Wang |
| Previous by Thread: | nessus Wifi Device detection, Federico Bolivar |
| Next by Thread: | [SOLVED] Large lists of target ip addresses in a file, Andrew Wang |
| Indexes: | [Date] [Thread] [Top] [All Lists] |