Capture
CLIENT STA list
Select a CLIENT STA to inspect its flow and capability profile.
| CLIENT STA | Frames | Data | Retries | Retry % | First | Last |
|---|
CLIENT STA
Capability profile
What the CLIENT STA advertises in its (re)association request, and what it actually did on air.
Inside the data frames
Which higher-layer protocols the dissector could see, and how much of the payload is encrypted. Absence of a protocol only means something when there is enough cleartext to have seen it.
Received signal
The level at which the capture point heard each frame, split by direction because they measure different things. STA → AP is the CLIENT STA as the sniffer hears it, on an AP-side capture that is a good stand-in for what the AP hears. AP → STA is the AP at the sniffer and says little about what the client experiences.
Roaming
Data rate & MCS
The rate the data frames were actually sent at, over time and per MCS. A high retry share on the low rates is rate-shifting under stress: the CLIENT STA drops its MCS because frames are not getting through.
Acknowledgement timing
Time between a frame and the ACK/BlockAck that confirms it. SIFS is 10 µs on 2.4 GHz and 16 µs on 5/6 GHz, so anything up to roughly 30 µs is normal. A long tail means something got in the way: a retry, a busy channel, or a station that is far away or slow to answer.
Throughput of this CLIENT STA
Flow
| Frame | Time (s) | Δ | Transmitter → Receiver | DS | Frame type | Rate | MCS | Notes |
|---|
Channel Health
This covers every transmitter in the capture, not just the selected CLIENT STA, channel utilisation is what a CLIENT STA actually competes with.