Hi there - I managed the Tier III support for Ciena's CoreSwitching
Platform and am having a customer issue with NMAP (4.2.0.7) and VxWorks
(5.3.1). When we run the following command:
/nmap -sT -O -p 21,22,23,137,138,139,2001,6000 ip-address
Infrequently, but very recreatable in our lab, the execution of the NMAP
command leaves the VxWorks FTP connection open with a CLOSE_WAIT status,
even though the NMAP is completed. Eventually if we run the command
enough, we can exhaust up enough resources and lock up our connecitity.
Interesting when we run the command without the -O option, we do not run
into this issue. Since the FTP protocol is on the VxWorks stack, we
feel confident that it is not our code causing the issue.
Is this something that has been seen before, and do you have any
suggestions?
Thanks,
Matt
Matt Becker
Ciena Corp
Director, P&T
678-867-3616
mbecker_at_ciena.com
_______________________________________________
Sent through the nmap-dev mailing list
http://cgi.insecure.org/mailman/listinfo/nmap-dev
Archived at http://SecLists.Org
Received on Feb 14 2007
Intro
