v28
DoubleBarDoubleJ Ranch & Tech Services LLC

WiFi RF Field Calculator & 802.11 Reference

← DoubleBarDoubleJ Home · David V Jones · Horseshoe Bend, Idaho · doublebardoublej@gmail.com

At-a-glance generations

SpecCommon nameBandPeak PHY rate*
802.11Original WLAN2.4 GHz / IR2 Mb/s
802.11bHR-DSSS2.4 GHz11 Mb/s
802.11aOFDM5 GHz54 Mb/s
802.11gOFDM2.4 GHz54 Mb/s
802.11nWi-Fi 42.4 / 5 GHz600 Mb/s
802.11acWi-Fi 55 GHz6.93 Gb/s
802.11axWi-Fi 6 / 6E2.4 / 5 / 6 GHz†9.61 Gb/s
802.11beWi-Fi 72.4 / 5 / 6 GHz≈23.1 Gb/s
802.11ahWi-Fi HaLowSub-1 GHz~0.15 Mb/s to tens of Mb/s
802.11adWiGig / DMG60 GHz~6.76 Gb/s
802.11ayEnhanced DMG60 GHz class20+ Gb/s MAC-SAP mode
802.11afTV White SpaceTV spectrumConfiguration dependent
802.11p / bdVehicular WLAN5.9 GHz ITSp: up to 27 Mb/s @ 10 MHz
802.11bbLight CommunicationsOpticalPHY dependent
802.11rFast BSS Transition / RoamingMAC featureNo new PHY rate
Tap a standard in the table to jump directly to its expanded description. The non-PHY amendment table farther down uses the same internal-link format.
*Maximum theoretical PHY link rate using the widest channel, highest modulation/coding, and maximum spatial streams defined by the PHY. Application throughput is lower. †6 GHz operation is associated with Wi-Fi 6E regulatory/certification use of the 802.11ax PHY.

PHY / radio specifications

802.11 (1997) — Original WLAN
2.4 GHz1–2 Mb/sDSSS / FHSS / Infrared

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.

PHYModulationRates
DSSSDBPSK at 1 Mb/s; DQPSK at 2 Mb/s1, 2 Mb/s
FHSS2/4-level GFSK variants1, 2 Mb/s
IRInfrared pulse-position modulation1, 2 Mb/s
802.11b (1999) — HR-DSSS / CCK
2.4 GHz20/22 MHz-class channel11 Mb/s max

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.

RateModulation / codingMeaning
1 Mb/sDBPSK + Barker spreadingMost robust legacy rate.
2 Mb/sDQPSK + Barker spreading2 bits per symbol before spreading effects.
5.5 Mb/sCCKHigher-rate HR-DSSS mode.
11 Mb/sCCKMaximum 802.11b PHY rate.
802.11a (1999) — OFDM in 5 GHz
5 GHz20 MHz6–54 Mb/s

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/sModulationCoding rate
6BPSK1/2
9BPSK3/4
12QPSK1/2
18QPSK3/4
2416-QAM1/2
3616-QAM3/4
4864-QAM2/3
5464-QAM3/4
802.11g (2003) — OFDM in 2.4 GHz
2.4 GHz20 MHz54 Mb/s max

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
2.4 / 5 GHz20 / 40 MHzMIMO600 Mb/s max

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 streamModulationCoding
0BPSK1/2
1QPSK1/2
2QPSK3/4
316-QAM1/2
416-QAM3/4
564-QAM2/3
664-QAM3/4
764-QAM5/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
5 GHz20/40/80/160 MHz256-QAMMU-MIMO

Very High Throughput (VHT) expands channel width and spatial-stream capacity and adds 256-QAM. It operates in the 5 GHz bands.

MCSModulationCoding
0BPSK1/2
1–2QPSK1/2, 3/4
3–416-QAM1/2, 3/4
5–764-QAM2/3, 3/4, 5/6
8–9256-QAM3/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
2.4 / 5 / 6 GHzOFDMA1024-QAM9.61 Gb/s max

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.

