Read Mesh Control field in 802.11 QoS frames#5056
Draft
TheGlitch76 wants to merge 1 commit into
Draft
Conversation
TheGlitch76
marked this pull request as draft
July 24, 2026 22:09
Data frames on an 802.11s mesh contain a variable length mesh control field which must be consumed by scapy to get to the rest of the packet. AI-Assisted: no
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Data frames on an 802.11s mesh contain a variable length mesh control field which must be consumed by scapy to get to the rest of the packet.
AI-Assisted: no
Description
This is the bare minimum to get Data frames sniffed from a mesh network to parse correctly. Note that all Data frames on an 802.11s mesh are QoS frames. The heuristic in
_dot11qos_is_meshis a little conservative, but it could be loosened later if someone finds traffic using the reserved bits in the wild.The only issue I'm aware of is that the Dot11 class will incorrectly label addr 1 thru 4 (for example, calling address 4 the BSSID). I'm not sure how to approach fixing that.I am working on this now, I hope to get it done this weekend.