aboutsummaryrefslogtreecommitdiffstats
path: root/wspcap.h
diff options
context:
space:
mode:
authorGuy Harris <guy@alum.mit.edu>2020-03-12 17:12:46 -0700
committerGuy Harris <guy@alum.mit.edu>2020-03-13 00:13:31 +0000
commitcd3af470b8eff89320509e36b61141b7f9a88c0b (patch)
tree4c005c4fbd512c263d90bf41dd7dca4aa71c5117 /wspcap.h
parentd73c0be3bf8d65189acffa6d32d6f2e5804942f2 (diff)
Update comments - Npcap no longer requires HAVE_REMOTE to be defined.
Change-Id: Ib9bda84907de4171376cf0fe29b6fdd4b58fd695 Reviewed-on: https://code.wireshark.org/review/36385 Reviewed-by: Guy Harris <guy@alum.mit.edu>
Diffstat (limited to 'wspcap.h')
-rw-r--r--wspcap.h14
1 files changed, 6 insertions, 8 deletions
diff --git a/wspcap.h b/wspcap.h
index 2a8c0fb92b..54d34633cb 100644
--- a/wspcap.h
+++ b/wspcap.h
@@ -1,13 +1,13 @@
/* wspcap.h
*
- * Wrapper around libpcap/WinPcap/Npcap's pcap.h.
+ * Wrapper around libpcap/WinPcap's pcap.h.
*
- * If HAVE_PCAP_REMOTE is defined, it forces the WinPcap/Npcap header files to
+ * If HAVE_PCAP_REMOTE is defined, it forces the WinPcap header files to
* define things required for remote capture, by defining HAVE_REMOTE.
*
- * With current versions of the WinPcap or Npcap SDK, if:
+ * With all versions of the WinPcap SDK, if:
*
- * 1) you are building with any current WinPcap or Npcap SDK;
+ * 1) you are building with any current WinPcap SDK;
* 2) you do not define HAVE_REMOTE before including pcap.h (or
* pcap/pcap.h);
* 3) you define a struct pcap_stat and pass it to a call to
@@ -43,10 +43,8 @@
* will make no difference).
*
* No version of the WinPcap SDK provided libpcap 1.9.0-or-later headers.
- * The Npcap SDK, as of SDK version 1.01, does not provide libpcap 1.9.0-
- * or-later headers, even though newer versions of Npcap are based on
- * with remote capture support will not have this problem. Newer versions
- * libpcap 1.9.0; an issue has been filed against Npcap for that.
+ * The Npcap SDK, as of SDK version 1.04, provides them, so this is
+ * only necessary for building with the WinPcap SDK.
*
* Wireshark - Network traffic analyzer
* By Gerald Combs <gerald@wireshark.org>