Nmap Development mailing list archives

Re: Protocol specific port lists - setting TCP ports removes UDP default list


From: wolfric1 <wolfric1 () gmail com>
Date: Sat, 30 Oct 2010 01:54:20 +0100

AFAIK you can't do tcp top ports or udp top ports... the reason you're only
getting tcp ports is you specified T:1-100 for tcp ports and no udp ports.
try

nmap -vvv -n -r -sS -sU -pT-,U:22,80,etc  <target>

the - after t scans all ports
If you want though you can do --top-ports # to do top ports. If you specify
-p you'll get rid of the top ports. if you just do --top-ports, it'll do the
top ports for both tcp and udp for the same amount.

Wolfric


On Fri, Oct 29, 2010 at 4:06 PM, Marcus Haebler <haebler () gmail com> wrote:

Hi,

I am trying to figure out if the following behavior is a bug or a feature:

nmap -vvv -n -r -sS -sU -p T:1-100 <target>

This will scan TCP ports 1-100 but no UDP ports. The UDP port list is empty
and consequently no scan is done. I would have expected that the UDP port
list is still the default list of ports.

The documentation does not mention this behavior. If it turns out to be the
desired behavior it should be added to the documentation.

BTW what I really want to do is scan the top 1000 UDP ports and all 64k TCP
ports in one scan. This seems to be impossible in a single scan at this
point since --top-ports seems to take precedence over everything specified
with -p.

# nmap -V
Nmap version 5.35DC1 ( http://nmap.org )


Thanks,

Marcus
_______________________________________________
Sent through the nmap-dev mailing list
http://cgi.insecure.org/mailman/listinfo/nmap-dev
Archived at http://seclists.org/nmap-dev/

_______________________________________________
Sent through the nmap-dev mailing list
http://cgi.insecure.org/mailman/listinfo/nmap-dev
Archived at http://seclists.org/nmap-dev/


Current thread: