Question 190
A Wi-Fi 6 laboratory shows a downlink transmission occupying scheduled subcarriers for multiple stations, yet a legacy analyzer labels it one generic data burst. Which continued monitoring approach matches the original problem?
Explanation
Correct Answer
Track missing RU metadata, unsupported HE/EHT PPDU formats and disagreement between trigger indications and decoder output. This addresses the decisive observation: A Wi-Fi 6 laboratory shows a downlink transmission occupying scheduled subcarriers for multiple stations, yet a legacy analyzer labels it one generic data burst.
Incorrect Answers
The option would address: Trend unsupported PPDU decodes, PHY synchronization failures, training-field visibility and frame-decode fallbacks. The scenario instead reports: A Wi-Fi 6 laboratory shows a downlink transmission occupying scheduled subcarriers for multiple stations, yet a legacy analyzer labels it one generic data burst. The decisive distinction is: Track missing RU metadata, unsupported HE/EHT PPDU formats and disagreement between trigger indications and decoder output.
This alternative addresses a different issue (radiotap metadata not part of transmitted MAC bytes). Monitor inconsistent pseudo-header format, absent receiver channel fields, and decoder assumptions across capture adapters. In the reported case: A Wi-Fi 6 laboratory shows a downlink transmission occupying scheduled subcarriers for multiple stations, yet a legacy analyzer labels it one generic data burst.
Monitor missing width or GI metadata, rate-calculation mismatches and PHY rate versus payload-goodput differences. The observed condition is: A Wi-Fi 6 laboratory shows a downlink transmission occupying scheduled subcarriers for multiple stations, yet a legacy analyzer labels it one generic data burst. This alternative addresses a different issue (guard interval and MCS context). The decisive distinction is: Track missing RU metadata, unsupported HE/EHT PPDU formats and disagreement between trigger indications and decoder output.