mirror of
https://github.com/nmap/nmap.git
synced 2026-08-04 14:49:29 +00:00
Document half-open and full-open IPv4 octet ranges.
This commit is contained in:
parent
5d2393d115
commit
b819aa7f25
1 changed files with 6 additions and 3 deletions
|
|
@ -187,8 +187,11 @@ address, you can specify a comma-separated list of numbers or ranges
|
|||
for each octet. For example, 192.168.0-255.1-254 will skip all
|
||||
addresses in the range that end in .0 or .255, and 192.168.3-5,7.1 will
|
||||
scan the four addresses 192.168.3.1, 192.168.4.1, 192.168.5.1, and
|
||||
192.168.7.1. Ranges need not be
|
||||
limited to the final octets: the specifier
|
||||
192.168.7.1. Either side of a range may be omitted; the default values
|
||||
are 0 on the left and 255 on the right. Using <literal>-</literal> by
|
||||
itself is the same as 0-255, but remember to use 0- in the first octet
|
||||
so the target specification doesn't look like a command-line option.
|
||||
Ranges need not be limited to the final octets: the specifier
|
||||
0-255.0-255.13.37 will perform an Internet-wide scan for all IP
|
||||
addresses ending in 13.37. This sort of broad sampling can be useful
|
||||
for Internet surveys and research.</para>
|
||||
|
|
@ -199,7 +202,7 @@ IPv6 because they are rarely useful.</para>
|
|||
|
||||
<para>Nmap accepts multiple host specifications on the command line,
|
||||
and they don't need to be the same type. The command <command>nmap
|
||||
scanme.nmap.org 192.168.0.0/8 10.0.0,1,3-7.0-255</command> does what
|
||||
scanme.nmap.org 192.168.0.0/8 10.0.0,1,3-7.-</command> does what
|
||||
you would expect.</para>
|
||||
|
||||
<para>While targets are usually specified on the command lines, the following options are also available to control target selection:</para>
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue