You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
C:\Windows\System32\Npcap>WlanHelper.exe 8c309594-364d-425a-98f7-7ba157b84aa6 modu ht
Success
C:\Windows\System32\Npcap>WlanHelper.exe 8c309594-364d-425a-98f7-7ba157b84aa6 modu
ht
C:\Windows\System32\Npcap>WlanHelper.exe 8c309594-364d-425a-98f7-7ba157b84aa6 channel 36+40
Error: makeOIDRequest::My_PacketRequest error, NTSTATUS error code = 0xc0232002 (Langaton lõhiverkkoliittymõ on suljettu, joten se ei tue pyydettyõ toimintoa)
Failure
C:\Windows\System32\Npcap>WlanHelper.exe 8c309594-364d-425a-98f7-7ba157b84aa6 channel 36
Error: makeOIDRequest::My_PacketRequest error, NTSTATUS error code = 0xc0232002 (Langaton lõhiverkkoliittymõ on suljettu, joten se ei tue pyydettyõ toimintoa)
Failure
Ht or irbaseband I get this error when using freq.
C:\Windows\System32\Npcap>WlanHelper.exe 8c309594-364d-425a-98f7-7ba157b84aa6 freq
Error: makeOIDRequest::My_PacketRequest error, NTSTATUS error code = 0xc0010015 (The data supplied at InformationBuffer in the given NDIS_OID_REQUEST structure is invalid for the given OID_XXX code.)
Failure
The text was updated successfully, but these errors were encountered:
My knowledge about 802.11 is still very limited. But you set the channel to 36+40 is surely wrong, because inside WlanHelper.exe, it accepts a int as the channel. So 36+40 won't be valid. What does 36+40 mean? two channels?
Does Microsoft even support 802.11ac with the "Native WiFi" stuff Npcap uses for raw capture? Microsoft are deprecating "Native WiFi", so the ability to capture in monitor mode at all may not stay around forever.
Does Npcap support 40 and 80 MHz wide channels?
I'm testing my Netgear A6200 (Broadcom BCM43526).
Seems that VHT/802.11ac is not supported but HT/802.11n is.
I'm trying to use channels 36+40 (40 MHz).
I also tested this way.
Ht or irbaseband I get this error when using freq.
The text was updated successfully, but these errors were encountered: