Skip to content

Read Mesh Control field in 802.11 QoS frames - #5056

Open
TheGlitch76 wants to merge 1 commit into
secdev:masterfrom
TheGlitch76:dot11s
Open

Read Mesh Control field in 802.11 QoS frames#5056
TheGlitch76 wants to merge 1 commit into
secdev:masterfrom
TheGlitch76:dot11s

Conversation

@TheGlitch76

@TheGlitch76 TheGlitch76 commented Jul 24, 2026

Copy link
Copy Markdown

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_mesh is a little conservative, but it could always be loosened in the future.

@TheGlitch76
TheGlitch76 marked this pull request as draft July 24, 2026 22:09
@TheGlitch76
TheGlitch76 force-pushed the dot11s branch 6 times, most recently from 1256ec9 to 3bef704 Compare July 30, 2026 20:27
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
@TheGlitch76
TheGlitch76 marked this pull request as ready for review July 30, 2026 20:40
@TheGlitch76

Copy link
Copy Markdown
Author

This is ready for review now. There might be a better way to configure Dot11QoS vs Dot11MeshQoS than in Dot11's guess_payload_class (?) but this was the simplest approach that I could get to work.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant