Re: nmap with nessus against Avaya P130

> The latest versions of the nmap.nasl
> wrapper disable those dangerous options (OS fingerprinting, TCP
> stealth scans, UDP scan, aggressive timings).
Do you mean that the plugin nmap.nasl has been updated?

> You should try scanning your gizmo with Nmap only.
 In fact, I've already done this, as i said in my first mail:
"First, i used Nmap only against the P130: no problem: 3 open ports (23,80 and 
4000) are detected as when i used nmap 3.75 alone". There was no reboot with 
nmap only. When i used Nessus running with nmap only (connect technique), the 
P130 never rebooted, but sometimes, the report did not display that the port 
4000 was opened. Would the plugin nmap be buggy?
The thing that i don't understand is why, when i run nessus with nmap, safe 
check or not, and Cajun P13x Dos enabled, nessus reports no security hole on 
port 4000 whereas the switch P130 reboots. In fact I see lots of packets 
arriving on the switch (meaning that nessus is doing the Dos) during 15-20 
seconds, then the switch crashes, 5 seconds later, nessus displays its report: 
no security hole! One time, it has even displayed "empty report". Don't you 
think it is strange?

Thanks
------------------------------------------

Faites un voeu et puis Voila ! www.voila.fr 

_______________________________________________
Nessus mailing list
Nessus@list.nessus.org
http://mail.nessus.org/mailman/listinfo/nessus