MCSModulationCoding
0BPSK1/2
1–2QPSK1/2, 3/4
3–416-QAM1/2, 3/4
5–764-QAM2/3, 3/4, 5/6
8–9256-QAM3/4, 5/6
10–111024-QAM3/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.

BSS Color does not create new spectrum. It helps a station distinguish same-BSS traffic from overlapping-BSS traffic and can permit more spatial reuse when signal thresholds and rules allow.
802.11be (2024) — Wi-Fi 7 / EHT
2.4 / 5 / 6 GHz320 MHz4096-QAMMulti-Link Operation

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.

MCSModulationTypical coding family
0–11BPSK through 1024-QAMExtends HE mappings
12–134096-QAM3/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
Sub-1 GHzLong rangeIoT1/2/4/8/16 MHz channels

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 widthPractical PHY-rate scaleField meaning
1 MHzroughly 0.15 Mb/s at robust MCS10 up to several Mb/sLongest-range / lowest-rate option.
2 MHzseveral Mb/sCommon compromise between range and rate.
4 / 8 MHzhigher single- to multi-tens of Mb/sMore spectrum, greater peak rate.
16 MHzup to tens of Mb/s; approximately 78 Mb/s-class peak configurations are commonly citedHighest-rate S1G mode where regulation permits.
Field shortcut: HaLow is not “slow Wi-Fi” in the 802.11b sense. It is a purpose-built sub-1 GHz OFDM WLAN optimized for long reach, low-power stations, large device populations, and IoT traffic. IEEE specifies a minimum data rate of at least 100 kb/s and a design range up to 1 km.
802.11ad (2012) — WiGig / DMG
60 GHzVery short rangeBeamforming~7 Gb/s

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
>45 GHz / 60 GHz classChannel bondingMIMO20+ Gb/s target

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
TV white-space spectrumOFDMRegion dependent

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
5.9 GHz ITS10 MHz-class channelsMobility

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
Optical / lightNot RF802.11 MAC

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

ItemNumeric value / encodingHow to read it
802.11 subtypeManagement 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 parametersTimestamp = 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 msBeacon and many timing values use TU rather than exact milliseconds.
Beacon Interval 100100 TU = 102.4 ms ≈ 9.7656 beacons/sThe most common configured interval.
Beacon Interval 5050 TU = 51.2 msTwice the beacon frequency of 100 TU, therefore more beacon airtime overhead.
Beacon Interval 200200 TU = 204.8 msHalf the beacon frequency of 100 TU; lower overhead but slower periodic signaling.
DTIM Period 1Every beacon. At 100 TU: 102.4 msLowest multicast/broadcast buffering delay, higher wake frequency.
DTIM Period 2Every 2 beacons. At 100 TU: 204.8 msCommon compromise.
DTIM Period 3Every 3 beacons. At 100 TU: 307.2 msMore power-save opportunity; buffered group traffic can wait longer.

Common Information Element numbers (Element IDs)

ElementElement IDHex
SSID00x00
Supported Rates10x01
DS Parameter Set30x03
TIM50x05
Country70x07
BSS Load110x0B
Channel Switch Announcement370x25
ERP Information420x2A
HT Capabilities450x2D
RSN480x30
Extended Supported Rates500x32
HT Operation610x3D
Multiple BSSID710x47
Extended Capabilities1270x7F
VHT Capabilities1910xBF
VHT Operation1920xC0
Reduced Neighbor Report (RNR)2010xC9
Element ID Extension2550xFF
HE/EHT and other newer elements often use Element ID 255 plus an Element-ID-Extension byte. A packet analyzer normally displays the extension name directly, so use both the base EID and extension value when decoding raw bytes.

Capability Information — 16-bit masks commonly seen in captures

