nmap.1

Ubuntu packages of security software。 相当不错的源码

\fIevery\fR
target IP address specified\. So if a class B sized target address space (/16) is specified on the command line, all 65,536 IP addresses are scanned\. Proper host discovery is skipped as with the list scan, but instead of stopping and printing the target list, Nmap continues to perform requested functions as if each target IP is active\. For machines on a local ethernet network, ARP scanning will still be performed (unless
\fB\-\-send\-ip\fR
is specified) because Nmap needs MAC addresses to further scan target hosts\. This option flag for this used to be
\fBP0\fR
(uses zero), but was renamed to avoid confusion with protocol ping\'s
\fBPO\fR
(uses the letter O) flag\.
.RE
.PP
\fB\-PS [portlist]\fR (TCP SYN Ping)
.RS 4
This option sends an empty TCP packet with the SYN flag set\. The default destination port is 80 (configurable at compile time by changing DEFAULT_TCP_PROBE_PORT_SPEC in
\fInmap\.h\fR)\. Alternate ports can be specified as a parameter\. The syntax is the same as for the
\fB\-p\fR
except that port type specifiers like
T:
are not allowed\. Examples are
\fB\-PS22\fR
and
\fB\-PS22\-25,80,113,1050,35000\fR\. Note that there can be no space between
\fB\-PS\fR
and the port list\. If multiple probes are specified they will be sent in parallel\.
.sp
The SYN flag suggests to the remote system that you are attempting to establish a connection\. Normally the destination port will be closed, and a RST (reset) packet sent back\. If the port happens to be open, the target will take the second step of a TCP 3\-way\-handshake by responding with a SYN/ACK TCP packet\. The machine running Nmap then tears down the nascent connection by responding with a RST rather than sending an ACK packet which would complete the 3\-way\-handshake and establish a full connection\. The RST packet is sent by the kernel of the machine running Nmap in response to the unexpected SYN/ACK, not by Nmap itself\.
.sp
Nmap does not care whether the port is open or closed\. Either the RST or SYN/ACK response discussed previously tell Nmap that the host is available and responsive\.
.sp
On Unix boxes, only the privileged user
root
is generally able to send and receive raw TCP packets\. For unprivileged users, a workaround is automatically employed whereby the connect() system call is initiated against each target port\. This has the effect of sending a SYN packet to the target host, in an attempt to establish a connection\. If connect() returns with a quick success or an ECONNREFUSED failure, the underlying TCP stack must have received a SYN/ACK or RST and the host is marked available\. If the connection attempt is left hanging until a timeout is reached, the host is marked as down\. This workaround is also used for IPv6 connections, as raw IPv6 packet building support is not yet available in Nmap\.
.RE
.PP
\fB\-PA [portlist]\fR (TCP ACK Ping)
.RS 4
The TCP ACK ping is quite similar to the just\-discussed SYN ping\. The difference, as you could likely guess, is that the TCP ACK flag is set instead of the SYN flag\. Such an ACK packet purports to be acknowledging data over an established TCP connection, but no such connection exists\. So remote hosts should always respond with a RST packet, disclosing their existence in the process\.
.sp
The
\fB\-PA\fR
option uses the same default port as the SYN probe (80) and can also take a list of destination ports in the same format\. If an unprivileged user tries this, or an IPv6 target is specified, the connect() workaround discussed previously is used\. This workaround is imperfect because connect() is actually sending a SYN packet rather than an ACK\.
.sp
The reason for offering both SYN and ACK ping probes is to maximize the chances of bypassing firewalls\. Many administrators configure routers and other simple firewalls to block incoming SYN packets except for those destined for public services like the company web site or mail server\. This prevents other incoming connections to the organization, while allowing users to make unobstructed outgoing connections to the Internet\. This non\-stateful approach takes up few resources on the firewall/router and is widely supported by hardware and software filters\. The Linux Netfilter/iptables firewall software offers the
\fB\-\-syn\fR
convenience option to implement this stateless approach\. When stateless firewall rules such as this are in place, SYN ping probes (\fB\-PS\fR) are likely to be blocked when sent to closed target ports\. In such cases, the ACK probe shines as it cuts right through these rules\.
.sp
Another common type of firewall uses stateful rules that drop unexpected packets\. This feature was initially found mostly on high\-end firewalls, though it has become much more common over the years\. The Linux Netfilter/iptables system supports this through the
\fB\-\-state\fR
option, which categorizes packets based on connection state\. A SYN probe is more likely to work against such a system, as unexpected ACK packets are generally recognized as bogus and dropped\. A solution to this quandary is to send both SYN and ACK probes by specifying
\fB\-PS\fR
and
\fB\-PA\fR\.
.RE
.PP
\fB\-PU [portlist]\fR (UDP Ping)
.RS 4
Another host discovery option is the UDP ping, which sends an empty (unless
\fB\-\-data\-length\fR
is specified) UDP packet to the given ports\. The portlist takes the same format as with the previously discussed
\fB\-PS\fR
and
\fB\-PA\fR
options\. If no ports are specified, the default is 31338\. This default can be configured at compile\-time by changing DEFAULT_UDP_PROBE_PORT_SPEC in
\fInmap\.h\fR\. A highly uncommon port is used by default because sending to open ports is often undesirable for this particular scan type\.
.sp
Upon hitting a closed port on the target machine, the UDP probe should elicit an ICMP port unreachable packet in return\. This signifies to Nmap that the machine is up and available\. Many other types of ICMP errors, such as host/network unreachables or TTL exceeded are indicative of a down or unreachable host\. A lack of response is also interpreted this way\. If an open port is reached, most services simply ignore the empty packet and fail to return any response\. This is why the default probe port is 31338, which is highly unlikely to be in use\. A few services, such as chargen, will respond to an empty UDP packet, and thus disclose to Nmap that the machine is available\.
.sp
The primary advantage of this scan type is that it bypasses firewalls and filters that only screen TCP\. For example, I once owned a Linksys BEFW11S4 wireless broadband router\. The external interface of this device filtered all TCP ports by default, but UDP probes would still elicit port unreachable messages and thus give away the device\.
.RE
.PP
\fB\-PE\fR; \fB\-PP\fR; \fB\-PM\fR (ICMP Ping Types)
.RS 4
In addition to the unusual TCP and UDP host discovery types discussed previously, Nmap can send the standard packets sent by the ubiquitous
ping
program\. Nmap sends an ICMP type 8 (echo request) packet to the target IP addresses, expecting a type 0 (echo reply) in return from available hosts\. Unfortunately for network explorers, many hosts and firewalls now block these packets, rather than responding as required by
\fIRFC 1122\fR\&[1]\. For this reason, ICMP\-only scans are rarely reliable enough against unknown targets over the Internet\. But for system administrators monitoring an internal network, they can be a practical and efficient approach\. Use the
\fB\-PE\fR
option to enable this echo request behavior\.
.sp
While echo request is the standard ICMP ping query, Nmap does not stop there\. The ICMP standard (\fIRFC 792\fR\&[2]) also specifies timestamp request, information request, and address mask request packets as codes 13, 15, and 17, respectively\. While the ostensible purpose for these queries is to learn information such as address masks and current times, they can easily be used for host discovery\. A system that replies is up and available\. Nmap does not currently implement information request packets, as they are not widely supported\. RFC 1122 insists that
\(lqa host SHOULD NOT implement these messages\(rq\. Timestamp and address mask queries can be sent with the
\fB\-PP\fR
and
\fB\-PM\fR
options, respectively\. A timestamp reply (ICMP code 14) or address mask reply (code 18) discloses that the host is available\. These two queries can be valuable when administrators specifically block echo request packets while forgetting that other ICMP queries can be used for the same purpose\.
.RE
.PP
\fB\-PO [protolist]\fR (IP Protocol Ping)
.RS 4
Another host discovery option is the IPProto ping, which sends IP packets with the specified protocol numbers in the Protocol field of the IP headers\. The protocol list takes the same format as with the port lists in the previously discussed TCP and UDP host discovery options\. If no protocols are specified, the default is to send multiple IP packets for ICMP (protocol 1), IGMP (protocol 2), and IP\-in\-IP (protocol 4)\. The default protocols can be configured at compile\-time by changing DEFAULT_PROTO_PROBE_PORT_SPEC in
\fInmap\.h\fR\. Note that for the ICMP, IGMP, TCP (protocol 6), and UDP (protocol 17), the packets are sent with the additional headers while other protocols are sent with no additional data beyond the IP header (unless the
\fB\-\-data\-length\fR
option is specified)\.
.sp
This host discovery method looks for responses in the same protocol as the probes, or ICMP Protocol Unreachable messages which signify the specified IP protocol isn\'t supported on the host (which gives away that it\'s up)\.
.RE
.PP
\fB\-PR\fR (ARP Ping)
.RS 4
One of the most common Nmap usage scenarios is to scan an ethernet LAN\. On most LANs, especially those using RFC1918\-blessed private address ranges, the vast majority of IP addresses are unused at any given time\. When Nmap tries to send a raw IP packet such as an ICMP echo request, the operating system must determine the destination hardware (ARP) address corresponding to the target IP so that it can properly address the ethernet frame\. This is often slow and problematic, since operating systems weren\'t written with the expectation that they would need to do millions of ARP requests against unavailable hosts in a short time period\.
.sp
ARP scan puts Nmap and its optimized algorithms in charge of ARP requests\. And if it gets a response back, Nmap doesn\'t even need to worry about the IP\-based ping packets since it already knows the host is up\. This makes ARP scan much faster and more reliable than IP\-based scans\. So it is done by default when scanning ethernet hosts that Nmap detects are on a local ethernet network\. Even if different ping types (such as
\fB\-PE\fR
or
\fB\-PS\fR) are specified, Nmap uses ARP instead for any of the targets which are on the same LAN\. If you absolutely don\'t want to do an ARP scan, specify
\fB\-\-send\-ip\fR\.
.RE
.PP
\fB\-\-traceroute\fR (Trace path to host)
.RS 4
Traceroutes are performed post\-scan using information from the scan results to determine the port and protocol most likely to reach the target\. It works with all scan types except connect scans (\-sT) and idle scans (\-sI)\. All traces use Nmap\'s dynamic timing model and are performed in parallel\.
.sp
Traceroute works by sending packets with a low TTL (time\-to\-live) in an attempt to elicit ICMP Time Exceeded messages from intermediate hops between the scanner and the target host\. Standard traceroute implementation start with a TTL of 1 and increment the TTL until the destination host is reached\. Nmap\'s traceroute starts with a high TTL and then decrements the TTL until it reaches 0\. Doing it backwards lets nmap employ clever caching algorithms to speed up traces over multiple hosts\. On average nmap sends 5\-10 fewer packets per host, depending on network conditions\. If a single subnet is being scanned (i\.e\. 192\.168\.0\.0/24) nmap may only have to send a single packet to most hosts\.
.RE
.PP
\fB\-\-reason\fR (Host and port state reasons)
.RS 4
Shows the reason each port is set to a specific state and the reason each host is up or down\. This option displays the type of the packet that determined a port or hosts state\. For example, A
RST
packet from a closed port or an echo reply from an alive host\. The information Nmap can provide is determined by the type of scan or ping\. The SYN scan and SYN ping (\fB\-sS\fR
and
\fB\-PT\fR) are very detailed, but the TCP connect scan and ping (\fB\-sT\fR) are limited by the implementation of the
connect
system call\. This feature is automatically enabled by the debug option (\fB\-d\fR) and the results are stored in XML log files even if this option is not specified\.
.RE
.PP
\fB\-n\fR (No DNS resolution)
.RS 4
Tells Nmap to
\fInever\fR
do reverse DNS resolution on the active IP addresses it finds\. Since DNS can be slow even with Nmap\'s built\-in parallel stub resolver, this option can slash scanning times\.
.RE
.PP
\fB\-R\fR (DNS resolution for all targets)
.RS 4
Tells Nmap to
\fIalways\fR
do reverse DNS resolution on the target IP addresses\. Normally reverse DNS is only performed against responsive (online) hosts\.
.RE
.PP
\fB\-\-system\-dns\fR (Use system DNS resolver)
.RS 4
By default, Nmap resolves IP addresses by sending queries directly to the name servers configured on your host and then listening for responses\. Many requests (often dozens) are performed in parallel to improve performance\. Specify this option to use your system resolver instead (one IP at a time via the getnameinfo() call)\. This is slower and rarely useful unless you find a bug in the Nmap parallel resolver (please let us know if you do)\. The system resolver is always used for IPv6 scans\.
.RE
.PP
\fB\-\-dns\-servers <server1[,server2],\.\.\.> \fR (Servers to use for reverse DNS queries)
.RS 4
By default Nmap will try to determine your DNS servers (for rDNS resolution) from your resolv\.conf file (Unix) or the Registry (Win32)\. Alternatively, you may use this option to specify alternate servers\. This option is not honored if you are using
\fB\-\-system\-dns\fR
or an IPv6 scan\. Using multiple DNS servers is often faster, especially if you choose authoritative servers for your target IP space\. This option can also improve stealth, as your requests can be bounced off just about any recursive DNS server on the internet\.
.sp
This option also comes in handy when scanning private networks\. Sometimes only a few name servers provide proper rDNS information, and you may not even know where they are\. You can scan the network for port 53 (perhaps with version detection), then try Nmap list scans (\fB\-sL\fR) specifying each name server one at a time with
\fB\-\-dns\-servers\fR
until you find one which works\.
.RE
.SH "PORT SCANNING BASICS"
.PP
While Nmap has grown in functionality over the years, it began as an efficient port scanner, and that remains its core function\. The simple command
\fBnmap \fR\fB\fItarget\fR\fR
scans more than 1660 TCP ports on the host
\fItarget\fR\. While many port scanners have traditionally lumped all ports into the open or closed states, Nmap is much more granular\. It divides ports into six states:
open,
closed,
filtered,
unfiltered,
open|filtered, or
closed|filtered\.
.PP