I have always had issues when running nessus on subnets. It may just be
my crappy systems I used to test with but it seemed to work faster and
not have near as many problems working with a file with only hosts. I
have also found that by running my nmap (which works fine with subnets)
and feeding the nmap details to nessus to base my scans on that nessus
runs smoother and provides quicker scan results for large networks. But
if you are in a hurry you could do some creative perl or sh magic to
generate your host files and nessus will work through them just fine.
Just my experience with Nessus. Hope it helps!
Mike M
Alex Campoe wrote:
Well, I have situations here in which, due to list maintenance
problems, it is easier for me to pass a long list of individual
machines instead of a miriad of tiny little ranges.
Perhaps Nicolas could work on (b) for the next release, if that's an
option.
Alex
Renaud Deraison wrote:
On Thu, Apr 28, 2005 at 10:38:44AM -0400, Alex Campoe wrote:
So, is there a limit on the number of characters/hosts you can pass
to nessus?
2Gb.
This would be an issue for scans in general, not only involving
NessusWX.
It only affects NessusWX. The issue is that NessusWX :
a) Pre-computes the list of IPs to scan (it should send a range and
let nessusd compute what to scan)
b) Misuses the communication protocol and uses the 'short' scan-start
message instead of the long version.
-- Renaud
_______________________________________________
Nessus mailing list
Nessus@list.nessus.org
http://mail.nessus.org/mailman/listinfo/nessus
------------------------------------------------------------------------
_______________________________________________
Nessus mailing list
Nessus@list.nessus.org
http://mail.nessus.org/mailman/listinfo/nessus
_______________________________________________
Nessus mailing list
Nessus@list.nessus.org
http://mail.nessus.org/mailman/listinfo/nessus
