Hi all, I want to automate scanning of our entire network as a batch job.
I am trying to run nessus (without gui) using: #nessus -x -T txt -q nesserver.corp 1241 root $$$$$ /tmp/targets /tmp/results The /tmp/targets file contains: xx.111.36.1 xx.111.36.2 xx.111.36.50 xx.111.36.51 xx.111.36.52 xx.111.36.100 xx.111.36.101 xx.111.36.102 xx.111.36.103 xx.111.36.104 xx.111.36.105 xx.111.36.129 xx.111.36.130 xx.111.36.132 xx.111.36.134 xx.111.36.141 xx.111.36.142 xx.111.36.143 xx.111.36.144 xx.111.36.145 xx.111.36.150 xx.111.36.169 xx.111.36.174 xx.111.36.177 xx.111.36.182 xx.111.36.186 xx.111.36.189 The problem is that I get inconsistent number of "TESTED HOSTS" for consecutive runs. While one run of nessus thinks that 8 hosts are up, the very next run (10 minutes later) sees 6 different machines (from the above set) as up and reports about them. The nmap scan in the beginning of each run sees ALL 27 hosts (as responding to pings). I have max_hosts set to 30 and I am pretty sure none of the hosts are becoming unreachable or dying. >From the top part of the generated reports: A) TESTED HOSTS xx.111.36.174 (Security notes found) xx.111.36.1 (Security holes found) xx.111.36.130 (Security holes found) xx.111.36.129 (Security holes found) xx.111.36.51 (Security holes found) xx.111.36.105 (Security warnings found) xx.111.36.132 (Security warnings found) b) TESTED HOSTS xx.111.36.103 (Security holes found) xx.111.36.141 (Security holes found) xx.111.36.102 (Security holes found) xx.111.36.144 (Security holes found) xx.111.36.143 (Security holes found) xx.111.36.142 (Security holes found) c) TESTED HOSTS xx.111.36.103 (Security holes found) xx.111.36.102 (Security holes found) xx.111.36.145 (Security holes found) xx.111.36.101 (Security notes found) xx.111.36.144 (Security holes found) xx.111.36.105 (Security holes found) xx.111.36.143 (Security holes found) xx.111.36.142 (Security holes found) Why this strange behavior ? Thx, -ansh
