Check whether MediaSpecificInformationEx contains 802.11 frame/phy data
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 3.6k
- Forks
- 592
- PR merge metrics
- No merged PRs in 30d
Description
As mentioned in https://github.com/nmap/npcap/issues/167#issuecomment-633380891, the MediaSpecificInformation tag for NBLs is marked obsolete, which is where we look to get raw WiFi information. We need to do some kernel debugging with the latest version of Npcap to see what other places this information might be reported. A promising one is the MediaSpecificInformationEx tag, which is very similar but allows a linked list of informational items.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the context in npcap issue 167 and review how raw WiFi information is obtained from the obsolete MediaSpecificInformation tag. Use the latest Npcap version for kernel debugging, then investigate whether MediaSpecificInformationEx and its linked informational items expose the 802.11 frame or PHY data. Done means documenting where the data is reported and whether that path can replace the obsolete tag.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- networking, operating-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100