New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Npcap should perhaps not report a zero RSSI value #64
Comments
Raw WiFi capture support is problematic right now for a few reasons, but I'm hopeful we'll be able to improve things. First, Npcap makes use of the Native 802.11 Wireless API which is deprecated in Windows 10. Newer drivers will be using the WLAN Device Driver Interface (WDI), and I haven't figured out how a NDIS filter driver like ours would be able to get similar information for packets under that API. Also, support is dependent on the device driver delivering accurate information. This can break down a number of ways:
The change I just pushed ought to prevent us from interpreting uninitialized or zeroed memory as out-of-band media-specific information, but there's no guarantees that the underlying drivers are behaving correctly. |
It appears to be even more problematic with WDI. To quote "Features not carried over in WDI":
...
|
I've asked about this on https://github.com/MicrosoftDocs/windows-driver-docs/issues/1476, and they answered that they will look into it. Feel free to add any additional concerns/infos, or ping the thread. Edit:
It looks worse than what I expected :/ |
It appears that, for some devices, the signal strength is reported as 0 dBm; this probably means that the device doesn't report the signal strength, not that the signal strength was 1 milliwatt.
See, for example, this ask.wireshark.org question.
The text was updated successfully, but these errors were encountered: