nmap / nmap/npcap

wlanhelper reports success on channel change but does not change channel

Open
#533 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C
Stars
3.6k
Forks
592
PR merge metrics
No merged PRs in 30d

Description

First of all, thank you for all the work on npcap! I'm using it to make nzyme work on Windows.

The wlanhelper utility does not throw any errors but also does not seem to actually perform the task:

PS C:\Users\lenna\workspace\nzyme> wlanhelper 422E8224-31DB-45E9-980E-A690DAA84B23 mode
monitor
PS C:\Users\lenna\workspace\nzyme> wlanhelper 422E8224-31DB-45E9-980E-A690DAA84B23 channel
1
PS C:\Users\lenna\workspace\nzyme> wlanhelper 422E8224-31DB-45E9-980E-A690DAA84B23 channel 11
Success
PS C:\Users\lenna\workspace\nzyme> wlanhelper 422E8224-31DB-45E9-980E-A690DAA84B23 channel
1

To make sure, I've tried this with normal privileges as well as Administrator privileges. Same result.

Here are the WiFi adapters that I tested (they all support monitor mode really well on Linux) and they all show the exact same behavior on two Windows machines:

  • ALFA AWUS036NH
  • Panda PAU05
  • Panda PAU07

Windows version: 10 (Build 19043)
npcap version: 1.50

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start at the wlanhelper channel command and reproduce the reported sequence on Windows with one of the listed adapters. Trace how the requested channel is applied and how the follow-up query reads it. Done means the command changes the channel, or reports a clear failure instead of printing success when the channel remains unchanged.

Written by the indexing model from the issue text.

Assessment

Tech stack
c
Domain
cli, networking
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.