skip to content

What are the three 802.11 frame types, what job does each do, and how does the Frame Control field tell them apart?

level: middleimportance: must knowfreq 34%

answer

  1. three jobs on one shared channel
  2. first two octets of every frame
  3. two type bits, four subtype bits
  4. which frames carry no payload
  5. QoS Data versus null data

basics

~20 s

802.11 uses management frames (beacons, probes, authentication, association) to build and run the network, control frames (RTS, CTS, ACK, Block Ack) to coordinate delivery, and data frames to carry payload. The Frame Control field's type and subtype bits identify each.

solid answer

~50 s

Every 802.11 frame opens with a two-octet `Frame Control` field whose 2-bit type and 4-bit subtype name it. **Management** frames (type 0) build and maintain the network: beacon, probe request and response, authentication, association, reassociation, disassociation, deauthentication and action. **Control** frames (type 1) are short frames with no upper-layer payload that coordinate the medium and acknowledge delivery: RTS, CTS, ACK, Block Ack Request and Block Ack. **Data** frames (type 2) carry the payload; on a modern network that is mostly `QoS Data`, which adds a QoS Control field with the traffic ID, plus the bodiless null data frames a station uses to signal power save. The same field carries the `To DS`, `From DS`, `Retry` and `Protected Frame` flags, so it tells you both what the frame is and how to read the rest of its header.

go deeper

for a junior

Recall the three types and two or three examples of each: beacon and probe for management, ACK and RTS/CTS for control, QoS Data for data.

for a middle

Explain the Frame Control layout - type, subtype and the flags - and why control frames are minimal while QoS Data adds a QoS Control field.

for a senior

Use type and subtype to slice a capture: airtime spent on beacons and probes, retried data, Block Ack patterns, and which frames PMF protects.

for a principal

Connect frame-class overhead to design choices: how many SSIDs a radio beacons for, and what a management-heavy channel costs in usable airtime.

## Why 802.11 needs three kinds of frame A wired LAN mostly moves one kind of frame over a private cable. A wireless LAN has more to do on a shared, half-duplex radio channel: it has to announce that it exists, admit and release stations, coordinate who transmits and confirm what arrived, and only then carry user traffic. IEEE 802.11 therefore sorts every frame into one of three **frame types**: - **Management frames** create and maintain the relationship between stations and an access point (AP): they advertise the network, answer searches, admit and release stations and carry housekeeping actions. - **Control frames** coordinate delivery on the medium itself: they reserve airtime and acknowledge what was received. They are short and carry no upper-layer payload. - **Data frames** carry the payload handed down from above - in practice IP packets - plus a few bodiless variants used for signalling. ## The Frame Control field Every 802.11 frame opens with a two-octet **`Frame Control`** field, and reading it is the first step in reading any capture. In order, it holds: 1. **Protocol Version** - two bits, zero on every frame you will see. 2. **Type** - two bits: 0 management, 1 control, 2 data. Value 3 is an extension type used by a few specialised PHYs, not by everyday WLAN traffic. 3. **Subtype** - four bits that name the frame within its type. 4. **Flags** - `To DS`, `From DS`, `More Fragments`, `Retry`, `Power Management`, `More Data`, `Protected Frame` and `Order`. The flags matter as much as the type. `To DS` and `From DS` say which direction a data frame travels relative to the distribution system and so how its address fields are laid out; `Retry` marks a retransmission; `Power Management` tells the AP a station is about to doze; `Protected Frame` says the frame body is encrypted. The Linux kernel's 802.11 definitions expose the same layout as masks (`IEEE80211_FCTL_TODS`, `IEEE80211_FCTL_RETRY`, `IEEE80211_FCTL_PROTECTED` and so on). ## Management, control and data subtypes **Management (type 0)** subtypes include Association Request and Response, Reassociation Request and Response, Probe Request and Response, **Beacon**, Disassociation, Authentication, Deauthentication and **Action**. Action frames are the extensible catch-all: block-acknowledgement setup, radio measurement and many newer features ride inside them. **Control (type 1)** subtypes include **RTS**, **CTS**, **ACK**, **Block Ack Request**, **Block Ack** and PS-Poll. They are deliberately minimal: a CTS or an ACK carries only the Frame Control, a Duration value, a single receiver address and the FCS, because it must be sent quickly and understood by every station on the channel. **Data (type 2)** subtypes include plain Data, **QoS Data** - which adds a two-octet QoS Control field holding the traffic identifier (TID), the acknowledgement policy and an A-MSDU flag - and the **null data** frames (Null and QoS Null) that carry no body at all and exist to signal state, mostly power save. ## Reading the type in a capture The subtype number only means something together with the type: the same four bits name three unrelated frames in the three types. Values below are derived from the Linux 802.11 definitions. | Frame | Type | Subtype | |---|---|---| | Probe Request / Probe Response | 0 | 4 / 5 | | Beacon | 0 | 8 | | Authentication / Deauthentication | 0 | 11 / 12 | | Action | 0 | 13 | | Block Ack Request / Block Ack | 1 | 8 / 9 | | RTS / CTS / ACK | 1 | 11 / 12 / 13 | | Data / Null | 2 | 0 / 4 | | QoS Data / QoS Null | 2 | 8 / 12 | In Wireshark the fields are `wlan.fc.type`, `wlan.fc.subtype` and the combined `wlan.fc.type_subtype`, so separating beacons from Block Acks from QoS Data is a filter, not guesswork. Subtype 12 is Deauthentication under type 0, CTS under type 1 and QoS Null under type 2 - which is exactly why a filter on the subtype alone misleads. ## What the classification tells an operator - A capture dominated by beacons and probe traffic says the channel is spending airtime on discovery rather than payload. - Management frames travel unencrypted unless Protected Management Frames are in force, and even then only unicast robust ones are encrypted while broadcast ones get an integrity check; beacons are never encrypted because every station must read them before it joins. - Control frames are never encrypted and carry no payload; a capture full of ACKs and Block Acks is normal, a capture full of retried data frames is not. - Data frames after key installation carry the `Protected Frame` flag; their headers stay readable while their bodies do not. The order in which management frames appear while a station joins, and the timing rules that decide when a control frame may be sent, are separate subjects; the frame classification is what lets you recognise each frame when those subjects come up.

  • Why is a Block Ack a control frame while the ADDBA exchange that sets it up is a management frame?
    The ADDBA Request and Response are management Action frames because they negotiate a lasting agreement per traffic ID: buffer size, policy and timeout. The Block Ack itself is a control frame because it does a medium-level job - acknowledging a window of received MPDUs immediately after they arrive, with no payload of its own.
  • Which 802.11 frames carry the Protected Frame flag, and which never do?
    Data frames carry it once keys are installed, and unicast robust management frames such as deauthentication, disassociation and many action frames carry it when Protected Management Frames are in force; broadcast ones get an integrity check instead. Control frames never carry it, and beacons are never encrypted because every station must read them before joining.
  • Why is a filter on the 802.11 subtype number alone misleading?
    The four subtype bits are reused across types: 12 means Deauthentication for management, CTS for control and QoS Null for data. A filter has to combine type and subtype - in Wireshark, `wlan.fc.type_subtype` or both `wlan.fc.type` and `wlan.fc.subtype` - or it mixes unrelated frames.

  • Says ACK and Block Ack are management frames because they manage delivery.
  • Thinks beacons are encrypted on a WPA2 or WPA3 network.
  • Believes a subtype number alone identifies a frame without its type.
  • Says null data frames carry an empty IP packet.
  • Calls probe requests control frames because they look for an AP.