Why Wireshark does not intercept the data?

Somehow Wireshark does not intercept the data? I have all the variations of adapters selected pereprobyval although it is clear what you have to choose, but it is not clear why it doesn't work.
5bbe48e390a91016704459.png5bbe4923ae019579092725.png
March 12th 20 at 08:10
1 answer
March 12th 20 at 08:12
I understand that the allocation for the first skinšote adapter is missing in the interface list in Wireshark. It depends on the library packet sniffing, but not from Wireshark. The dedicated adapter is wireless, which means his work with winpcap is not guaranteed. Probably to intercept Wi-Fi will need AirPcap.

Here is what it written by the developers of winpcap 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, other don't support promiscuous mode. In the best case, WinPcap is able to see an Ethernet emulation and not 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.
Wow, thank you! Will Google in this direction. - rene98 commented on March 12th 20 at 08:15

Find more questions by tags WiresharkWindows