I've got 4.11 on Gentoo and I have just verified this:
# nmap -sP -p1-1024 192.168.1.5
Starting Nmap 4.11 ( http://www.insecure.org/nmap/ ) at 2006-10-12 09:23
BST
No ports specified -- If you really don't want to scan any ports use
ping scan...
QUITTING!
-h
Hari Sekhon
Mike Wallette wrote:
> Hello!
>
> While running nmap against a host on my internal network today, I specified a pair of mutually incompatible options by mistake. nmap displayed an error message and terminated without running the scan, as it should, but the error message returned didn't quite match the problem:
>
> $ sudo nmap -sP -v -v -v -p1-1024 192.168.3.62
>
> Starting Nmap 4.11 ( http://www.insecure.org/nmap/ ) at 2006-10-11 09:36 AKDT
> No ports specified -- If you really don't want to scan any ports use ping scan...
> QUITTING!
> $
>
> As you can see, I *was* using a ping scan, and I *did* specify ports. Of course, that was the problem--you shouldn't specify ports when running a ping scan. Not a big problem, but I thought I would point it out, in case you'd like to fix it.
>
> Here is the relevant system information regarding the host from which I was running the scan:
>
> $ uname -a
> Linux 2.6.17-gentoo-r8 #1 SMP PREEMPT Wed Sep 20 15:51:03 AKDT 2006 i686 Genuine Intel(R) CPU T2600 @ 2.16GHz GNU/Linux
> $ sudo nmap -V
>
> Nmap version 4.11 ( http://www.insecure.org/nmap/ )
> $
>
> Sincerely,
>
> Michael Wallette
> mike_at_gecko-ak.org
>
> _______________________________________________
> Sent through the nmap-dev mailing list
> http://cgi.insecure.org/mailman/listinfo/nmap-dev
> Archived at http://SecLists.Org
>
>
_______________________________________________
Sent through the nmap-dev mailing list
http://cgi.insecure.org/mailman/listinfo/nmap-dev
Archived at http://SecLists.Org
Received on Oct 12 2006
Intro
