What is an 802.11 beacon frame, what does it carry, and how often does an access point send one?
answer
- the network announcing itself
- management, broadcast, never encrypted
- time units of 1.024 ms
- fixed fields, then elements
- SSID, TIM, RSN
basics
~20 sA beacon is a broadcast 802.11 management frame an access point sends, by default about ten times a second per BSSID, announcing its SSID, timestamp, capabilities, channel, supported rates, security suites (RSN element) and which dozing stations have buffered traffic (TIM).
solid answer
~40 sA beacon is an 802.11 **management frame** (type 0, subtype 8) that an AP broadcasts on a fixed schedule to announce a BSS. Its body opens with a **Timestamp**, the **Beacon Interval** and **Capability Information**, then elements: the **SSID**, **Supported Rates**, the **DS Parameter Set** with the channel, the **TIM** listing stations with buffered frames, the **Country** element, the **RSN** element with the security suites, and the HT/VHT/HE/EHT elements. The interval is counted in time units of 1.024 ms; hostapd defaults to `beacon_int=100`, about 102 ms, so roughly ten beacons a second for each BSSID. Beacons go out unencrypted, usually at a low rate every client can decode, so every extra SSID costs airtime on the channel.
code
ini · 6 linesinterface=wlan0
ssid=corp-example
beacon_int=100
dtim_period=2
beacon_rate=60
ignore_broadcast_ssid=0go deeper
Recall that a beacon is a broadcast management frame announcing the SSID and capabilities about ten times a second, and that it is never encrypted.
Explain the fixed fields and the main elements, the time unit behind the interval, and what the TIM and DTIM do for power save.
Use beacons as evidence: read the RSN and operation elements to confirm configuration, and spot missing beacons when a client loses the network.
Set SSID-count and beacon-rate standards for dense sites, weighing the airtime beacons consume against legacy clients that need low basic rates.
## What a beacon is A **beacon** is an 802.11 **management frame** (type 0, subtype 8) that an access point (AP) transmits on its own schedule to announce a basic service set (BSS). It is how a network says "I exist, here is my name, here is how I work" to every station on the channel, associated or not. Stations that scan passively learn about networks by listening for beacons, and associated stations use them to stay in step with their AP; how a station then chooses and joins a network is a separate subject. Beacons are **broadcast** - Address 1 is `ff:ff:ff:ff:ff:ff` - and Address 2 and Address 3 both carry the **BSSID**. They are never encrypted, because a station must read them before it has any keys. ## How often it is sent The AP sends one beacon per **beacon interval**, measured in time units (TU) of 1,024 microseconds. hostapd, the open-source reference implementation, defaults to `beacon_int=100`, about 102.4 ms, so roughly ten beacons a second **per BSSID**. Each SSID a radio serves normally has its own BSSID and its own beacon stream, unless the AP uses the Multiple BSSID element to advertise several BSSIDs from one beacon. A short hostapd fragment shows the knobs that shape beacons: ```ini ssid=corp-example beacon_int=100 dtim_period=2 beacon_rate=60 ``` `dtim_period=2` (hostapd's default) puts a delivery traffic indication message in every second beacon, and `beacon_rate=60` would send beacons at 6 Mbps; without it, hostapd's comment says the driver's default, likely the lowest rate, is used. ## What it carries A beacon body starts with three **fixed fields**: 1. **Timestamp** - the AP's timer, which associated stations use to synchronise. 2. **Beacon Interval** - the spacing in TU. 3. **Capability Information** - bits such as ESS (this is an AP network) and Privacy. Then come **elements**, each a tag, a length and a value: | Element | ID | What it tells a station | |---|---|---| | SSID | 0 | the network name, up to 32 octets | | Supported Rates | 1 | the legacy rates, with the basic rates marked | | DS Parameter Set | 3 | the channel the AP is on | | TIM | 5 | which dozing stations have buffered frames; DTIM count and period | | Country | 7 | regulatory domain and power limits | | RSN | 48 | the ciphers and key-management suites on offer | | HT, VHT, HE, EHT capabilities and operation | various | which generation features and channel widths are in use | | Vendor Specific | 221 | extensions such as the WMM parameters | A **probe response** carries almost the same content, and the differences are worth knowing when reading a capture: - a beacon is broadcast on a schedule; a probe response is sent to the one station whose probe request asked for it, so its Address 1 is that station; - a beacon goes out whether or not anyone is listening; a probe response exists only because a station asked; - the TIM, which only makes sense on the regular schedule that dozing stations wake for, is a beacon element and is not in probe responses; - both carry the same Timestamp, Beacon Interval and Capability Information fixed fields, so either one tells a station what the network offers. ## Why beacons matter to the person running the WLAN - **Airtime cost.** Beacons usually go out at a low legacy rate every client can decode. Every extra SSID multiplies beacon frames on the channel, and several APs on one channel each beacon for every SSID. On a dense floor, that overhead is a real share of the airtime. - **Power save.** The TIM tells dozing stations whether to wake for buffered traffic, and the DTIM beacon is when buffered broadcast and multicast frames are released, so `dtim_period` trades battery life against broadcast latency. - **Configuration evidence.** The RSN element is the authoritative statement of which security suites the network offers, and the capability and operation elements show the channel width and generation actually in use. - **Hiding the SSID does not stop beacons.** hostapd's `ignore_broadcast_ssid` sends an empty or blanked SSID element, but the beacon still goes out with its BSSID, channel and capabilities, so it hides the name only. ## Reading beacons in a capture In Wireshark, `wlan.fc.type_subtype` separates beacons from other management frames, and `wlan.bssid` groups them by network. A missing run of beacons from a BSSID means the AP stopped transmitting on that channel or the capture lost it, which is the first thing to rule out when a client "loses the network".
- Why does adding SSIDs to every AP radio slow down a busy channel?Each SSID normally has its own BSSID and beacons separately, about ten times a second, at a rate every client can decode - usually a low one. Several APs sharing a channel each beacon for every SSID, so the beacon load multiplies and takes airtime that data frames would otherwise use.
- What does the DTIM period in an 802.11 beacon change for clients?A DTIM beacon is when the AP releases buffered broadcast and multicast frames, so dozing stations must wake for it. hostapd's `dtim_period=2` means every second beacon. A longer period saves client battery but delays broadcast and multicast delivery to sleeping stations.
- Thinks beacons are encrypted once WPA3 is enabled.
- Says the beacon interval is exactly 100 ms by default.
- Believes hiding the SSID stops the AP from sending beacons.
- Calls a beacon a control frame because it coordinates stations.
- Assumes one beacon per AP no matter how many SSIDs it serves.