The 160 MHz Capture Blind Spot
At a stadium press box, a vendor's 5 GHz network uses contiguous 160 MHz channels (36–64) with 4x4 APs and MCS 9. The analysis laptop has a 2x2 802.11ac monitor-mode adapter locked to the primary 80 MHz; the adapter supports 80 MHz but not 160 MHz. Beacons and 20 MHz management frames decode normally, but most VHT data frames are reported as PHY errors and produce no MPDU. A legacy 802.11a handheld at 6 Mbps decodes perfectly. The spectrum trace shows energy across the full 160 MHz. No other 5 GHz radios are nearby. The team must explain the pattern before buying new capture hardware. The AP's primary 20 MHz is channel 36, and the capture adapter has two receive chains.
1. Why do the 20 MHz management frames and the 6 Mbps 802.11a frames decode, while the AP's 160 MHz VHT data frames fail? Refer to the PPDU preamble and the adapter's capabilities.
Read the worked answer
For a VHT PPDU, L-SIG and VHT-SIG-A are duplicated in every 20 MHz subchannel, so a receiver tuned to the primary 80 MHz can still read the signaling fields if the primary 20 MHz is inside its capture bandwidth. That explains why the analyzer can report something about the frame. The failure happens after the SIG fields: the VHT data symbols occupy the full 160 MHz and are spatially multiplexed across four streams. An 80 MHz, 2x2 adapter captures only half the occupied bandwidth and only two of the four spatial streams, so it cannot reconstruct the data symbols. Demodulation fails before a valid MPDU/FCS is produced, which the tool reports as a PHY error. The 6 Mbps 802.11a frame is a 20 MHz, single-stream PPDU, and management frames are 20 MHz or duplicated, so both fit the adapter. The spectrum trace confirms energy outside the adapter's 80 MHz capture, which supports this diagnosis rather than a bad AP.
2. What hardware or capture configuration would reliably decode these frames, and what evidence in the PHY metadata would confirm the diagnosis?
Read the worked answer
A monitor adapter that supports 160 MHz and at least four receive chains is required, or capture with a 4x4 AP radio in monitor mode. Configure the center frequency for the 160 MHz channel, set the primary 20 MHz to 36, and explicitly set width to 160 MHz rather than 80 MHz. Confirmation comes from PHY metadata: a successful decode should show VHT, 160 MHz, MCS 9, and four spatial streams. On the current adapter, the SIG may decode as 160 MHz while the data fails; that mismatch between signaled bandwidth/spatial streams and adapter capability is the key evidence. FCS/PHY error counts should fall sharply after the change. Spectrum occupancy alone does not prove decode capability because energy can be present without a receiver being able to demodulate the data symbols.
3. If the adapter were replaced with a 160 MHz unit that still has only two receive chains, which frames would still fail and why?
Read the worked answer
Width solves the bandwidth problem but not spatial multiplexing. A 4-SS MCS 9 transmission requires four receive chains to separate the streams; a 2-chain radio can decode the robust SIG fields but cannot recover four spatial streams, so those MPDUs still fail. Frames transmitted with one or two spatial streams would decode if bandwidth and MCS are supported. The analyst should check the AP's and client's spatial-stream configuration; if most traffic is 4-SS, a 4-chain capture radio is required. Otherwise the capture will be biased toward lower-SS data frames and management frames, which can mislead troubleshooting.