Answer the question
In order to leave comments, you need to log in
Answer the question
In order to leave comments, you need to log in
I understand that the adapter highlighted in the first screenshot is not in the list of interfaces in Wireshark. This depends on the packet capture library, not Wireshark. The dedicated adapter is wireless and therefore not guaranteed to work with winpcap. It will probably require AirPcap to intercept wifi.
Here is what the winpcap developers write about this in the FAQ:
Q-16: Which network adapters are supported by WinPcap?
A: The WinPcap device driver was developed to work primarily with Ethernet (10/100/1000) adapters. Support for other MACs was added during the development, but Ethernet remains the most tested one.
...
Wireless adapters: these adapters may present problems, because they are not properly supported by the Windows Kernel. Some of them are not detected, others don't support promiscuous mode. In the best case, WinPcap is able to an Ethernet emulation and not see the real transiting packets: this means that the 802.11 frames are transformed into fake Ethernet frames before being captured, and that control frames are not received.
For real wireless capture, CACE Technologies offers the AirPcap adapter, specifically designed to sniff 802.11 traffic, including control frames, management frames and power information. AirPcap at this time is the only solution for capturing raw 802.11 traffic with WinPcap. More details can be found on the AirPcap product page.
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question