On Wed May 18 2005 at 03:36, Beirne Konarski wrote: >> It looks like it was the snmpwalk portscan.
> I've been told since that this is pretty unlikely. I guessed it because > it showed as having run the longest in the log. You did not say what kind of "DOS" you rencountered. If it was a service crash (not a device crash), there is another possibility if you restricted the port range. snmpwalk and netstat are not real scanners, they can find ports out of the user specified range. They behave as if you entered "1-65535" In this case, you cannot protect a fragile port by excluding it and setting "consider unscanned ports as closed". _______________________________________________ Nessus mailing list [email protected] http://mail.nessus.org/mailman/listinfo/nessus