BitHex maskClassic/common decoded meaning
00x0001ESS
10x0002IBSS
20x0004CF-Pollable (legacy)
30x0008CF-Poll Request (legacy)
40x0010Privacy
50x0020Short Preamble
60x0040PBCC / revision-dependent legacy-reserved use
70x0080Channel Agility / revision-dependent reserved use
80x0100Spectrum Management
90x0200QoS
100x0400Short Slot Time
110x0800APSD
120x1000Radio Measurement
130x2000DSSS-OFDM / revision-dependent EPD or reserved use
140x4000Delayed Block Ack / revision-dependent reserved use
150x8000Immediate Block Ack / revision-dependent reserved use
Revision warning: the Capability Information field has evolved. Older analyzers and older 802.11 revisions label some bits differently from the newest non-DMG definitions. For modern captures, trust the analyzer’s standard-revision-aware decode, but the hex masks above are still useful for locating the set bits.

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.

RateNormal byteBasic-rate byte
1 Mb/s0x020x82
2 Mb/s0x040x84
5.5 Mb/s0x0B0x8B
6 Mb/s0x0C0x8C
9 Mb/s0x120x92
11 Mb/s0x160x96
12 Mb/s0x180x98
18 Mb/s0x240xA4
24 Mb/s0x300xB0
36 Mb/s0x480xC8
48 Mb/s0x600xE0
54 Mb/s0x6C0xEC
Example: 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 / fieldNumeric meaning
DTIM Count0 means this beacon is the DTIM; otherwise it is the number of beacon intervals remaining before the next DTIM.
DTIM PeriodUnsigned 8-bit period. 1 = every beacon, 2 = every second beacon, 3 = every third beacon, etc.
Bitmap Control bit 00x01 is the Traffic Indicator for buffered group-addressed traffic in the applicable DTIM context.
Bitmap Control bits 1–7Bitmap offset portion used to compress the Partial Virtual Bitmap.
Partial Virtual BitmapBits correspond to AID-related buffered-unicast indications after applying the bitmap offset rules.
Beacon field / IEWhat the value means in the field
Timestamp64-bit TSF timer value. Stations use timing synchronization functions to maintain a common time base inside the BSS.
Beacon IntervalAdvertised 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 InformationBit 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.
SSIDNetwork name, 0–32 octets. A zero-length/hidden SSID does not make the WLAN cryptographically secure.
Supported RatesLegacy 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 RatesAdditional legacy rate entries when they do not all fit in Supported Rates.
DS Parameter Set / ChannelLegacy 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.
TIMTraffic 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 CountNumber of beacon intervals until the next DTIM beacon. 0 means this beacon is a DTIM.
DTIM PeriodHow 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 BitmapCompressed indication of which Association IDs (AIDs) have unicast data buffered. Bit 0 also participates in signaling buffered broadcast/multicast traffic at DTIMs.
RSNRobust 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.
CountryRegulatory-country information and channel/power constraints. Useful when investigating domain mismatches.
ERP Information2.4 GHz 802.11g protection state, including whether non-ERP/legacy stations are present and whether protection mechanisms are required.
HT Capabilities / HT Operation802.11n features and current operation: channel width, MCS support, guard interval and related HT behavior.
VHT Capabilities / VHT Operation802.11ac capabilities and operating channel-width/center-channel information, spatial streams and VHT MCS support.
HE Capabilities / HE Operation802.11ax capabilities/operation including HE PHY/MAC parameters; captures may expose BSS Color and other HE-specific information.
EHT Capabilities / EHT Operation802.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 LoadMay 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 BSSIDAllows several BSS profiles to be represented more efficiently by a transmitting BSSID, reducing beacon/probe overhead in multi-SSID deployments.
Multi-Link / MLO elementsWi-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.
Important: Beacon values describe what the AP advertises, not necessarily what a particular client negotiated. To prove the client’s actual link, also inspect association/reassociation frames, data-frame PHY headers/radiotap metadata, and AP/client telemetry.

Roaming — 802.11r, 802.11k and 802.11v

802.11r — Fast BSS Transition (FT)
RoamingFast BSS TransitionMAC / SecurityVoice-friendly

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.

