Re: [Nmap-scanner-general] udp_scan problem
Brought to you by:
perldork
From: Max <nm...@we...> - 2006-05-02 02:07:14
|
Hi Julien, I am sorry for the delayed response. I have not tested the Nmap::Scanner module against 4.0.x of nmap yet, but will this week and hopefully will hav= e a fix to make this work for you by the end of the weekend, which is probabl= y too late for you now, but maybe will let you use the module again another time. Again, my apologies for the delay in response and thank you for using the module. - Max On 4/25/06, Moutet Julien <jul...@gm...> wrote: > > Hi > > I have problems with "udp_scan" scan type. When using provided examples > (scan_to_xml.pl by example), the output is: > > # perl scan_to_xml.pl 192.168.1.10 > <nmap-error> > <pid=3D"5889"/> > <cmdline=3D"'/usr/bin/nmap' -v -v -v -sS -sU -p > 21,25,80,443,3306,8080,22,79,13,11,7,10 -P B -O --max_rtt_timeout 200 -o= X - > 192.168.1.10"/> > <perl-msg>Document requires an element [Ln: 1, Col: 1] > </perl-msg> > <nmap-msg>ARNING: UDP scan was requested, but no udp ports were > specified. Skipping this scan type. > </nmap-msg> > </nmap-error> > > From command line, the result is the same. > > The problem seems to be in the -p argument ( "U:" and "T:" ) : > > # man nmap > [...] > PORT SPECIFICATION AND SCAN ORDER: > -p <port ranges>: Only scan specified ports > Ex: -p22; -p1-65535; -p U:53,111,137,T:21-25,80,139,8080 > [...] > > Informations: > nmap-scanner-0.9 > nmap 4.0 > perl 5.8.8 > > > Any suggestions. > Thx in advance. > -- > Julien Moutet > > Student in Telecoms and Network Computing > http://www.stri.net/ > > > > |