osmith
/
wireshark
forked from osmocom/wireshark
1
0
Fork 0
Code Pull Requests Releases Wiki Activity

Update docs for WinPcap to Npcap switch 

Change-Id: I23287165c3aaf11327a3320282fa9eebe23e2a22
Reviewed-on: https://code.wireshark.org/review/32616
Petri-Dish: Anders Broman <a.broman58@gmail.com>
Tested-by: Petri Dish Buildbot
Reviewed-by: Anders Broman <a.broman58@gmail.com>
This commit is contained in:
Moshe Kaplan 2019-03-28 21:06:23 -04:00 committed by Anders Broman
parent 8eabc748cf
commit 2cb8bed2e4
5 changed files with 34 additions and 35 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
docbook/faq.adoc
View File

@ -735,7 +735,7 @@ problem with one or more of:
* the operating system you're using;
* the device driver for the interface you're using;
* the WinPcap library and/or the WinPcap device driver;
* the Npcap library and/or the Npcap device driver;
so first check https://nmap.org/npcap/guide/[the Npcap User's Guide] to
see if your problem is mentioned there. If not, then see
@ -770,7 +770,7 @@ Reports, Questions, Suggestions, etc" section.
You may also want to ask the
mailto:wireshark-users@wireshark.org[wireshark-users@wireshark.org] and
the mailto:winpcap-users@winpcap.org[winpcap-users@winpcap.org] mailing
the mailto:dev@nmap.org[dev@nmap.org] mailing
lists to see if anybody happens to know about the problem and know a
workaround or fix for the problem. (Note that you will have to subscribe
to that list in order to be allowed to mail to it; see

2
docbook/wsug_src/WSUG_app_howitworks.adoc
View File

@ -23,7 +23,7 @@ When Wireshark starts, a lot of things are done:
* Load and set the disabled protocols from the disabled_protos file
* Init libpcap/winpcap (the capturing engine)
* Init libpcap/Npcap (the capturing engine)
* Process command line parameters

6
docbook/wsug_src/WSUG_chapter_advanced.adoc
View File

@ -566,7 +566,7 @@ time stamps will be saved to the capture file, so they also will be available
for (later) analysis.
So where do these time stamps come from? While capturing, Wireshark gets the
time stamps from the libpcap (WinPcap) library, which in turn gets them from the
time stamps from the libpcap (Npcap) library, which in turn gets them from the
operating system kernel. If the capture data is loaded from a capture file,
Wireshark obviously gets the data from that file.
@ -581,7 +581,7 @@ packet list, see the “Time Display Format” item in the
While reading or writing capture files, Wireshark converts the time stamp data
between the capture file format and the internal format as required.
While capturing, Wireshark uses the libpcap (WinPcap) capture library which
While capturing, Wireshark uses the libpcap (Npcap) capture library which
supports microsecond resolution. Unless you are working with specialized
capturing hardware, this resolution should be adequate.
@ -736,7 +736,7 @@ formats, save the arrival time of packets as UTC values. UN*X systems, and
“Windows NT based” systems represent time internally as UTC. When Wireshark is
capturing, no conversion is necessary. However, if the system time zone is not
set correctly, the system’s UTC time might not be correctly set even if the
system clock appears to display correct local time. When capturing, WinPcap has
system clock appears to display correct local time. When capturing, Npcap has
to convert the time to UTC before supplying it to Wireshark. If the system’s
time zone is not set correctly, that conversion will not be done correctly.

55
docbook/wsug_src/WSUG_chapter_build_install.adoc
View File

@ -63,7 +63,7 @@ Once you have downloaded the relevant files, you can go on to the next step.
Windows installer names contain the platform and version. For example,
Wireshark-win64-{wireshark-version}.exe installs Wireshark {wireshark-version}
for 64-bit Windows. The Wireshark installer includes WinPcap which is required
for 64-bit Windows. The Wireshark installer includes Npcap which is required
for packet capture.
Simply download the Wireshark installer from {wireshark-download-url}
@ -134,19 +134,19 @@ By default Wireshark installs into `%ProgramFiles%\Wireshark` on 32-bit Windows
and `%ProgramFiles64%\Wireshark` on 64-bit Windows. This expands to `C:\Program
Files\Wireshark` on most systems.
[[ChBuildInstallWinPcap]]
[[ChBuildInstallNpcap]]
==== Installing WinPcap
==== Installing Npcap
The Wireshark installer contains the latest WinPcap installer.
The Wireshark installer contains the latest Npcap installer.
If you don’t have WinPcap installed you won’t be able to capture live network
If you don’t have Npcap installed you won’t be able to capture live network
traffic but you will still be able to open saved capture files. By default the
latest version of WinPcap will be installed. If you don’t wish to do this or if
you wish to reinstall WinPcap you can check the _Install WinPcap_ box as needed.
latest version of Npcap will be installed. If you don’t wish to do this or if
you wish to reinstall Npcap you can check the _Install Npcap_ box as needed.
For more information about WinPcap see {winpcap-main-url} and
{wireshark-wiki-url}WinPcap.
For more information about Npcap see {npcap-main-url} and
{wireshark-wiki-url}Npcap.
[[ChBuildInstallWinWiresharkCommandLine]]
@ -156,7 +156,7 @@ For more information about WinPcap see {winpcap-main-url} and
For special cases, there are some command line parameters available:
* `/S` runs the installer or uninstaller silently with default values. The
silent installer *will not* install WinPCap.
silent installer *will not* install Npcap.
* `/desktopicon` installation of the desktop icon, `=yes` - force installation,
`=no` - don’t install, otherwise use default settings. This option can be
@ -178,17 +178,17 @@ Example:
Running the installer without any parameters shows the normal interactive installer.
[[ChBuildInstallWinPcapManually]]
[[ChBuildInstallNpcapManually]]
==== Manual WinPcap Installation
==== Manual Npcap Installation
As mentioned above, the Wireshark installer takes care of installing WinPcap.
As mentioned above, the Wireshark installer takes care of installing Npcap.
The following is only necessary if you want to use a different version than the
one included in the Wireshark installer, e.g. because a new WinPcap version was
one included in the Wireshark installer, e.g. because a new Npcap version was
released.
Additional WinPcap versions (including newer alpha or beta releases) can
be downloaded from the main WinPcap site at {winpcap-main-url}. The
Additional Npcap versions (including newer alpha or beta releases) can
be downloaded from the main Npcap site at {npcap-main-url}. The
_Installer for Windows_ supports modern Windows operating systems.
[[ChBuildInstallWinWiresharkUpdate]]
@ -206,14 +206,13 @@ Wireshark is done the same way as installing it. Simply download and start the
installer exe. A reboot is usually not required and all your personal settings
remain unchanged.
[[ChBuildInstallWinPcapUpdate]]
[[ChBuildInstallNpcapUpdate]]
==== Update WinPcap
==== Update Npcap
New versions of WinPcap are less frequently available. You will find
WinPcap update instructions the WinPcap web site at {winpcap-main-url}.
You may have to reboot your machine after installing a new WinPcap
version.
New versions of Npcap. You will find Npcap update instructions the Npcap web
site at {npcap-main-url}. You may have to reboot your machine after installing
a new Npcap version.
[[ChBuildInstallWinUninstall]]
@ -223,16 +222,16 @@ You can uninstall Wireshark using the _Programs and Features_ control panel.
Select the “Wireshark” entry to start the uninstallation procedure.
The Wireshark uninstaller provides several options for removal. The default is
to remove the core components but keep your personal settings and WinPcap.
WinPcap is left installed by default in case other programs need it.
to remove the core components but keep your personal settings.
Npcap is left installed by default in case other programs need it.
[[ChBuildInstallWinPcapUninstall]]
[[ChBuildInstallNpcapUninstall]]
==== Uninstall WinPcap
==== Uninstall Npcap
You can uninstall WinPcap independently of Wireshark using the _WinPcap_ entry
You can uninstall Npcap independently of Wireshark using the _Npcap_ entry
in the _Programs and Features_ control panel. Remember that if you uninstall
WinPcap you won’t be able to capture anything with Wireshark.
Npcap you won’t be able to capture anything with Wireshark.
//
// macOS

2
docbook/wsug_src/WSUG_chapter_capture.adoc
View File

@ -533,7 +533,7 @@ you can achieve the same effect (securely) through an SSH tunnel.
The Remote Packet Capture Protocol service must first be running on the
target platform before Wireshark can connect to it. The easiest way is
to install WinPcap from {winpcap-download-url} on the target. Once
to install Npcap from {npcap-download-url} on the target. Once
installation is completed go to the Services control panel, find the
Remote Packet Capture Protocol service and start it.