ItemMeaning
FTFast BSS Transition. The actual fast-roaming mechanism defined by 802.11r.
Mobility DomainA group of APs that participate in the same 802.11r roaming domain.
MDIDMobility Domain Identifier. A 16-bit value used to identify the FT mobility domain.
PMK-R0Top-level FT Pairwise Master Key material associated with the mobility domain.
PMK-R1Derived key material associated with a particular target AP/R1 key holder.
FT over-the-airThe client exchanges FT authentication directly with the target AP over the wireless medium.
FT over-the-DSThe client coordinates the FT exchange through the current AP/distribution system before moving to the target AP.

Key 802.11r beacon / association values

ElementNumeric valueField meaning
Mobility Domain IEElement ID 54 / 0x36Advertises the FT mobility domain and FT capability policy.
Mobility Domain ID2 octets / 16 bitsExample: 0x1234. APs intended for seamless FT roaming should advertise the same MDID.
FT Capability and Policy1 octetContains FT-related capability/policy bits including whether FT over the DS is supported.
Fast BSS Transition IEElement ID 55 / 0x37Carries FT authentication/key information during the FT exchange.
RSN AKM for FTFT-specific AKM suites appear in the RSN elementExamples include FT with 802.1X and FT with PSK/SAE depending on the network security design.
Field check: if the APs are intended to support 802.11r, look for the Mobility Domain IE (EID 54 / 0x36) and confirm the MDID is consistent across the roaming APs. Then verify the RSN element advertises an FT-capable AKM appropriate for the WLAN security mode.

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
Roaming supportNeighbor ReportsMeasurements

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.

FunctionWhat it does
Neighbor ReportProvides candidate AP/BSSID/channel information to reduce roam scanning time.
Radio measurementsSupports measurements related to channels, beacons and link conditions.
Roaming benefitCan reduce the time spent hunting for a target AP, especially in large multi-AP networks.
Think of 802.11k as “where should I look?” It assists discovery and measurement but does not itself perform the fast security transition.
802.11v — BSS Transition Management
Roaming supportBSS TransitionNetwork guidance

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.

FunctionWhat it means
BSS Transition Management RequestThe AP/network suggests that a client move, optionally providing candidate BSSs.
Client responseThe client may accept, reject or ignore the recommendation depending on implementation and policy.
Roaming benefitHelps steer clients away from overloaded or less-desirable APs.
Think of 802.11v as “the network recommends where to go.” It is guidance, not a forced roam.

How the roaming trio fits together

StandardField shorthandRole 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

SymptomLikely areaWhat to capture
Client stays on distant APClient roaming policy / RF overlapRSSI/SNR over time, neighbor reports, BSS transition requests.
Roam occurs but voice dropsAuthentication/reassociation delayAuthentication, reassociation, FT frames, packet-loss gap.
Long scan pause before roamCandidate discoveryProbe behavior, 802.11k neighbor reports, scan channels.
Network asks client to move but it does not802.11v/client policyBSS Transition Management Request/Response.
FT advertised but not usedClient compatibility/security configurationMobility Domain IE, RSN AKMs, authentication algorithm, reassociation exchange.
Important: good roaming is a combination of RF design, client behavior and protocol support. Even with 802.11k/v/r enabled, excessive overlap, weak target-cell signal or client-specific roaming thresholds can still cause sticky-client behavior.

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.

Estimated total path loss
— dB
Free-space path loss—
Material / wall loss—
Total estimated loss—
Estimated received powerEnter Tx power to calculate

SNR / SINR and likely MCS

Two calculator stages: Distance and wall entries above estimate received power. To use that estimate for MCS, enter AP transmit power; the calculation now updates automatically as distance or walls change; the received-power result will automatically feed the Signal (dBm) field below. You can also edit Signal manually. Watch the 'Illustrative MCS' value below. Without AP transmit power, distance alone cannot determine received signal, so MCS only changes when you edit the Signal/Noise/Interference fields.

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

Enter the noise floor as measured or assumed in a 20 MHz bandwidth. Thermal noise is about −174 dBm/Hz; a 20 MHz receiver with a ~9 dB noise figure sees roughly −92 dBm, an 80 MHz receiver about −86 dBm. Uncheck only if your entered value was already measured at the link width.

4 · PHY and device capabilities

Requested settings are limited by the AP and client capabilities.

5 · Adjacent-channel interference (optional)

Adjacent-channel interference — optional modeling inputs (Version 22)

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.

Adjacent interferers disabled; existing SINR behavior preserved.

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.

v28 baseline: Operating band is controlled above in the RF Loss Calculator.

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.

Live nominal spectrum visualization

AP A and AP B occupy the indicated frequency intervals. The amber region indicates shared nominal spectrum, not measured interference.

Illustrative received interference coupling — AP B into AP A

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.

Disabled — Live Link uses existing inputs only. To enable, clear the separate Co-channel interference input; the two sources are mutually exclusive to avoid double-counting. The 2.4 GHz adjacent-channel inputs are ignored when 5/6 GHz is selected.

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.

Live link calculations
SNR
32.00 dB
SINR
32.00 dB
MCS estimate
10
Predicted PHY rate
— Mb/s
Initial values: signal −60 dBm, noise −92 dBm (20 MHz reference), no interference.
Calculating…
Channel-width capability: Enter the maximum channel width supported by the AP and client for the band and direction being estimated. The PHY rate uses the minimum of the requested width and both limits. Defaults are permissive placeholders, not verified device capabilities. The model does not verify channel availability, puncturing, or regulatory permissions.
Spatial-stream capability: Enter the AP and client maximum spatial streams for the direction being estimated. The calculator uses the lowest of the requested NSS and those two limits. Defaults of 4 are permissive placeholders, not verified equipment capabilities.
802.11n MCS convention: For HT (Wi-Fi 4), the calculator displays both the per-stream modulation/coding MCS (0–7) and the conventional HT MCS index (0–31), which includes the number of spatial streams. AP/client MCS ceiling inputs use the per-stream 0–7 scale for 802.11n. For Wi-Fi 5/6/7, MCS and NSS are reported separately.
Predicted bit rate means PHY link rate, not TCP/UDP throughput. It uses the estimated MCS, channel width, spatial streams, and a simplified symbol-time model. For HT/VHT, select either 0.8 µs long GI or 0.4 µs short GI; for HE/EHT, select 0.8, 1.6, or 3.2 µs GI. The rate is approximate and does not subtract MAC overhead, contention, retries, or aggregation inefficiencies. Changing PHY generation automatically limits the channel-width choices to those supported by that generation, selecting the nearest lower supported width when necessary. Effective channel width and NSS are each limited to the minimum of requested and AP/client capability values. This is a single-direction PHY estimate; verify bandwidth and directional Tx/Rx capabilities for actual equipment.
Engineering limitation: No IEEE-standard universal SINR-to-MCS threshold table exists. The displayed MCS is a planning heuristic, not a prediction guaranteed for any chipset. Association negotiates capabilities, not a fixed operating MCS. Each transmitter independently adapts its rate based on packet success, retries and RF conditions. Same-channel Wi-Fi transmissions that defer cleanly mainly cause airtime contention, not a constant interference power.

Formula

FSPL (dB) = 20 log₁₀(distance km) + 20 log₁₀(frequency MHz) + 32.44
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.

MaterialPlanning rangeComments
Drywall / sheetrock~2–4 dBCan be higher with insulation, plumbing, tile or metal studs.
Wood / plywood~3–6 dBMoisture content matters.
Interior glass~3–6 dBOrdinary glass is usually modest loss.
Brick~6–12 dBThickness and moisture strongly affect loss.
Concrete block / CMU~8–15 dBFilled cells/rebar can increase attenuation.
Reinforced concrete~10–20+ dBRebar and thickness can make loss severe.
Low-E / metallized glass~10–30+ dBMetallic coating can attenuate Wi-Fi dramatically.
Foil-faced insulation~15–30+ dBCan behave like an RF shield.
Metal wall / sheet metal~20–40+ dBMay block direct path almost completely; openings dominate.
Important field limitation: indoor RF is not simply “distance + wall dB.” Reflections, diffraction, multipath, wall angle, AP/client antenna orientation, people, shelving, machinery, and adjacent floors can change the result substantially. Use this calculator for planning and sanity checks, then validate with measured RSSI/SNR and throughput at the actual location.

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 conditionLikely effectWhat to measure
High same-channel utilization, low retry rateMostly contention: higher latency and lower throughput even with clean RF.Channel utilization, airtime, queue delay, busy time.
High utilization + high retriesContention plus collisions/interference/hidden nodes.Retries, failed frames, ACK loss, client SNR, hidden-node geometry.
High RSSI but poor throughputOften congestion/CCI, not lack of signal.MCS, airtime share, utilization, retries, neighboring BSSs.
Low PHY rate client in busy BSSLarge airtime cost; impacts everyone.Per-client airtime, MCS/NSS, bytes vs airtime.
Wide 80/160/320 MHz channel in dense areaMore chance of overlapping another BSS; fewer independent channel choices.Primary/secondary channel occupancy and puncturing where supported.
Field rule: Do not diagnose Wi-Fi capacity from RSSI alone. Record RSSI/SNR + negotiated MCS/NSS + channel width + channel utilization + retries + airtime + latency distribution. That combination separates weak-signal problems from same-channel contention far more reliably.

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.

SpecPurpose
802.11dRegulatory-domain / country information support.
802.11eQoS enhancements; foundation for WMM-style prioritized access.
802.11hSpectrum management in 5 GHz, including DFS/TPC concepts.
802.11iRobust security enhancements; foundation associated with WPA2/RSN.
802.11kRadio Resource Measurement; neighbor and measurement information used by roaming/optimization systems.
802.11rFast BSS Transition (FT), the primary IEEE fast-roaming amendment.
802.11uInterworking with external networks; network discovery/selection information.
802.11vWireless Network Management, including BSS Transition Management used for roaming guidance.
802.11wProtected Management Frames.
802.11aiFast Initial Link Setup.
802.11azNext-generation positioning / enhanced ranging.
802.11bfWLAN sensing enhancements using supported Wi-Fi PHYs.
802.11bk320 MHz positioning enhancements based on EHT/802.11be capabilities.

Modulation & rate terms

BPSK1 bit per modulation symbol; robust, low spectral efficiency. QPSK2 bits per symbol. 16-QAM4 bits per symbol. 64-QAM6 bits per symbol. 256-QAM8 bits per symbol. 1024-QAM10 bits per symbol; requires cleaner RF/higher SNR. 4096-QAM12 bits per symbol; highest EHT constellation, requiring excellent link quality. OFDMSplits data across many orthogonal subcarriers. OFDMASchedules subsets of OFDM subcarriers (Resource Units) to different users. MCSModulation and Coding Scheme index: shorthand for constellation, code rate and PHY-specific parameters. NSSNumber of spatial streams. More streams can increase PHY rate when both ends and the RF channel support them. GIGuard Interval. Shorter GI improves rate but leaves less timing margin for multipath. PHY rateRaw over-the-air signaling rate. It is not application throughput. Basic RateA legacy rate a station must support to participate in a BSS; often used for management/control transmission policy. RSSIReceived signal-strength indication; device-dependent measurement of received power. SNRSignal-to-noise ratio. High-order QAM generally needs higher SNR/EVM quality. AirtimeActual time the channel is occupied. For capacity analysis, airtime is often more revealing than byte count.

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 / modelPublished transmit powerPublished antenna gainDefinition / source
Cisco Catalyst 9130AXIAvailable 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-635Consult radio-specific conducted-power and regulatory tables; not directly comparable herePeak 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 ProMax 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 R550Peak 26 dBm (2.4 GHz); 25 dBm (5 GHz)Up to 3 dBiPeak 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 modeMCS 0MCS 7MCS 11
2.4 GHz HE20−97 dBm−78 dBm−67 dBm
2.4 GHz HE40−94 dBm−75 dBm−64 dBm
5 GHz HE80See full datasheetSee full datasheetSee 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 locationUsually visibleNot normally visible
AP uplink / switch SPAN or TAPEthernet/IP traffic forwarded to or from AP, VLAN tags if present at capture point, DHCP, DNS, TCP, UDP, tunneled AP traffic802.11 beacons, probe exchanges, RF retries, radio RSSI, management/control frames
Wireless adapter in monitor mode, tuned to target channel802.11 management/control/data frames and sometimes radiotap RSSI/channel metadata, subject to adapter/driver supportDecrypted application payload without suitable keys and decryption setup; traffic on other channels not monitored
Controller/gateway uplinkTraffic exposed at that interface; may be tunneled or already decapsulatedOver-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

ObjectiveCapture filterField note
All traffic involving a known AP management IPhost 192.0.2.10Only packets with that IP; will not capture all bridged client traffic
One client IPhost 192.0.2.25Use actual client IP; routed/tunneled paths may hide it
DHCPv4udp port 67 or udp port 68Captures BOOTP/DHCPv4 exchanges
DNS over conventional port 53port 53TCP and UDP; excludes encrypted DNS on other ports
ARParpIPv4 address-resolution frames on Ethernet
ICMP / ping (IPv4)icmpDoes not include ICMPv6
HTTPS on TCP 443tcp port 443Excludes QUIC/HTTP3 over UDP 443
TCP or UDP 443port 443Includes TCP and UDP
Traffic on a VLAN (tag visible)vlan 100Only works if capture retains 802.1Q tag; offload/SPAN may affect visibility
Client MAC on Ethernetether host 02:11:22:33:44:55Works 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

QuestionWireshark display filter
Packets involving one client IPv4ip.addr == 192.0.2.25
Packets involving one client IPv6ipv6.addr == 2001:db8::25
DHCPv4 discovery / lease trafficbootp
DNS queries and responsesdns
DNS responses indicating errordns.flags.rcode != 0
ARP trafficarp
IPv6 neighbor discoveryicmpv6.type == 135 || icmpv6.type == 136
TCP connection setup (SYN without ACK)tcp.flags.syn == 1 && tcp.flags.ack == 0
TCP retransmission analysistcp.analysis.retransmission || tcp.analysis.fast_retransmission
TCP duplicate ACK indicationstcp.analysis.duplicate_ack
TCP reset framestcp.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 443tcp.port == 443 || udp.port == 443
QUIC when decoded as QUICquic

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

QuestionWireshark display filterNote
Beaconswlan.fc.type_subtype == 0x08Beacon management frames
Probe requestswlan.fc.type_subtype == 0x04Client discovery attempts
Probe responseswlan.fc.type_subtype == 0x05AP discovery responses
Authentication frameswlan.fc.type_subtype == 0x0b802.11 authentication, not all higher-layer authentication
Association requestswlan.fc.type_subtype == 0x00Client association attempt
Reassociation requestswlan.fc.type_subtype == 0x02Useful for roaming analysis
Deauthentication frameswlan.fc.type_subtype == 0x0cInspect reason code and protected management frame context
Disassociation frameswlan.fc.type_subtype == 0x0aInspect reason code
Frames marked retrywlan.fc.retry == 1802.11 MAC retry bit; requires 802.11 capture
EAPOL handshake frameseapolOften visible before data decryption
One BSSIDwlan.bssid == 02:11:22:33:44:55Replace example with actual BSSID
One station MACwlan.addr == 02:11:22:33:44:55Matches 802.11 address fields
RSSI at or below −75 dBm (if radiotap supplies it)radiotap.dbm_antsignal <= -75Driver-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

  1. Define the question: association/roaming, DHCP, DNS, application delay, TCP loss, or RF retries.
  2. Choose the observation point: SPAN/TAP on AP uplink for forwarded client traffic; monitor-mode radio for over-the-air management and retransmission evidence.
  3. Begin broad: initially avoid restrictive capture filters so you do not discard relevant evidence.
  4. Capture a timestamped baseline: record AP, SSID, VLAN, client MAC/IP, channel, width, test time, and whether traffic is bridged or tunneled.
  5. Apply display filters: isolate DHCP, DNS, TCP setup/retransmissions, roaming events or retries, as appropriate.
  6. Correlate: compare wired trace, wireless trace, AP counters and client telemetry; align clocks before attributing delays to RF.
  7. 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.