[bugzilla-daemon@xxxxxxxxxxxxx]

Jasey changed bug 13078

What	Removed	Added
CC		jrdepriest@gmail.com

Comment # 2 on bug 13078 from Jasey

I have had this same issue with the 2.2 line. If I run any version of 2.0,
interfaces are found. Any version of 2.2 shows no interfaces.

tshark version information:
TShark (Wireshark) 2.2.3 (v2.2.3-0-g57531cd)

Copyright 1998-2016 Gerald Combs <gerald@wireshark.org> and contributors.
License GPLv2+: GNU GPL version 2 or later
<http://www.gnu.org/licenses/old-licenses/gpl-2.0.html>
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

Compiled (64-bit) with WinPcap (4_1_3), with GLib 2.42.0, with zlib 1.2.8, with
SMI 0.4.8, with c-ares 1.12.0, with Lua 5.2.4, with GnuTLS 3.2.15, with Gcrypt
1.6.2, with MIT Kerberos, with GeoIP.

Running on 64-bit Windows 7 Service Pack 1, build 7601, with locale
English_United States.1252, with WinPcap version 4.1.3 (packet.dll version
0.07), based on libpcap version 1.0 branch 1_0_rel0b (20091008), with GnuTLS
3.2.15, with Gcrypt 1.6.2.
       Intel(R) Core(TM) i5-3320M CPU @ 2.60GHz (with SSE4.2), with 7889MB of
physical memory.

tshark finds no interfaces
C:\>tshark -D
tshark: There are no interfaces on which a capture can be done

windump has no problem
C:\>\tools\windump\WinDump.exe -D
1.\Device\NPF_{0CABC01D-E1A9-4434-AD94-4A8D8848E221} (Microsoft)
2.\Device\NPF_{CA8C5243-D0D0-44EF-8E8C-4FDDA9E10754} (Microsoft)
3.\Device\NPF_{24BD1B2E-03E2-4326-9360-D5B2CA3CA19D} (Microsoft)
4.\Device\NPF_{72B8E320-0DF4-468E-9B56-B9C51C49EC48} (Cisco AnyConnect VPN
Virtual Miniport Adapter for Windows x64)
5.\Device\NPF_{985F2846-4B63-4E2D-8F31-9A506F06AD32} (Microsoft)
6.\Device\NPF_{B01705B2-EB0C-4CF8-9B58-E848CE8D50FB} (Intel(R) 82579LM Gigabit
Network Connection)

I did have npcap installed from nmap. I uninstalled it, reinstalled Wireshark,
including a reinstall of winpcap, then rebooted and I still have the same
issue.

What's strange is that tshark shows this
WinPcap version 4.1.3 (packet.dll version 0.07), based on libpcap version 1.0
branch 1_0_rel0b (20091008)
But windump shows this
WinPcap version 4.1.3 (packet.dll version 4.1.0.2980), based on libpcap version
1.0 branch 1_0_rel0b (20091008)

If that is still npcap messing things up, then I guess I need to start bugging
the nmap dev list.

The NPF driver that is actually running is npf.sys with version 4.1.0.2980,
name WinPcap, by Riverbed Technologies.

I can't see evidence of npcap running or even present on my system.

---

      You are receiving this mail because:

• You are watching all bug changes.