Some 802.11 drivers don't appear to provide an FCS, but Npcap sets the IEEE80211_RADIOTAP_F_FCS flag anyway
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 3.6k
- Forks
- 592
- PR merge metrics
- No merged PRs in 30d
Description
See Wireshark bug 15010 for details. It appears that a Netgear A6210 adapter, with Netgear driver v1.0.0.39, doesn't supply an FCS at the end of the packet for raw 802.11 packets.
In UN*X, drivers generally supply the radiotap header themselves, so the driver can set the IEEE80211_RADIOTAP_F_FCS flag if and only if the FCS is present.
Unfortunately, the Windows interface for 802.11 adapters may not allow Npcap to determine this, so this might require a quirks list in Npcap.
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 linked Wireshark bug and the Npcap Windows 802.11 capture path; no source file or test is named in the issue. Determine how the Netgear A6210 driver exposes FCS information and whether a quirks list is needed, then verify that IEEE80211_RADIOTAP_F_FCS is set only when an FCS is present.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100