PenTest/nmap
1
0
Fork 0
mirror of https://github.com/nmap/nmap.git synced 2026-01-09 16:09:03 +00:00
Code Issues Projects Releases Wiki Activity

move --reason to the output section

Browse Source
This commit is contained in:
fyodor
2008-09-21 09:40:47 +00:00
parent d231a35e21
commit 131dbdbcf0
1 changed files with 26 additions and 25 deletions
Download Patch File Download Diff File Expand all files Collapse all files

51
docs/refguide.xml
View File

@@ -780,31 +780,6 @@ Traceroutes are performed post-scan using information from the scan results to d
<para>
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 implementations 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.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>
<option>--reason</option> (Host and port state reasons)
<indexterm><primary><option>--reason</option></primary></indexterm>
</term>
<listitem>
<para>
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 <literal>RST</literal> 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 (<option>-sS</option> and <option>-PS</option>) are very detailed, but the
TCP connect scan (<option>-sT</option>) is limited by the
implementation of the <function>connect</function> system call. This feature is automatically enabled by
the debug option
(<option>-d</option>)<indexterm><primary><option>--reason</option></primary><secondary>implied by <option>-d</option></secondary></indexterm>
and the results are stored in XML log files
even if this option is not specified.
</para>
</listitem>
</varlistentry>
@@ -3408,6 +3383,32 @@ increased.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>
<option>--reason</option> (Host and port state reasons)
<indexterm><primary><option>--reason</option></primary></indexterm>
</term>
<listitem>
<para>
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 <literal>RST</literal> 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 (<option>-sS</option> and <option>-PS</option>) are very detailed, but the
TCP connect scan (<option>-sT</option>) is limited by the
implementation of the <function>connect</function> system call. This feature is automatically enabled by
the debug option
(<option>-d</option>)<indexterm><primary><option>--reason</option></primary><secondary>implied by <option>-d</option></secondary></indexterm>
and the results are stored in XML log files
even if this option is not specified.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>
<option>--packet-trace</option> (Trace packets and data sent and received)