A county NOC engineer hunting power-save behavior notices QoS Null and Null data frames are sparse or absent in a capture despite clients clearly sleeping. What analyzer limitation should the CWNE keep in mind?
Select an answer to reveal the explanation.
Short Explanation
Null frames are the client's "do not disturb" note—and some sniffers just don't hear every whisper. Empty PCAP rows aren't proof the handheld never sent them. Know your adapter's blind spots before blaming the STA.
Full Explanation
Null data and QoS Null frames commonly signal power-save state changes but are easy to under-capture depending on sniffer PHY support, filters, driver offloads, and monitor-mode limitations. Expert protocol analysis treats sparse Null visibility as a possible instrumentation limit rather than conclusive evidence that power-save signaling never occurred. Corroborate with TIM/DTIM behavior, PS-Poll/uAPSD patterns, and multi-tool captures when power-save troubleshooting matters.