Skip to content
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 #1528

guyharris opened this Issue Mar 26, 2019 · 2 comments


None yet
2 participants
Copy link

guyharris commented Mar 26, 2019

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 question.


This comment has been minimized.

Copy link

dmiller-nmap commented Mar 28, 2019

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:

  1. The hardware may not make some information available to the driver.
  2. The driver may not make the information available to higher layers.
  3. The driver may use a different API (WDI, Native 802.11, etc.) than we expect to make the information available.
  4. The driver may provide incorrect information (zero, uninitialized, stale, etc) to higher layers.

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.


This comment has been minimized.

Copy link

guyharris commented Apr 5, 2019

Raw WiFi capture support is problematic right now for a few reasons

It appears to be even more problematic with WDI. To quote "Features not carried over in WDI":

The following features are available in the previous Native WLAN driver model, but are not available in WDI.


  • Netmon
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.