forked from osmocom/wireshark
Docs: Mention Npcap in our man pages.
Mention Npcap whereever we mention WinPcap. Change-Id: I6ee295ca88302e2516d5658a5d528f9675209da8 Reviewed-on: https://code.wireshark.org/review/32352 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:
parent
b08003309b
commit
7fbee2640c
|
@ -48,7 +48,7 @@ default capture file format is B<pcapng> format.
|
||||||
When the B<-P> option is specified, the output file is written in the
|
When the B<-P> option is specified, the output file is written in the
|
||||||
B<pcap> format.
|
B<pcap> format.
|
||||||
|
|
||||||
Without any options set it will use the libpcap/WinPcap library to
|
Without any options set it will use the libpcap, Npcap, or WinPcap library to
|
||||||
capture traffic from the first available network interface and writes
|
capture traffic from the first available network interface and writes
|
||||||
the received raw packet data, along with the packets' time stamps into a
|
the received raw packet data, along with the packets' time stamps into a
|
||||||
pcap file.
|
pcap file.
|
||||||
|
|
|
@ -55,7 +55,7 @@ file on disk.
|
||||||
|
|
||||||
If B<-p> is supplied B<rawshark> expects the following format. This
|
If B<-p> is supplied B<rawshark> expects the following format. This
|
||||||
matches the I<struct pcap_pkthdr> structure and packet data used in
|
matches the I<struct pcap_pkthdr> structure and packet data used in
|
||||||
libpcap/WinPcap. This structure's format is platform-dependent; the
|
libpcap, Npcap, or WinPcap. This structure's format is platform-dependent; the
|
||||||
size of the I<tv_sec> field in the I<struct timeval> structure could be
|
size of the I<tv_sec> field in the I<struct timeval> structure could be
|
||||||
32 bits or 64 bits. For B<rawshark> to work, the layout of the
|
32 bits or 64 bits. For B<rawshark> to work, the layout of the
|
||||||
structure in the input must match the layout of the structure in
|
structure in the input must match the layout of the structure in
|
||||||
|
@ -111,13 +111,13 @@ Specify how the packet data should be dissected. The encapsulation is of the
|
||||||
form I<type>B<:>I<value>, where I<type> is one of:
|
form I<type>B<:>I<value>, where I<type> is one of:
|
||||||
|
|
||||||
B<encap>:I<name> Packet data should be dissected using the
|
B<encap>:I<name> Packet data should be dissected using the
|
||||||
libpcap/WinPcap data link type (DLT) I<name>, e.g. B<encap:EN10MB> for
|
libpcap/Npcap/WinPcap data link type (DLT) I<name>, e.g. B<encap:EN10MB> for
|
||||||
Ethernet. Names are converted using pcap_datalink_name_to_val().
|
Ethernet. Names are converted using pcap_datalink_name_to_val().
|
||||||
A complete list of DLTs can be found at
|
A complete list of DLTs can be found at
|
||||||
L<http://www.tcpdump.org/linktypes.html>.
|
L<http://www.tcpdump.org/linktypes.html>.
|
||||||
|
|
||||||
B<encap>:I<number> Packet data should be dissected using the
|
B<encap>:I<number> Packet data should be dissected using the
|
||||||
libpcap/WinPcap LINKTYPE_ I<number>, e.g. B<encap:105> for raw IEEE
|
libpcap/Npcap/WinPcap LINKTYPE_ I<number>, e.g. B<encap:105> for raw IEEE
|
||||||
802.11 or B<encap:101> for raw IP.
|
802.11 or B<encap:101> for raw IP.
|
||||||
|
|
||||||
B<proto>:I<protocol> Packet data should be passed to the specified Wireshark
|
B<proto>:I<protocol> Packet data should be passed to the specified Wireshark
|
||||||
|
@ -353,8 +353,8 @@ whitespace. The same directory as for the personal preferences file is
|
||||||
used.
|
used.
|
||||||
|
|
||||||
Capture filter name resolution is handled by libpcap on UNIX-compatible
|
Capture filter name resolution is handled by libpcap on UNIX-compatible
|
||||||
systems and WinPcap on Windows. As such the Wireshark personal F<hosts> file
|
systems and Npcap or WinPcap on Windows. As such the Wireshark personal
|
||||||
will not be consulted for capture filter name resolution.
|
F<hosts> file will not be consulted for capture filter name resolution.
|
||||||
|
|
||||||
=item Name Resolution (subnets)
|
=item Name Resolution (subnets)
|
||||||
|
|
||||||
|
@ -400,8 +400,8 @@ The personal F<ethers> file is looked for in the same directory as the personal
|
||||||
preferences file.
|
preferences file.
|
||||||
|
|
||||||
Capture filter name resolution is handled by libpcap on UNIX-compatible
|
Capture filter name resolution is handled by libpcap on UNIX-compatible
|
||||||
systems and WinPcap on Windows. As such the Wireshark personal F<ethers> file
|
systems and Npcap or WinPcap on Windows. As such the Wireshark personal
|
||||||
will not be consulted for capture filter name resolution.
|
F<ethers> file will not be consulted for capture filter name resolution.
|
||||||
|
|
||||||
=item Name Resolution (manuf)
|
=item Name Resolution (manuf)
|
||||||
|
|
||||||
|
|
|
@ -1874,8 +1874,8 @@ whitespace. The same directory as for the personal preferences file is
|
||||||
used.
|
used.
|
||||||
|
|
||||||
Capture filter name resolution is handled by libpcap on UNIX-compatible
|
Capture filter name resolution is handled by libpcap on UNIX-compatible
|
||||||
systems and WinPcap on Windows. As such the Wireshark personal F<hosts> file
|
systems and Npcap or WinPcap on Windows. As such the Wireshark personal
|
||||||
will not be consulted for capture filter name resolution.
|
F<hosts> file will not be consulted for capture filter name resolution.
|
||||||
|
|
||||||
=item Name Resolution (subnets)
|
=item Name Resolution (subnets)
|
||||||
|
|
||||||
|
@ -1921,8 +1921,8 @@ The personal F<ethers> file is looked for in the same directory as the personal
|
||||||
preferences file.
|
preferences file.
|
||||||
|
|
||||||
Capture filter name resolution is handled by libpcap on UNIX-compatible
|
Capture filter name resolution is handled by libpcap on UNIX-compatible
|
||||||
systems and WinPcap on Windows. As such the Wireshark personal F<ethers> file
|
systems and Npcap or WinPcap on Windows. As such the Wireshark personal
|
||||||
will not be consulted for capture filter name resolution.
|
F<ethers> file will not be consulted for capture filter name resolution.
|
||||||
|
|
||||||
=item Name Resolution (manuf)
|
=item Name Resolution (manuf)
|
||||||
|
|
||||||
|
|
|
@ -71,7 +71,7 @@ B<Wireshark> can read / import the following file formats:
|
||||||
|
|
||||||
=item *
|
=item *
|
||||||
pcap - captures from B<Wireshark>/B<TShark>/B<dumpcap>, B<tcpdump>,
|
pcap - captures from B<Wireshark>/B<TShark>/B<dumpcap>, B<tcpdump>,
|
||||||
and various other tools using libpcap's/WinPcap's/tcpdump's/WinDump's
|
and various other tools using libpcap's/Npcap's/WinPcap's/tcpdump's/WinDump's
|
||||||
capture format
|
capture format
|
||||||
|
|
||||||
=item *
|
=item *
|
||||||
|
|
Loading…
Reference in New Issue