mirror of
https://github.com/nmap/nmap.git
synced 2026-10-20 19:01:56 +00:00
Remove/change some text to describe Npcap, not WinPcap
This commit is contained in:
parent
a2690ffa45
commit
7bf0a7f016
6 changed files with 10 additions and 28 deletions
|
|
@ -724,13 +724,13 @@ support was dropped when Microsoft removed raw TCP/IP socket support
|
|||
in Windows XP SP2. Now Nmap must send lower-level ethernet frames
|
||||
instead.</para></listitem>
|
||||
|
||||
<listitem><para>When using Nmap with WinPcap instead of Npcap, you cannot
|
||||
<listitem><para>When using Nmap without Npcap, you cannot
|
||||
generally scan your own machine from itself (using a
|
||||
loopback<indexterm><primary>loopback
|
||||
interface</primary></indexterm> IP such as 127.0.0.1 or any of its
|
||||
registered IP addresses). This is a Windows limitation that we
|
||||
have worked around in Npcap, which is included in the Windows self-installer.
|
||||
Users stuck with WinPcap can use a TCP
|
||||
Users stuck without a Npcap installation can use a TCP
|
||||
connect scan without pinging (<option>-sT -Pn</option>) as that uses
|
||||
the high level socket API rather than sending raw
|
||||
packets.</para></listitem>
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue