Conversation
The radiotap parser read the TSFT field without applying the spec's 8-byte alignment. With extended present-words (EXT bit set, e.g. on ath9k_htc), the field chain shifts by 4 bytes and the channel field reads 0, causing every frame to bail with 'bad reported frequency' and no 802.11 data to be recorded.
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
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.
Fixes #1498
What
Add the radiotap-spec-required 8-byte alignment before the TSFT field in
tap/src/protocols/parsers/dot11/dot11_header_parser.rs. When the present-flags word carries the EXT bit (e.g.ath9k_htcemits two present words), the field area starts at a 4-byte-misaligned offset; without the alignment, the channel field is read 4 bytes early and lands on0x0000, tripping thefrequency == 0bail — discarding every frame.Why
See #1498 for full detail. Symptom: a tap only ever records the single strongest AP while raw
tcpdumpon the same interface sees dozens; deauth/disconnect timeline events never fire because frames never make it past the header parser.Verification
Tested with a USB Atheros AR9271 (
ath9k_htc) tap on Ubuntu, pinned channel: