Wireshark-bugs: [Wireshark-bugs] [Bug 13078] New: No interfaces found.

Date: Mon, 31 Oct 2016 21:17:05 +0000
Bug ID 13078
Summary No interfaces found.
Product Wireshark
Version 2.2.1
Hardware x86-64
OS Windows 7
Status UNCONFIRMED
Severity Major
Priority Low
Component GTK+ UI
Assignee [email protected]
Reporter [email protected]

Created attachment 15032 [details]
Screen Capture of npf driver state and interfaces available.

Build Information:
Wireshark 2.2.1 (v2.2.1-0-ga6fbd27 from master-2.2)

Copyright 1998-2016 Gerald Combs <[email protected]> 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 Qt 5.6.1, 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, with QtMultimedia,
with AirPcap.

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.10r9), based on libpcap version 1.0 branch 1_0_rel0b (20091008), with GnuTLS
3.2.15, with Gcrypt 1.6.2, without AirPcap.
Intel(R) Core(TM) i7-4790 CPU @ 3.60GHz (with SSE4.2), with 8100MB of physical
memory.


Built using Microsoft Visual C++ 12.0 build 40629
--
No interfaces are shown in the interface list. This happens even if Wireshark
is launched with Administrator privileges. tshark doesn't detect a suitable
interface either. The npf driver is running (sc query npf output: 

SERVICE_NAME: npf 
        TYPE               : 1  KERNEL_DRIVER  
        STATE              : 4  RUNNING 
                                (STOPPABLE, NOT_PAUSABLE, IGNORES_SHUTDOWN)
        WIN32_EXIT_CODE    : 0  (0x0)
        SERVICE_EXIT_CODE  : 0  (0x0)
        CHECKPOINT         : 0x0
        WAIT_HINT          : 0x0

WinDump show interfaces that can be used to capture packets and even
successfully capture them; the results can even be opened with Wireshark and we
can see sniffed packets. (see attachment)

winpcap has been installed by the Wireshark installer. I tried running the
installer with and without administrator privileges and observe the same
behavior. 

Thanks.


You are receiving this mail because:
  • You are watching all bug changes.