At-a-glance generations
| Spec | Common name | Band | Peak PHY rate* |
|---|---|---|---|
| 802.11 | Original WLAN | 2.4 GHz / IR | 2 Mb/s |
| 802.11b | HR-DSSS | 2.4 GHz | 11 Mb/s |
| 802.11a | OFDM | 5 GHz | 54 Mb/s |
| 802.11g | OFDM | 2.4 GHz | 54 Mb/s |
| 802.11n | Wi-Fi 4 | 2.4 / 5 GHz | 600 Mb/s |
| 802.11ac | Wi-Fi 5 | 5 GHz | 6.93 Gb/s |
| 802.11ax | Wi-Fi 6 / 6E | 2.4 / 5 / 6 GHz† | 9.61 Gb/s |
| 802.11be | Wi-Fi 7 | 2.4 / 5 / 6 GHz | ≈23.1 Gb/s |
| 802.11ah | Wi-Fi HaLow | Sub-1 GHz | ~0.15 Mb/s to tens of Mb/s |
| 802.11ad | WiGig / DMG | 60 GHz | ~6.76 Gb/s |
| 802.11ay | Enhanced DMG | 60 GHz class | 20+ Gb/s MAC-SAP mode |
| 802.11af | TV White Space | TV spectrum | Configuration dependent |
| 802.11p / bd | Vehicular WLAN | 5.9 GHz ITS | p: up to 27 Mb/s @ 10 MHz |
| 802.11bb | Light Communications | Optical | PHY dependent |
| 802.11r | Fast BSS Transition / Roaming | MAC feature | No new PHY rate |
PHY / radio specifications
802.11 (1997) — Original WLAN
The original standard defined multiple physical layers. The best-known radio options were 2.4 GHz FHSS and DSSS. It established the MAC behavior that later Wi-Fi generations evolved from.
| PHY | Modulation | Rates |
|---|---|---|
| DSSS | DBPSK at 1 Mb/s; DQPSK at 2 Mb/s | 1, 2 Mb/s |
| FHSS | 2/4-level GFSK variants | 1, 2 Mb/s |
| IR | Infrared pulse-position modulation | 1, 2 Mb/s |
802.11b (1999) — HR-DSSS / CCK
Extended DSSS in 2.4 GHz. The 5.5 and 11 Mb/s modes use Complementary Code Keying (CCK). Legacy 802.11b consumes substantial airtime because every frame takes much longer to transmit than modern OFDM frames.
| Rate | Modulation / coding | Meaning |
|---|---|---|
| 1 Mb/s | DBPSK + Barker spreading | Most robust legacy rate. |
| 2 Mb/s | DQPSK + Barker spreading | 2 bits per symbol before spreading effects. |
| 5.5 Mb/s | CCK | Higher-rate HR-DSSS mode. |
| 11 Mb/s | CCK | Maximum 802.11b PHY rate. |
802.11a (1999) — OFDM in 5 GHz
Introduced OFDM to mainstream WLANs. A 20 MHz channel uses 64 FFT subcarriers in the legacy OFDM design, with data carried on multiple orthogonal subcarriers.
| Rate Mb/s | Modulation | Coding rate |
|---|---|---|
| 6 | BPSK | 1/2 |
| 9 | BPSK | 3/4 |
| 12 | QPSK | 1/2 |
| 18 | QPSK | 3/4 |
| 24 | 16-QAM | 1/2 |
| 36 | 16-QAM | 3/4 |
| 48 | 64-QAM | 2/3 |
| 54 | 64-QAM | 3/4 |
802.11g (2003) — OFDM in 2.4 GHz
Brings the 802.11a OFDM rates to 2.4 GHz while retaining backward compatibility with 802.11b. Mixed b/g networks can incur protection overhead.
OFDM rates: 6, 9, 12, 18, 24, 36, 48, 54 Mb/s using BPSK, QPSK, 16-QAM, and 64-QAM with the same legacy OFDM coding combinations shown under 802.11a. Compatibility rates 1, 2, 5.5, and 11 Mb/s may also be present.
802.11n (2009) — Wi-Fi 4 / HT
High Throughput (HT) introduced MIMO spatial streams, 40 MHz channels, frame aggregation, and optional short guard interval. Modulation extends through 64-QAM.
| MCS per spatial stream | Modulation | Coding |
|---|---|---|
| 0 | BPSK | 1/2 |
| 1 | QPSK | 1/2 |
| 2 | QPSK | 3/4 |
| 3 | 16-QAM | 1/2 |
| 4 | 16-QAM | 3/4 |
| 5 | 64-QAM | 2/3 |
| 6 | 64-QAM | 3/4 |
| 7 | 64-QAM | 5/6 |
Representative 1-stream rates: 20 MHz long GI: 6.5–65 Mb/s; 20 MHz short GI: up to 72.2 Mb/s; 40 MHz long GI: up to 135 Mb/s; 40 MHz short GI: up to 150 Mb/s. Four spatial streams × 150 = 600 Mb/s.
802.11ac (2013) — Wi-Fi 5 / VHT
Very High Throughput (VHT) expands channel width and spatial-stream capacity and adds 256-QAM. It operates in the 5 GHz bands.
| MCS | Modulation | Coding |
|---|---|---|
| 0 | BPSK | 1/2 |
| 1–2 | QPSK | 1/2, 3/4 |
| 3–4 | 16-QAM | 1/2, 3/4 |
| 5–7 | 64-QAM | 2/3, 3/4, 5/6 |
| 8–9 | 256-QAM | 3/4, 5/6 |
Peak PHY: about 866.7 Mb/s per spatial stream at 160 MHz, MCS 9, short GI; up to about 6.93 Gb/s with 8 spatial streams.
802.11ax (2021) — Wi-Fi 6 / 6E / HE
High Efficiency (HE) focuses not only on peak speed but on efficient use of airtime in dense networks. OFDMA lets an AP divide a channel into Resource Units (RUs) so multiple stations can be scheduled within the same PPDU. Other major tools include uplink/downlink MU-MIMO, BSS Color, and Target Wake Time.
| MCS | Modulation | Coding |
|---|---|---|
| 0 | BPSK | 1/2 |
| 1–2 | QPSK | 1/2, 3/4 |
| 3–4 | 16-QAM | 1/2, 3/4 |
| 5–7 | 64-QAM | 2/3, 3/4, 5/6 |
| 8–9 | 256-QAM | 3/4, 5/6 |
| 10–11 | 1024-QAM | 3/4, 5/6 |
Peak PHY: 1.201 Gb/s per spatial stream at 160 MHz, MCS 11, 0.8 μs GI; 9.608 Gb/s with 8 streams.
802.11be (2024) — Wi-Fi 7 / EHT
Extremely High Throughput (EHT) extends HE with 320 MHz channels in 6 GHz, 4096-QAM, wider/more flexible multi-user operation, puncturing enhancements, and Multi-Link Operation (MLO). MLO can use multiple links/bands under one logical connection, improving throughput and/or latency depending on implementation and spectrum conditions.
| MCS | Modulation | Typical coding family |
|---|---|---|
| 0–11 | BPSK through 1024-QAM | Extends HE mappings |
| 12–13 | 4096-QAM | 3/4, 5/6 |
Peak theoretical PHY: approximately 23.1 Gb/s: about 2.882 Gb/s per spatial stream (320 MHz, MCS 13 / 4096-QAM 5/6, 0.8 µs GI) × 8 spatial streams, the maximum in the ratified 802.11be-2024. The often-quoted ≈46 Gb/s figure assumed 16 spatial streams, which was discussed during development but not included in the published amendment. The 802.11be project also set a ≥30 Gb/s MAC-throughput objective; a single 8-stream link cannot reach that, so treat it as a project goal (approachable only by combining links, e.g. with MLO), not a single-link PHY rate.
802.11ah (2016) — Wi-Fi HaLow / S1G
Specification: IEEE 802.11ah, commonly marketed as Wi-Fi HaLow. It operates in license-exempt sub-1 GHz spectrum; exact channel frequencies and allowed bandwidths depend on country. The lower carrier frequency improves propagation and wall penetration compared with 2.4/5/6 GHz, while narrower channels trade peak speed for range and link budget.
Its S1G OFDM PHY is derived from familiar Wi-Fi OFDM concepts but scaled for narrower channels. Modulations include BPSK, QPSK, 16-QAM, 64-QAM, and 256-QAM, with coding rates selected by MCS. MCS 10 is a very robust 1 MHz mode using BPSK with repetition.
| Channel width | Practical PHY-rate scale | Field meaning |
|---|---|---|
| 1 MHz | roughly 0.15 Mb/s at robust MCS10 up to several Mb/s | Longest-range / lowest-rate option. |
| 2 MHz | several Mb/s | Common compromise between range and rate. |
| 4 / 8 MHz | higher single- to multi-tens of Mb/s | More spectrum, greater peak rate. |
| 16 MHz | up to tens of Mb/s; approximately 78 Mb/s-class peak configurations are commonly cited | Highest-rate S1G mode where regulation permits. |
802.11ad (2012) — WiGig / DMG
Directional Multi-Gigabit (DMG) operation around 60 GHz uses very wide channels and directional beamforming. It includes single-carrier and OFDM PHY modes. High free-space and obstruction losses make it suited to short, highly directional links.
Modulation families: π/2-BPSK, π/2-QPSK, π/2-16QAM and OFDM modes. Maximum PHY rates are roughly 6.76 Gb/s.
802.11ay (2021) — Enhanced 60 GHz / EDMG
Enhanced DMG (EDMG) extends 802.11ad with channel bonding/aggregation, MIMO and improved beamforming. The amendment defines at least one mode capable of more than 20 Gb/s at the MAC service access point; theoretical PHY configurations can be much higher.
802.11af (2013) — TV White Space WLAN
Adapts WLAN operation to unused television channels under database/regulatory control. Its OFDM PHY is derived from 802.11ac concepts but scaled to narrower TV channels. Modulation ranges from BPSK through 256-QAM depending on MCS and configuration. Rates depend heavily on TV-channel bandwidth and bonding, so there is no single universal field rate.
802.11p / 802.11bd — Vehicular WLAN
802.11p adapts OFDM for vehicular environments, effectively using longer symbol timing than 20 MHz legacy OFDM. Typical PHY rates are 3, 4.5, 6, 9, 12, 18, 24, 27 Mb/s in 10 MHz channels with BPSK through 64-QAM. 802.11bd is the newer Next Generation V2X enhancement, adding more advanced PHY/MAC capabilities while maintaining coexistence goals.
802.11bb (2023) — Light Communications
802.11bb defines WLAN light communications using optical spectrum rather than an RF carrier. It adapts 802.11 MAC/PHY concepts to light communication front ends. Treat this as a specialized PHY, not a normal 2.4/5/6 GHz Wi-Fi mode.
Beacon values — what they tell you
An AP periodically sends Beacon management frames to advertise a BSS and tell clients how to interpret and use it. The exact Information Elements (IEs) vary by PHY generation, security mode and features enabled.
Beacon numeric decoder
| Item | Numeric value / encoding | How to read it |
|---|---|---|
| 802.11 subtype | Management type = 00b; Beacon subtype = 1000b. A common raw Frame Control value is 0x0080 (first octet 0x80 on-air capture representation). | Identifies the frame as a Beacon management frame. |
| Fixed parameters | Timestamp = 8 octets; Beacon Interval = 2; Capability Information = 2. | These 12 octets appear before tagged Information Elements in the Beacon body. |
| Time Unit (TU) | 1 TU = 1024 μs = 1.024 ms | Beacon and many timing values use TU rather than exact milliseconds. |
| Beacon Interval 100 | 100 TU = 102.4 ms ≈ 9.7656 beacons/s | The most common configured interval. |
| Beacon Interval 50 | 50 TU = 51.2 ms | Twice the beacon frequency of 100 TU, therefore more beacon airtime overhead. |
| Beacon Interval 200 | 200 TU = 204.8 ms | Half the beacon frequency of 100 TU; lower overhead but slower periodic signaling. |
| DTIM Period 1 | Every beacon. At 100 TU: 102.4 ms | Lowest multicast/broadcast buffering delay, higher wake frequency. |
| DTIM Period 2 | Every 2 beacons. At 100 TU: 204.8 ms | Common compromise. |
| DTIM Period 3 | Every 3 beacons. At 100 TU: 307.2 ms | More power-save opportunity; buffered group traffic can wait longer. |
Common Information Element numbers (Element IDs)
| Element | Element ID | Hex |
|---|---|---|
| SSID | 0 | 0x00 |
| Supported Rates | 1 | 0x01 |
| DS Parameter Set | 3 | 0x03 |
| TIM | 5 | 0x05 |
| Country | 7 | 0x07 |
| BSS Load | 11 | 0x0B |
| Channel Switch Announcement | 37 | 0x25 |
| ERP Information | 42 | 0x2A |
| HT Capabilities | 45 | 0x2D |
| RSN | 48 | 0x30 |
| Extended Supported Rates | 50 | 0x32 |
| HT Operation | 61 | 0x3D |
| Multiple BSSID | 71 | 0x47 |
| Extended Capabilities | 127 | 0x7F |
| VHT Capabilities | 191 | 0xBF |
| VHT Operation | 192 | 0xC0 |
| Reduced Neighbor Report (RNR) | 201 | 0xC9 |
| Element ID Extension | 255 | 0xFF |
Capability Information — 16-bit masks commonly seen in captures
| Bit | Hex mask | Classic/common decoded meaning |
|---|---|---|
| 0 | 0x0001 | ESS |
| 1 | 0x0002 | IBSS |
| 2 | 0x0004 | CF-Pollable (legacy) |
| 3 | 0x0008 | CF-Poll Request (legacy) |
| 4 | 0x0010 | Privacy |
| 5 | 0x0020 | Short Preamble |
| 6 | 0x0040 | PBCC / revision-dependent legacy-reserved use |
| 7 | 0x0080 | Channel Agility / revision-dependent reserved use |
| 8 | 0x0100 | Spectrum Management |
| 9 | 0x0200 | QoS |
| 10 | 0x0400 | Short Slot Time |
| 11 | 0x0800 | APSD |
| 12 | 0x1000 | Radio Measurement |
| 13 | 0x2000 | DSSS-OFDM / revision-dependent EPD or reserved use |
| 14 | 0x4000 | Delayed Block Ack / revision-dependent reserved use |
| 15 | 0x8000 | Immediate Block Ack / revision-dependent reserved use |
Supported Rates byte — numerical decoding
The lower 7 bits are the rate in units of 500 kb/s. Bit 7 (0x80) marks a Basic Rate. Formula: rate Mb/s = (byte & 0x7F) × 0.5.
| Rate | Normal byte | Basic-rate byte |
|---|---|---|
| 1 Mb/s | 0x02 | 0x82 |
| 2 Mb/s | 0x04 | 0x84 |
| 5.5 Mb/s | 0x0B | 0x8B |
| 6 Mb/s | 0x0C | 0x8C |
| 9 Mb/s | 0x12 | 0x92 |
| 11 Mb/s | 0x16 | 0x96 |
| 12 Mb/s | 0x18 | 0x98 |
| 18 Mb/s | 0x24 | 0xA4 |
| 24 Mb/s | 0x30 | 0xB0 |
| 36 Mb/s | 0x48 | 0xC8 |
| 48 Mb/s | 0x60 | 0xE0 |
| 54 Mb/s | 0x6C | 0xEC |
0x8C → clear Basic bit: 0x0C = 12; 12 × 0.5 = 6 Mb/s, and because bit 7 was set, 6 Mb/s is a Basic Rate. 0x6C → 108 × 0.5 = 54 Mb/s, not marked Basic.TIM / DTIM byte layout
| Byte / field | Numeric meaning |
|---|---|
| DTIM Count | 0 means this beacon is the DTIM; otherwise it is the number of beacon intervals remaining before the next DTIM. |
| DTIM Period | Unsigned 8-bit period. 1 = every beacon, 2 = every second beacon, 3 = every third beacon, etc. |
| Bitmap Control bit 0 | 0x01 is the Traffic Indicator for buffered group-addressed traffic in the applicable DTIM context. |
| Bitmap Control bits 1–7 | Bitmap offset portion used to compress the Partial Virtual Bitmap. |
| Partial Virtual Bitmap | Bits correspond to AID-related buffered-unicast indications after applying the bitmap offset rules. |
| Beacon field / IE | What the value means in the field |
|---|---|
| Timestamp | 64-bit TSF timer value. Stations use timing synchronization functions to maintain a common time base inside the BSS. |
| Beacon Interval | Advertised in Time Units (TU), where 1 TU = 1024 μs. A common value is 100 TU = 102.4 ms. Lower values create more management overhead; higher values reduce beacon overhead but can delay discovery/power-save signaling. |
| Capability Information | Bit field describing BSS capabilities such as ESS/IBSS mode, privacy/security indication, short preamble support, spectrum management, QoS, short slot time, APSD and radio-measurement capabilities. Interpret the individual bits rather than the hexadecimal value alone. |
| SSID | Network name, 0–32 octets. A zero-length/hidden SSID does not make the WLAN cryptographically secure. |
| Supported Rates | Legacy rates the BSS supports. A rate marked as a Basic Rate is mandatory for stations in that BSS and is important for management/control interoperability. |
| Extended Supported Rates | Additional legacy rate entries when they do not all fit in Supported Rates. |
| DS Parameter Set / Channel | Legacy indication of the current 2.4 GHz channel. Modern captures may rely more on HT/VHT/HE/EHT Operation IEs for complete channel-width/center-frequency information. |
| TIM | Traffic Indication Map. Shows whether the AP has buffered unicast traffic for sleeping stations. Includes DTIM Count, DTIM Period, Bitmap Control and Partial Virtual Bitmap. |
| DTIM Count | Number of beacon intervals until the next DTIM beacon. 0 means this beacon is a DTIM. |
| DTIM Period | How many beacon intervals occur between DTIMs. Example: Beacon Interval 100 TU and DTIM Period 3 → DTIM about every 307.2 ms. Larger periods may save client battery but can delay buffered broadcast/multicast delivery. |
| Bitmap Control / Partial Virtual Bitmap | Compressed indication of which Association IDs (AIDs) have unicast data buffered. Bit 0 also participates in signaling buffered broadcast/multicast traffic at DTIMs. |
| RSN | Robust Security Network information: security protocol/ciphers and AKM suites such as 802.1X or PSK/SAE. This is one of the most important IEs when validating WPA2/WPA3 configuration. |
| Country | Regulatory-country information and channel/power constraints. Useful when investigating domain mismatches. |
| ERP Information | 2.4 GHz 802.11g protection state, including whether non-ERP/legacy stations are present and whether protection mechanisms are required. |
| HT Capabilities / HT Operation | 802.11n features and current operation: channel width, MCS support, guard interval and related HT behavior. |
| VHT Capabilities / VHT Operation | 802.11ac capabilities and operating channel-width/center-channel information, spatial streams and VHT MCS support. |
| HE Capabilities / HE Operation | 802.11ax capabilities/operation including HE PHY/MAC parameters; captures may expose BSS Color and other HE-specific information. |
| EHT Capabilities / EHT Operation | 802.11be/Wi-Fi 7 capabilities such as EHT MCS/NSS support and operating details associated with wide channels and EHT operation. |
| Reduced Neighbor Report (RNR) | Compact information about neighboring BSSs. Particularly important for 6 GHz discovery because clients can learn about 6 GHz APs through information advertised elsewhere. |
| BSS Load / QBSS Load | May include station count, channel utilization and admission-capacity information. Useful, but do not equate a single utilization percentage directly with user throughput. |
| Channel Switch Announcement (CSA) | Tells clients the AP plans to move to another channel after a countdown. Often encountered around DFS events or planned channel changes. |
| Multiple BSSID | Allows several BSS profiles to be represented more efficiently by a transmitting BSSID, reducing beacon/probe overhead in multi-SSID deployments. |
| Multi-Link / MLO elements | Wi-Fi 7 information describing a Multi-Link Device and its affiliated links. Useful when verifying whether a client/AP pair is actually advertising MLO capability. |
Roaming — 802.11r, 802.11k and 802.11v
802.11r — Fast BSS Transition (FT)
802.11r is the primary IEEE roaming amendment. It reduces the authentication/key-establishment delay when a client moves from one AP to another within the same mobility domain. It does not define a new modulation or data rate; the client continues to use the PHY of the underlying WLAN such as 802.11n/ac/ax/be.
Why 802.11r matters
Without Fast BSS Transition, a roam can involve scanning, authentication, reassociation and security key negotiation. That delay can be noticeable to voice, video and other latency-sensitive traffic. 802.11r prepares keying material so the handoff can complete much faster.
| Item | Meaning |
|---|---|
| FT | Fast BSS Transition. The actual fast-roaming mechanism defined by 802.11r. |
| Mobility Domain | A group of APs that participate in the same 802.11r roaming domain. |
| MDID | Mobility Domain Identifier. A 16-bit value used to identify the FT mobility domain. |
| PMK-R0 | Top-level FT Pairwise Master Key material associated with the mobility domain. |
| PMK-R1 | Derived key material associated with a particular target AP/R1 key holder. |
| FT over-the-air | The client exchanges FT authentication directly with the target AP over the wireless medium. |
| FT over-the-DS | The client coordinates the FT exchange through the current AP/distribution system before moving to the target AP. |
Key 802.11r beacon / association values
| Element | Numeric value | Field meaning |
|---|---|---|
| Mobility Domain IE | Element ID 54 / 0x36 | Advertises the FT mobility domain and FT capability policy. |
| Mobility Domain ID | 2 octets / 16 bits | Example: 0x1234. APs intended for seamless FT roaming should advertise the same MDID. |
| FT Capability and Policy | 1 octet | Contains FT-related capability/policy bits including whether FT over the DS is supported. |
| Fast BSS Transition IE | Element ID 55 / 0x37 | Carries FT authentication/key information during the FT exchange. |
| RSN AKM for FT | FT-specific AKM suites appear in the RSN element | Examples include FT with 802.1X and FT with PSK/SAE depending on the network security design. |
What 802.11r does not do
- It does not decide when the client should roam. The client still makes the roaming decision.
- It does not guarantee a client will roam at a particular RSSI threshold.
- It does not fix poor RF design, excessive cell overlap or coverage holes.
- It does not create additional bandwidth or change MCS/data-rate capability.
802.11k — Radio Resource Measurement / Neighbor Assistance
802.11k helps a station learn about nearby APs and radio conditions so it can make a better roaming decision without blindly scanning every possible channel.
| Function | What it does |
|---|---|
| Neighbor Report | Provides candidate AP/BSSID/channel information to reduce roam scanning time. |
| Radio measurements | Supports measurements related to channels, beacons and link conditions. |
| Roaming benefit | Can reduce the time spent hunting for a target AP, especially in large multi-AP networks. |
802.11v — BSS Transition Management
802.11v adds Wireless Network Management functions. For roaming, the important feature is BSS Transition Management, which allows the network to recommend candidate APs to a client.
| Function | What it means |
|---|---|
| BSS Transition Management Request | The AP/network suggests that a client move, optionally providing candidate BSSs. |
| Client response | The client may accept, reject or ignore the recommendation depending on implementation and policy. |
| Roaming benefit | Helps steer clients away from overloaded or less-desirable APs. |
How the roaming trio fits together
| Standard | Field shorthand | Role in roaming |
|---|---|---|
| 802.11k | “Where can I roam?” | Neighbor information and measurements. |
| 802.11v | “Where should I roam?” | Network-assisted transition recommendations. |
| 802.11r | “How do I roam quickly?” | Fast authentication/key transition between APs. |
Roaming symptoms to measure
| Symptom | Likely area | What to capture |
|---|---|---|
| Client stays on distant AP | Client roaming policy / RF overlap | RSSI/SNR over time, neighbor reports, BSS transition requests. |
| Roam occurs but voice drops | Authentication/reassociation delay | Authentication, reassociation, FT frames, packet-loss gap. |
| Long scan pause before roam | Candidate discovery | Probe behavior, 802.11k neighbor reports, scan channels. |
| Network asks client to move but it does not | 802.11v/client policy | BSS Transition Management Request/Response. |
| FT advertised but not used | Client compatibility/security configuration | Mobility Domain IE, RSN AKMs, authentication algorithm, reassociation exchange. |
RF Loss Calculator
This calculator estimates free-space path loss (FSPL) plus approximate attenuation through common building materials. It is intended as a field-planning aid, not a substitute for an RF survey.
1 · RF path and radio parameters
2 · Walls and obstructions
Choose a material and number of penetrations. Default losses now change with the selected band (915 MHz / 2.4 / 5 / 6 GHz); most materials attenuate more at higher frequency. Values are approximate mid-range planning figures and change with thickness, moisture, framing, angle of incidence, metal backing and frequency.
Middle box: optionally override the material's default dB loss with your own measured/known value. Right box: number of walls/penetrations.
| Free-space path loss | — |
| Material / wall loss | — |
| Total estimated loss | — |
| Estimated received power | Enter Tx power to calculate |
SNR / SINR and likely MCS
Android keyboard tip: enter a positive magnitude such as 60, then tap Make negative (−). All dBm values may be signed.
Signal, noise and aggregate overlapping interference are entered in dBm. Interference is optional. Results update automatically when you edit an input. Estimates are illustrative, not guaranteed radio performance.
3 · Signal, noise and interference
4 · PHY and device capabilities
Requested settings are limited by the AP and client capabilities.
5 · Adjacent-channel interference (optional)
Choose a desired 2.4 GHz primary channel and optionally enable a left and/or right interfering transmitter. Enter its received level and an assumed or measured effective coupling (dB). Effective interference = received level + coupling. Coupling is not automatically derived from channel numbers: it depends on spectral overlap, transmitter emissions, receiver filtering, and bandwidth. These are simultaneous-power calculations, not airtime/collision predictions.
Illustrative model only: assumes flat interferer power spectral density, an ideal rectangular desired-channel passband, and uniform out-of-band suppression. Not an IEEE 802.11 spectral-mask or receiver-selectivity prediction. Manual, geometry, and comparison modes retain manual coupling for primary SINR; only explicitly selected automatic mode uses estimated coupling for primary SINR, MCS, and PHY rate.
Geometry preview: Computes nominal occupied-width overlap only, using rectangular channel intervals and explicitly selected 40 MHz secondary-channel direction. This is not an 802.11 spectral mask, interference attenuation, or throughput model. Manual coupling remains primary unless automatic estimated coupling mode is explicitly selected. Comparison shows a separate estimated SINR. A 40 MHz channel with an invalid secondary-channel placement is flagged as out of the US channel 1–11 range.
Scope: Channels 1–11 are listed for this US-oriented 2.4 GHz exercise. Channel width is descriptive only; this tool does not compute coupling, account for 40 MHz secondary-channel placement, or validate regulatory channel plans. Use measured receiver characteristics where available. The existing overlapping-interference input remains independent and is added in linear power.
2.4 GHz spectrum visualization
Both views use the desired channel and enabled left/right interferers above. Analyzer heights use entered received powers, not modeled coupled interference. Nominal channel envelopes are not measured spectral masks.
5 GHz / 6 GHz channel overlap — geometry exercise
Independent nominal frequency-geometry exercise. Select each AP's channel width and center channel. This does not modify the existing 2.4 GHz interference model, SINR, MCS, or PHY-rate calculations.
AP A and AP B occupy the indicated frequency intervals. The amber region indicates shared nominal spectrum, not measured interference.
Standalone planning exercise. Enter AP B's total received channel power at AP A's receiver (not AP B transmit power). Assumes uniform power spectral density across AP B's nominal channel, an ideal rectangular AP A receiver passband, and a constant assumed rejection outside that passband. This is not a measured spectral mask, receiver selectivity, or Wi-Fi contention model. Opt-in use in SINR is an illustrative simultaneous-interference scenario, not a throughput or airtime prediction.
Model: fraction of AP B power inside AP A's nominal passband = overlap MHz / AP B bandwidth MHz. Effective coupled fraction = inside fraction + (1 − inside fraction) × 10−rejection/10. Effective received interference (dBm) = AP B received power (dBm) + 10 log₁₀(coupled fraction). For zero overlap, this model still assumes residual leakage; it does not calculate actual frequency-dependent rejection. AP A's channel width fraction is not used as the power fraction. Only the explicit opt-in control can feed this modeled interference into Live Link SINR.
Nominal rectangular channel footprints only; not spectral masks, interference power, carrier sensing, or airtime. 5 GHz selections use a limited set of standard channel blocks; 6 GHz uses the standard 20/40/80/160 MHz channelization grid. Regulatory permissions, DFS, and device support are not validated. 6 GHz center frequency = 5950 + 5 × channel number MHz; 5 GHz = 5000 + 5 × channel number MHz.
Formula
Total estimated loss = FSPL + sum of obstruction losses.
If transmit power is entered: Rx dBm ≈ Tx dBm + Tx antenna gain + Rx antenna gain − total loss.
Approximate material attenuation guidance
The ranges below span all Wi-Fi bands. The calculator dropdown picks a band-specific value inside (or near) each range: lower at 915 MHz, higher at 5–6 GHz. Override with a measured value whenever you have one.
| Material | Planning range | Comments |
|---|---|---|
| Drywall / sheetrock | ~2–4 dB | Can be higher with insulation, plumbing, tile or metal studs. |
| Wood / plywood | ~3–6 dB | Moisture content matters. |
| Interior glass | ~3–6 dB | Ordinary glass is usually modest loss. |
| Brick | ~6–12 dB | Thickness and moisture strongly affect loss. |
| Concrete block / CMU | ~8–15 dB | Filled cells/rebar can increase attenuation. |
| Reinforced concrete | ~10–20+ dB | Rebar and thickness can make loss severe. |
| Low-E / metallized glass | ~10–30+ dB | Metallic coating can attenuate Wi-Fi dramatically. |
| Foil-faced insulation | ~15–30+ dB | Can behave like an RF shield. |
| Metal wall / sheet metal | ~20–40+ dB | May block direct path almost completely; openings dominate. |
Co-channel interference / contention
Co-channel interference (CCI) is often better understood in Wi-Fi as co-channel contention: two or more BSSs or stations can hear activity on the same channel and must share the same airtime. Because 802.11 uses CSMA/CA, a station normally defers while the medium is busy, then performs a randomized backoff before transmitting.
What happens to latency
- Queueing increases. Frames wait behind local traffic and neighboring same-channel transmissions.
- Contention/backoff grows. More contenders mean more opportunities to freeze and restart backoff counters.
- Jitter increases. Access delay becomes less predictable, so voice, video and interactive traffic can show wider latency variation even before packet loss is obvious.
- Tail latency can become severe. Average ping may look acceptable while the 95th/99th percentile becomes poor during bursts.
- Hidden nodes make it worse. If two transmitters cannot hear each other but both reach the AP, simultaneous transmissions can collide, forcing retries and exponential contention-window growth.
What happens to data rate and throughput
- PHY rate and throughput are different. A client may remain associated at a high MCS while receiving only a small fraction of channel airtime; its PHY rate can look excellent while TCP/UDP throughput collapses.
- Airtime is the scarce resource. Roughly speaking, if two busy BSSs fully hear one another on the same channel, they must divide usable airtime rather than each receiving a private copy of the channel.
- Slow clients consume disproportionate airtime. A frame sent at a low PHY rate occupies the channel longer, reducing the airtime left for every other same-channel station.
- Retries consume airtime twice. A failed transmission used airtime and its retransmission uses more. Retry rate is therefore a strong field indicator of interference/hidden-node problems.
- Rate adaptation may step down MCS. If collisions/interference reduce effective SINR or increase frame loss, the radio may select more robust modulation/coding, which further increases airtime per payload bit.
| Observed condition | Likely effect | What to measure |
|---|---|---|
| High same-channel utilization, low retry rate | Mostly contention: higher latency and lower throughput even with clean RF. | Channel utilization, airtime, queue delay, busy time. |
| High utilization + high retries | Contention plus collisions/interference/hidden nodes. | Retries, failed frames, ACK loss, client SNR, hidden-node geometry. |
| High RSSI but poor throughput | Often congestion/CCI, not lack of signal. | MCS, airtime share, utilization, retries, neighboring BSSs. |
| Low PHY rate client in busy BSS | Large airtime cost; impacts everyone. | Per-client airtime, MCS/NSS, bytes vs airtime. |
| Wide 80/160/320 MHz channel in dense area | More chance of overlapping another BSS; fewer independent channel choices. | Primary/secondary channel occupancy and puncturing where supported. |
Why adjacent-channel interference is different
With true co-channel activity, compatible Wi-Fi devices can normally detect one another and share airtime. With overlapping/adjacent energy that is not cleanly decoded as valid 802.11, the victim may see elevated noise, corrupted frames or energy-detect busy time without the same orderly coordination. In 2.4 GHz this is why channel planning traditionally favors non-overlapping 20 MHz channels rather than partially overlapping channels.
Common non-PHY amendments
These are important 802.11 specifications, but they generally do not define a new modulation/data-rate family. They add MAC, security, roaming, management, QoS, positioning, sensing or other behavior to an underlying PHY.
| Spec | Purpose |
|---|---|
| 802.11d | Regulatory-domain / country information support. |
| 802.11e | QoS enhancements; foundation for WMM-style prioritized access. |
| 802.11h | Spectrum management in 5 GHz, including DFS/TPC concepts. |
| 802.11i | Robust security enhancements; foundation associated with WPA2/RSN. |
| 802.11k | Radio Resource Measurement; neighbor and measurement information used by roaming/optimization systems. |
| 802.11r | Fast BSS Transition (FT), the primary IEEE fast-roaming amendment. |
| 802.11u | Interworking with external networks; network discovery/selection information. |
| 802.11v | Wireless Network Management, including BSS Transition Management used for roaming guidance. |
| 802.11w | Protected Management Frames. |
| 802.11ai | Fast Initial Link Setup. |
| 802.11az | Next-generation positioning / enhanced ranging. |
| 802.11bf | WLAN sensing enhancements using supported Wi-Fi PHYs. |
| 802.11bk | 320 MHz positioning enhancements based on EHT/802.11be capabilities. |
Modulation & rate terms
How to read a field capture
For an AP, first identify band/channel + channel width + advertised PHY generation. Then inspect Beacon Interval, DTIM, Supported/Basic Rates, RSN, HT/VHT/HE/EHT Operation. For a client problem, add actual MCS, NSS, retries, RSSI/SNR, channel utilization and latency. A strong RSSI with high utilization and low throughput points in a very different direction than a weak SNR with repeated MCS fallback.
Appendix — Manufacturer RF characteristics and receiver selectivity
Informational reference only. These published example specifications do not feed the RF calculator, change its default values, or validate its automatic adjacent-channel coupling estimate. Values vary by regulatory domain, firmware, radio configuration, MCS, and power definition. The listed models are examples, not a market-share ranking.
Access point transmit power and integrated antenna gain
| Manufacturer / model | Published transmit power | Published antenna gain | Definition / source |
|---|---|---|---|
| Cisco Catalyst 9130AXI | Available power settings up to 23 dBm (2.4 GHz), 26 dBm (5 GHz) | 4 dBi (2.4 GHz); 6 dBi (5 GHz) | Published power settings and peak integrated gain; Cisco datasheet |
| HPE Aruba AP-635 | Consult radio-specific conducted-power and regulatory tables; not directly comparable here | Peak 4.6 dBi (2.4 GHz); 7.0 dBi (5 GHz); 6.3 dBi (6 GHz) | Peak individual integrated antenna gain; HPE QuickSpecs |
| Ubiquiti UniFi U6 Pro | Max 22 dBm (2.4 GHz); 26 dBm (5 GHz) | 4 dBi (2.4 GHz); 6 dBi (5 GHz) | Manufacturer maximum TX power and antenna gain; Ubiquiti specifications |
| RUCKUS R550 | Peak 26 dBm (2.4 GHz); 25 dBm (5 GHz) | Up to 3 dBi | Peak TX port/chain plus combining gain; RUCKUS datasheet |
Power terminology: conducted output power, summed/combined chain power, and EIRP are not interchangeable. EIRP for a single transmit path is conducted power + antenna gain − feed losses; MIMO aggregation and regulatory constraints require additional care. Maximum hardware settings are not necessarily typical deployed settings.
Receiver sensitivity — published RUCKUS R550 examples
| Band / HE mode | MCS 0 | MCS 7 | MCS 11 |
|---|---|---|---|
| 2.4 GHz HE20 | −97 dBm | −78 dBm | −67 dBm |
| 2.4 GHz HE40 | −94 dBm | −75 dBm | −64 dBm |
| 5 GHz HE80 | See full datasheet | See full datasheet | See full datasheet |
Source: RUCKUS R550 receive-sensitivity tables. Sensitivity is a packet-demodulation threshold under stated conditions, not the receiver noise floor or noise figure.
Noise figure and thermal-noise reference
Complete-access-point, model-specific receiver noise figures are not established by the sources in this appendix. Published low-noise-amplifier or RF front-end component noise figures must not be substituted for a complete access point's cascaded receiver noise figure.
Noise floor (dBm) ≈ −174 + 10 log10(B in Hz) + receiver NF (dB), for approximately 290 K. Illustrative assumed 7 dB complete-receiver NF: 20 MHz ≈ −93.99 dBm; 40 MHz ≈ −90.98 dBm; 80 MHz ≈ −87.97 dBm. These are calculations, not published AP measurements.
Filter isolation, adjacent-channel rejection and blocking
No verified, model-specific adjacent-channel rejection (ACR), nonadjacent-channel rejection, or blocking-versus-frequency curves are established here for the four complete APs. Do not infer a fixed −10, −20, or −30 dB receiver suppression from antenna gain, TX spectral masks, or sensitivity alone.
For quantitative out-of-band interference work, obtain the victim receiver's measured packet-error-rate-versus-interferer-power data, desired signal level, frequency offset, bandwidth, modulation, and test conditions. Distinguish (1) interfering transmitter spectral leakage, (2) victim receiver filtering/selectivity, and (3) receiver desensitization/blocking. IEEE 802.11 receiver rejection tests provide standardized conditions but do not automatically characterize a particular deployed AP.
Field use: Treat the calculator's channel-overlap-derived coupling as an illustrative estimate, not certified receiver rejection. Use measured receiver response or an explicitly identified assumption for engineering decisions. Manufacturer URLs require internet access; the reference text remains available offline. Appendix compiled 2026-10-25.
Appendix 2 — Wireshark capture and display filters for Wi-Fi AP network analysis
Informational reference only. This appendix is a field guide to packet acquisition and filtering; it does not change calculator inputs, outputs, or RF calculations. Use packet capture only on networks you own or are authorized to examine.
First identify where you are capturing
| Capture location | Usually visible | Not normally visible |
|---|---|---|
| AP uplink / switch SPAN or TAP | Ethernet/IP traffic forwarded to or from AP, VLAN tags if present at capture point, DHCP, DNS, TCP, UDP, tunneled AP traffic | 802.11 beacons, probe exchanges, RF retries, radio RSSI, management/control frames |
| Wireless adapter in monitor mode, tuned to target channel | 802.11 management/control/data frames and sometimes radiotap RSSI/channel metadata, subject to adapter/driver support | Decrypted application payload without suitable keys and decryption setup; traffic on other channels not monitored |
| Controller/gateway uplink | Traffic exposed at that interface; may be tunneled or already decapsulated | Over-the-air RF details; inner client traffic if encapsulated/encrypted |
Important: The Wi-Fi client MAC may not appear on the wired side when traffic is routed, NATed, proxied, or tunneled. Wi-Fi 6/7 radios and multi-link traffic may require multiple simultaneous capture interfaces/channels for complete observation.
Two different filter languages
Capture filters use libpcap/BPF syntax and are set before capture. They reduce what is recorded; discarded frames cannot be recovered. Display filters use Wireshark field expressions and are applied after capture, leaving captured packets intact. In Wireshark, the main filter bar is a display filter, not a capture filter.
A. Capture filters (BPF) — start on an AP Ethernet uplink
| Objective | Capture filter | Field note |
|---|---|---|
| All traffic involving a known AP management IP | host 192.0.2.10 | Only packets with that IP; will not capture all bridged client traffic |
| One client IP | host 192.0.2.25 | Use actual client IP; routed/tunneled paths may hide it |
| DHCPv4 | udp port 67 or udp port 68 | Captures BOOTP/DHCPv4 exchanges |
| DNS over conventional port 53 | port 53 | TCP and UDP; excludes encrypted DNS on other ports |
| ARP | arp | IPv4 address-resolution frames on Ethernet |
| ICMP / ping (IPv4) | icmp | Does not include ICMPv6 |
| HTTPS on TCP 443 | tcp port 443 | Excludes QUIC/HTTP3 over UDP 443 |
| TCP or UDP 443 | port 443 | Includes TCP and UDP |
| Traffic on a VLAN (tag visible) | vlan 100 | Only works if capture retains 802.1Q tag; offload/SPAN may affect visibility |
| Client MAC on Ethernet | ether host 02:11:22:33:44:55 | Works only when this MAC is present in Ethernet headers |
Addresses 192.0.2.10, 192.0.2.25 and 02:11:22:33:44:55 are examples; substitute actual values. On VLAN-tagged frames, some capture-filter expressions may require explicit VLAN-aware syntax depending on capture path and BPF compiler. Test capture visibility before narrowing filters.
B. Display filters — inspect a captured AP uplink trace
| Question | Wireshark display filter |
|---|---|
| Packets involving one client IPv4 | ip.addr == 192.0.2.25 |
| Packets involving one client IPv6 | ipv6.addr == 2001:db8::25 |
| DHCPv4 discovery / lease traffic | bootp |
| DNS queries and responses | dns |
| DNS responses indicating error | dns.flags.rcode != 0 |
| ARP traffic | arp |
| IPv6 neighbor discovery | icmpv6.type == 135 || icmpv6.type == 136 |
| TCP connection setup (SYN without ACK) | tcp.flags.syn == 1 && tcp.flags.ack == 0 |
| TCP retransmission analysis | tcp.analysis.retransmission || tcp.analysis.fast_retransmission |
| TCP duplicate ACK indications | tcp.analysis.duplicate_ack |
| TCP reset frames | tcp.flags.reset == 1 |
| High TCP round-trip-time samples (over 100 ms) | tcp.analysis.ack_rtt > 0.1 |
| VLAN 100 (when tag visible) | vlan.id == 100 |
| TCP/UDP traffic on port 443 | tcp.port == 443 || udp.port == 443 |
| QUIC when decoded as QUIC | quic |
Interpretation: TCP retransmissions and RTT are indicators of end-to-end behavior, not proof of Wi-Fi RF interference. Packet loss, congestion, server delays, SPAN drops, or capture placement can produce similar symptoms. Wireshark's TCP analysis fields depend on capture completeness and packet ordering.
C. Display filters — over-the-air 802.11 monitor-mode capture only
| Question | Wireshark display filter | Note |
|---|---|---|
| Beacons | wlan.fc.type_subtype == 0x08 | Beacon management frames |
| Probe requests | wlan.fc.type_subtype == 0x04 | Client discovery attempts |
| Probe responses | wlan.fc.type_subtype == 0x05 | AP discovery responses |
| Authentication frames | wlan.fc.type_subtype == 0x0b | 802.11 authentication, not all higher-layer authentication |
| Association requests | wlan.fc.type_subtype == 0x00 | Client association attempt |
| Reassociation requests | wlan.fc.type_subtype == 0x02 | Useful for roaming analysis |
| Deauthentication frames | wlan.fc.type_subtype == 0x0c | Inspect reason code and protected management frame context |
| Disassociation frames | wlan.fc.type_subtype == 0x0a | Inspect reason code |
| Frames marked retry | wlan.fc.retry == 1 | 802.11 MAC retry bit; requires 802.11 capture |
| EAPOL handshake frames | eapol | Often visible before data decryption |
| One BSSID | wlan.bssid == 02:11:22:33:44:55 | Replace example with actual BSSID |
| One station MAC | wlan.addr == 02:11:22:33:44:55 | Matches 802.11 address fields |
| RSSI at or below −75 dBm (if radiotap supplies it) | radiotap.dbm_antsignal <= -75 | Driver-dependent capture metadata; not available in every trace |
Capture limitations: A standard Ethernet AP-uplink capture will not contain wlan.* or radiotap.* fields. Monitor-mode hardware, channel tuning, PHY compatibility, regulatory restrictions and driver support determine what can be observed. Encrypted 802.11 payloads require appropriate authorized decryption material and configuration; WPA3/enterprise captures have additional limitations.
D. Practical capture workflow for AP performance troubleshooting
- Define the question: association/roaming, DHCP, DNS, application delay, TCP loss, or RF retries.
- Choose the observation point: SPAN/TAP on AP uplink for forwarded client traffic; monitor-mode radio for over-the-air management and retransmission evidence.
- Begin broad: initially avoid restrictive capture filters so you do not discard relevant evidence.
- Capture a timestamped baseline: record AP, SSID, VLAN, client MAC/IP, channel, width, test time, and whether traffic is bridged or tunneled.
- Apply display filters: isolate DHCP, DNS, TCP setup/retransmissions, roaming events or retries, as appropriate.
- Correlate: compare wired trace, wireless trace, AP counters and client telemetry; align clocks before attributing delays to RF.
- Preserve evidence: save original
.pcapng, annotate test conditions, and redact sensitive traffic before sharing.
E. Official references
Wireshark User's Guide · Capture and analysis workflow · Capture filter (pcap-filter) syntax · Wireshark display-filter field reference · WLAN capture setup.
Field names and decoder behavior can vary by Wireshark release and capture encapsulation. Confirm individual filters against the installed Wireshark version. Source links require internet; this reference page and examples work offline.