Retry

Set when this frame is a retransmission.

Reading a capture

A capture full of Retry frames is the single clearest sign of a problem, but it does not say whether the original was lost on the way out or the acknowledgement was lost on the way back.

Where it sits

QoS Data MPDU > Frame Control > Retry

• Open in the explorer — Ack
• Open in the explorer — TCP over IPv4, in a protected QoS Data frame, aggregated
• Open in the explorer — Association Request
• Open in the explorer — Association Response
• Open in the explorer — Beacon
• Open in the explorer — Compressed Block Ack
• Open in the explorer — CTS
• Open in the explorer — Four-way handshake message 1
• Open in the explorer — Four-way handshake message 2
• Open in the explorer — Four-way handshake message 3
• Open in the explorer — Four-way handshake message 4
• Open in the explorer — Probe Request
• Open in the explorer — Probe Response
• Open in the explorer — ARP request in a QoS Data frame
• Open in the explorer — ICMP echo over IPv4, in a QoS Data frame
• Open in the explorer — UDP over IPv6, in a QoS Data frame
• Open in the explorer — TCP over IPv4, in a protected QoS Data frame
• Open in the explorer — TCP over IPv4, in an open QoS Data frame
• Open in the explorer — UDP over IPv4, in a QoS Data frame
• Open in the explorer — RTS
• Open in the explorer — Trigger frame

Accuracy

Clause

802.11-2024 §9.2.4.1.6

Verified

Not verified against the standard. Treat this as a claim, not a fact.