In the Advanced tab there is an option under "UDP port scanner (NASL)" that says "Maximum run time in seconds: 0", are we correct to assume zero means unlimited, or does it literally mean 0secs, in which case it would not complete, and that could be Charles' problem.
One of the problems with UDP scans is that they take hours usually, so its probably best to do it as a separate process using nmap and rely on netstat from within Nessus - and/or import the nmap results. Would that satisfy the PCI dependency, or have we got to use the UDP plugin or the nmap plugin with UDP scanning enabled? Charles Wu wrote: > Per this message from the Nessus archive, it seems that a non nmap UDP > port scanner has been developed and implemented for Nessus > > http://www.mail-archive.com/nessus@list.nessus.org/msg17847.html > > So, went to the support site and grabbed the Nessus UDP Port Scanner > from the PCI Compliance page, followed the proper instructions to unzip > and build the plug-in database, and have the following configuration > (see below / attached screen shot) > > Based on these settings, I am under the impression that I have enabled > Nessus to scan BOTH TCP & UDP ports 1-65535 – however, the scan output > below states that a full UDP port scan isn’t occurring > > Any ideas / thoughts? What am I missing? -- Simon John nessus at the-jedi.co.uk _______________________________________________ Nessus mailing list Nessus@list.nessus.org http://mail.nessus.org/mailman/listinfo/nessus
