• About Me
  • Craft & Code
    • Linux Commands
    • JNCIE-SEC - Training
  • 802.11 - Airbender
    • 802.11 - Just Roaming
    • 802.11 - WEP -> WPA3
    • 802.11 - the 802.1X Story
    • 802.11 - Survey´s
    • 802.11 - Design Fails
    • 802.11 - The Wave
    • 802.11 - Modulation P.1
    • 802.11 - Modulation P.2
    • 802.11 - Shark's Filtered
    • 802.11 - Design Guideline
    • 802.11 - Secure Wifi
    • 802.11 - Wi-Fi 7
    • 802.11 - The Amendments
    • 802.11 - Wi-Fi 8
    • 802.11 - Antennas
    • 802.11 - MLO
    • 802.11 - Frequency Puncturing
    • 802.11 - EBR
    • 802.11 - Radar Love (DFS)
    • 802.11 - SCS
    • 802.11 - OFDMA - Eva Santos Edition
    • 802.11 - DMG
    • 802.11 - EDMG
    • CWNE-Sticker-Gen
  • an IoT blog
    • IoT - Radio Pond
    • IoT - Technology
klick.us
Enrico Aderhold
  1. You are here:  
  2. Home
  3. 802.11 - Airbender

802.11 - EDMG

802.11ay – EDMG: Because 60 GHz wasn’t crazy enough

So first we got 802.11ad and thought, “Cool, gigabit Wi‑Fi with beams and lasers.” But then IEEE said, “Hold my spectrum,” and dropped 802.11ay — aka Enhanced Directional Multi-Gigabit (EDMG). This one doesn’t just dip a toe into 60 GHz... it cannonballs into it.

Let’s talk spectrum madness

EDMG still lives in the 60 GHz band, which is kind of like the outer edge of Wi‑Fi sanity. Short range. No walls. Oxygen laughs at it. But it’s fast. Really fast.

We’re not doing 20 MHz or 80 MHz here. We’re throwing entire GHz at the problem:

  • 4.32 GHz PPDUs – like bundling two 2.16 GHz streams together
  • 8.64 GHz PPDUs – stack four of 'em, just for fun
  • Duplicate Transmissions – EDMG lets you clone your 2.16 GHz PPDU across multiple adjacent channels like it’s building Wi‑Fi Voltron

These monsters are all defined in Clause 28 – the wildest part of the 802.11 standard. Think of it as the black-ops section for Wi‑Fi PHY engineers who live off Red Bull and RF burns.

What makes EDMG different?

802.11ad was directional. EDMG is extra directional. It doesn’t just point antennas – it weaponizes them. Beamforming is baked in. Everything must be precise. No multipath welcome. You either hit the target or you don’t transmit.

Also, unlike older standards, you’re not dealing with MHz-level granularity. This is GHz Wi‑Fi. It’s like moving from water pistols to pressure washers.

MAC’s still doing its best

The MAC layer under EDMG is holding on for dear life. It reuses a lot from DMG (802.11ad) but needs to keep up with:

  • Insane aggregation sizes – EDMG PPDUs must include EOF Padding when packing in those A-MPDUs
  • Capability signaling – still using that old DMG Capabilities element, but now with EDMG superpowers
  • PHY type flag – in the MIB, it proudly wears the number 15. If your device has it, congrats, you're EDMG-ready

Secure Ranging – Wi‑Fi gets spooky accurate

Now this is cool: EDMG doesn’t just blast bits – it also does ranging with PHY-level security. That means secure training fields inside the PPDU that let your AP say, “You’re definitely 3.4 meters away, and I’m sure of it.”

Great for presence detection, indoor tracking, and freaking out your cat.

Why this matters (or doesn't)

Let’s be honest: 60 GHz Wi‑Fi isn’t for everyone. If your house has more than one wall or you're trying to game in the basement, forget it.

But if you want uncompressed 8K video over the air, at short range, in a line-of-sight studio setup, EDMG is your jam. It’s not mainstream – it’s Millimeter-Wave Punk Rock Wi‑Fi.

Also, you get to say things like “my PPDU spans 8.64 GHz,” and that's worth something.

802.11ay = EDMG = Wi‑Fi that says screw your drywall.
Huge channels, tight beams, secure ranging, and duplicate transmissions like it's cloning RF sheep. It’s not Wi‑Fi for the masses – it’s Wi‑Fi for the brave.

Details
Written by: Enrico Aderhold
Created: 25 September 2025

802.11 - DMG

802.11ad – when Wi‑Fi said "to hell with walls"

First, we played with 2.4 GHz – the neighborhood walkie-talkie band. Then came 5 GHz – finally some speed and less microwave oven drama. Then 6 GHz showed up like a slick younger cousin with fresh spectrum and clean air.

But now? Now we’re talking 60 GHz. Holy cow. That’s not Wi‑Fi – that’s laser tag with bits.

Welcome to DMG – Directional Multi-Gigabit Wi‑Fi

This is 802.11ad, aka DMG. It lives in the 60 GHz band and does one thing really well: short-range, high-speed, line-of-sight data blaster action. We’re talking up to 7 Gbps. But blink too hard or move behind a couch? Boom – connection gone.

PHY Layer: Directional or Die

The PHY in 802.11ad is obsessed with directionality. This ain’t omnidirectional party Wi‑Fi. It’s laser-focused, beamformed, antenna-steering wizardry. It needs:

  • A clean line of sight (good luck in your grandma’s concrete house)
  • Beamforming just to stay connected when you breathe wrong
  • Custom PPDUs designed for DMG operation – no regular Wi‑Fi handshake here

MAC Layer: Grown-Up Framing and Beam Chit-Chat

MAC gets a glow-up too. DMG adds new elements to management frames – because this stuff ain’t plug and play. Devices need to negotiate capabilities, angles, and sometimes their life choices:

  • DMG Capabilities Element – says what the device can do at 60 GHz
  • DMG Operation Element – tells others what it’s currently doing
  • Beacon Interval Control – because even high-speed Wi‑Fi needs to say "hi" sometimes

We also got Action frames like:

  • Channel Switch Announcements – radar incoming? switch now
  • Measurement Requests – is this channel even alive?
  • Power Constraint Frames – you're in Europe now, tone it down

IBSS Mode – who’s the DFS boss?

In peer-to-peer (IBSS) setups, one device becomes the DFS Owner. That’s right – Wi‑Fi Lord of the Rings. If radar shows up, this dude picks a new channel. Except... if two think they’re the owner? Then it's Thunderdome.

EDMG – the sequel with more GHz

Like any good sequel, 802.11ad got an upgrade: EDMG. Now we can do crazy stuff like:

  • 4.32 GHz and 8.64 GHz PPDUs – because 2.16 GHz just wasn't enough
  • Duplicate transmission across multiple bands – copy-paste your signal like a champ
  • Still beamformed, still fragile as glass, but hey – fast AF

So should you care?

If you want to shoot 8K video wirelessly across the room (and only across the room), yes. If you live in a castle with 50 cm stone walls – forget it. DMG is Wi‑Fi for short-range laser missions. No prisoners. No mercy. No multipath. No walls.

802.11ad is Wi‑Fi’s midlife crisis: faster car, higher frequency, and zero tolerance for obstacles. But damn, when it works – it flies.

Details
Written by: Enrico Aderhold
Created: 25 September 2025

802.11 - OFDMA

OFDMA and Curly Hair – A Surprisingly Accurate Analogy

 

In honor of Eva Santos – whose spirit echoes in every signal we shape.

 

Imagine a crowded hair salon: one head, many ringlets, and several stylists working in parallel. That’s OFDMA in a nutshell. Let’s break it down:

WLAN Concept Curly Hair Analogy Explanation
Total Channel Bandwidth The Entire Head of Hair This is your full 20, 40, or 80 MHz channel. In old-school OFDM, one user gets the whole head to themselves – no sharing.
OFDM Styling the Entire Head Only one client can use the entire frequency spectrum at a time – like one stylist doing the whole head alone.
OFDMA Styling Individual Ringlets OFDMA slices the channel into smaller “Resource Units” (RUs) – like dividing curls into distinct ringlets. Stylists can work in parallel.
Resource Units (RUs) Individual Curls Each RU is a group of subcarriers assigned to a client – non-overlapping and isolated. Just like a stylist working a single curl without messing up the rest.
Multiple Clients (A, B, C) Multiple Stylists OFDMA enables multiple users to transmit/receive at once, each on their own curl. No queueing, less wait, more throughput.
Different Transmit Power Different Styling Products The AP can apply high power to some RUs and low power to others – like strong gel for distant curls and light mousse for close strands.

 

OFDMA Under the Hood – Deep Dive

Orthogonal Frequency Division Multiple Access is Wi‑Fi’s modern answer to traffic jams. Instead of one car at a time on the highway (OFDM), we now get many lanes, many drivers, all at once.

1. From OFDM to OFDMA

  • OFDM: One STA owns the full channel bandwidth for the entire transmission window.
  • OFDMA: The same frequency band is sliced into RUs. Each user gets their own lane to drive down – no collisions.

2. Resource Units (RUs)

Each RU = a fixed chunk of subcarriers. These are dynamically allocated per PPDU:

  • In 20 MHz: RU sizes are typically 26, 52, 106, 242 tones.
  • In 80 MHz: You can go up to 996-tone RUs or multiple smaller ones.
  • HE PPDU: An HE OFDMA PPDU must have at least one RU smaller than the full channel (i.e., not the whole highway).

3. Multi-User Access & Power Control

What makes OFDMA awesome isn’t just slicing the pie – it’s deciding how to serve it:

  • DL and UL Support: Access Point allocates RUs downlink; clients can reply uplink using their own RUs.
  • Per-RU Power Control: Different clients, different path loss, different power. The AP compensates smartly.
  • Combining with MIMO: RUs can carry:
    • SISO (one stream)
    • SU-MIMO (multiple streams to one user)
    • MU-MIMO (multiple streams to many users)
    • Or all of the above – in one PPDU. Yes, really.

4. What Happens Inside the PHY

The PHY layer does some serious signal gymnastics to pull this off:

  1. Stream Parsing & Mapping: Assign bits to modulation symbols.
  2. Encoding: Either BCC or LDPC, depending on config.
  3. Tone Mapping: For LDPC, assign symbols to specific tones/subcarriers.
  4. Spatial Mapping: Apply MIMO matrix (Q-matrix). Combine streams as needed.
  5. IDFT: Convert from frequency domain to time domain using inverse DFT. All RU signals get combined here.
  6. GI & Windowing: Add guard interval, apply windowing to reduce spectral side-lobes. Then it's RF time.

Why OFDMA Rocks in Real Life

In dense networks – schools, stadiums, offices, coffee shops – OFDMA cuts latency, improves throughput, and makes Wi‑Fi feel less like dial-up roulette. It’s not just a PHY trick. It’s airtime democracy.

Instead of users screaming one at a time, they whisper in harmony – each on their own beautiful curl of spectrum.

Details
Written by: Enrico Aderhold
Created: 25 September 2025

802.11 - DFS

Dynamic Frequency Selection in 5 GHz Wi-Fi

On DFS channels, an access point checks for radar before transmitting and must leave the channel if it detects radar during operation. For a WLAN designer, that makes channel changes and client reconnection part of the design.

What is DFS (Dynamic Frequency Selection)?

DFS is Wi‑Fi’s way of staying out of trouble – mostly with military-grade radar systems that have been using 5 GHz long before your APs were even a thing. It’s baked into IEEE 802.11 to detect radar activity and dynamically vacate or avoid certain frequencies.

So whenever you hear DFS, think: “We’re operating in shared spectrum. We better behave.”

Why and When DFS is Required

In regulatory domains (hello FCC, ETSI), Wi-Fi gear must comply with DFS rules when operating in certain 5 GHz bands. That’s when the management attribute dot11SpectrumManagementRequired is set to true.

But it’s not just about radar. DFS can also help with automatic channel planning, avoiding congestion, and interference reduction – even when not strictly required by law.

Core DFS Mechanics – How It Works

  • Radar Detection: The AP or STA listens for radar patterns before and during operation on a channel.
  • Channel Quieting: The AP can “quiet down” a channel for clean listening, reducing chatter to better detect radar.
  • Discontinue Operation: If radar is detected, you must immediately stop using that frequency. No excuses. It’s the law.
  • Channel Selection: Once you bounce, you have to find a new channel and tell everyone where you’re going.
  • Measurement & Reporting: Devices can request/perform signal checks across channels – think of it like recon before moving.
  • Association Rules: Clients can only associate based on supported DFS channels – that list matters, especially when dot11SpectrumManagementRequired is true.

DFS Owner in IBSS (Ad-Hoc Networks)

In Independent BSS (IBSS), there’s no central AP, so one STA becomes the DFS Owner. Their job?

  • Choose the next channel if radar shows up
  • Coordinate recovery across the group
  • Respect the DFS Recovery Interval (so you don’t hop channels too fast)

But there’s a catch: you can’t guarantee a single DFS Owner exists at all times. That’s why IBSS DFS has to be robust and semi-autonomous.

Frames Used in DFS – How Devices Talk About It

DFS isn’t magic – it’s all managed through specific IEEE 802.11 management frames. Here’s who’s talking and what they’re saying:

  • Channel Switch Announcement
    Type: Spectrum Management Action Frame
    Used by: AP or STA
    Why: To say “Heads up, we’re changing the channel – radar’s in town.”
  • Extended Channel Switch Announcement
    Type: Public Action Frame
    Used for: More complex switch scenarios, like multi-AP coordination.
  • DSE Measurement Request/Report
    Type: Public Action Frame
    Used for: Measuring signal strength, radar presence, interference – all that jazz.
  • Channel Availability Query
    Type: Public Action Frame
    Why: “Hey, is this channel clean?”
  • DSE Power Constraint
    Type: Public Action Frame
    Used to: Enforce regulatory power limits in DFS zones (sometimes you gotta lower the volume).
  • DCS Measurement Request/Response
    Type: Public Action Frame
    Related to: Dynamic Channel Selection (DCS) – a sibling of DFS, handling broader channel management strategies.
  • Probe Request/Response
    Type: Management Frame
    Why it matters: Clients looking for APs in DFS areas must declare their supported channels. The AP checks this before allowing association.

Why DFS Matters

If you’re running Wi-Fi in the 5 GHz band (and most of us are), DFS is that quiet guardian in the background making sure you don’t accidentally jam NATO radar. It’s not optional if you’re in regulated bands – and if you’re building enterprise or mission-critical networks, you better understand it fully.

DFS is the grown-up part of Wi-Fi. It’s what separates the home gamer from the wireless warrior.

Details
Written by: Enrico Aderhold
Created: 25 September 2025

802.11 - Spatially Constrained Service

What the heck is SCS (Spatially Constrained Service)?

Okay, this one’s for the latency junkies. SCS is a new trick from the Wi-Fi 7 (EHT) playbook. It’s designed for traffic that can’t wait. Think VR, AR, industrial robots doing salsa in real time – stuff where delay is death.

Basically, SCS says: “Let’s treat some traffic like royalty and make sure it gets through the wireless mess fast and predictable.” That means low latency and low jitter – every time.

SCS Needs MLDs (Multi-Link Devices)

SCS isn’t just some fancy QoS tag – it’s a full-on service class that only works if both ends of the party speak MLD (Multi-Link Device). It’s an optional feature, defined in section 35.17 of the standard – but if you're building for serious Wi-Fi 7, it’s not optional in practice.

How SCS Tells You It's There

Devices advertise their SCS superpowers using specific flags in their IEs (Information Elements). Here’s the gist:

  • Non-AP EHT STA says “Hey, I can send SCS Requests”
  • EHT AP says “Cool, I can answer those with SCS Responses”
  • They both use something called the SCS Descriptor element (ID 185) to define the stream and its latency-hungry properties

This SCS Descriptor includes a QoS Characteristics Element – the part that tells the AP exactly how tight those latency demands are.

SCS Setup – The Talk Before the Dance

Getting SCS rolling means a little negotiation between client and AP:

  •  The client sends an SCS Request frame
  •  The AP replies with an SCS Response frame

Simple handshake, but the magic’s in the details: for periodic traffic with funky intervals (like 1/60 seconds), the non-AP STA can send updates to adjust the service start time – same SCSID, different flavor.

If the AP says yes, it has to process traffic that matches that SCS contract. That means matching frames against TCLAS rules (Traffic Classification filters). If it matches, it gets the QoS velvet rope.

And if the stream is Downlink-only, and there’s no QoS element in the SCS descriptor, that’s okay too – still gets processed, still gets loved.

When SCS Gets Rejected or Killed

Sometimes, things go south. Maybe the AP’s like, “Nope, can’t give you that much latency love.” In that case:

  • It sends back an SCS Response with status = TCLAS_PROCESSING_TERMINATED
  • No QoS Characteristics included in that response – you get the cold shoulder

 

SCS is like RSVP for wireless: you tell the AP what kind of service you need, and if it’s got the juice, it delivers. But it’s picky – you need MLDs, you need the descriptors, and you need everything lined up tight.

If you’re building real-time stuff in Wi-Fi 7 – or just want to act like you are – you better know how to talk SCS. Because this is the future of predictable low-latency Wi-Fi.

Details
Written by: Enrico Aderhold
Created: 25 September 2025

802.11 - EBR

What’s Up With the EBR Element?

Alright, here’s the deal. The Expedited Bandwidth Request (EBR) element ain’t in every frame – it’s an optional part of the 802.11 spec, but when it shows up, it means business. This thing is all about telling the AP, “Yo, I got traffic and it’s hot – make room!”

Why EBR Even Exists

The EBR is basically a tiny flag inside a frame that says: “Hey AP, this TSPEC request I’m sending? It’s kind of a big deal.” You’ll mostly find it mentioned in the deep corners of the spec – stuff like interworking with external networks and even emergency call support. So yeah, we’re not talking about your average cat video stream here.

When and Where It Shows Up

  • Sender → Receiver? Comes from a non-AP STA and hits the AP. It’s the STA that says, “I need that QoS hookup.”
  • Frame Type? Sits inside an ADDTS Request frame. If the STA’s trying to lock in a Traffic Stream (TS), this is where EBR gets its ride.
  • Optional? Yep – but only if dot11EBRActivated = true on that STA. If not, forget it. No EBR allowed.
  • Needs TSPEC? 100%. You can’t send an EBR without a TSPEC. They’re a package deal.
  • One Per Frame? Always. No double-dipping. Just one EBR per ADDTS.

What’s Inside This Thing?

EBR uses the classic 802.11 IE format. You’ve seen it before: Element ID, Length, then the actual content – which in this case is just one field:

  • Precedence Level – That’s the key. A single byte that tells the AP how urgent this traffic is. Higher value? More urgent. Plain and simple.

No fuss. No drama. Just a straight-up “hey I need this stream handled like, now.” The AP reads that level and decides whether to grant you your golden slice of airtime.

Real Talk: When Would You Actually Use This?

Imagine your STA is about to make a voice call, or start an emergency alarm flow, or do anything time-critical. That’s when you might toss in the EBR. It’s like waving a little priority flag at the AP and saying, “Don’t throw me in the best-effort queue, bro.”

So yeah – not for every TS. But when it counts, the EBR’s the guy you want backing you up.

Details
Written by: Enrico Aderhold
Created: 25 September 2025

802.11 - MLO

Multi-Link Operation (MLO) – One Wi-Fi, Many Radios

MLO is the fresh stuff – the kind of thing that changes how radios talk. Defined in EHT (802.11be), this thing lets Wi-Fi devices chat over multiple links – same band, different bands, same time, different time. You get the idea. It's like the difference between juggling one ball and spinning five at once. Smarter, faster, more chaotic if you mess it up.

What is an MLD?

MLD = Multi-Link Device. There’s two kinds you care about:

  • AP MLD: The boss. It manages multiple APs on different channels.
  • non-AP MLD: The client. That’s your phone, your laptop – it joins up with the AP MLD and can do cool multi-link stuff… if it’s built right.

One non-AP MLD can only be linked to one AP MLD at a time. The client always starts the dance by associating.

Upper MAC Does the Heavy Lifting

The MLD’s upper MAC (yes, there’s one upper, many lowers) has a bunch of jobs:

  • Association & Auth – Gets the whole relationship started.
  • Security – Handles PTK/GTK/IGTK/BIGTK, including PMKSA stuff per link.
  • Sequence Numbers – Keeps track of frame counters across links. One 48-bit PN for unicast with PTKSA. Same SN logic for group frames.
  • TTLM (TID-to-Link Mapping) – Chooses which link gets which traffic stream. Important stuff.
  • Aggregation – Reassembles MPDUs that came from different links.
  • In-order Delivery – Makes sure packets show up in the right order. Even if they came from different radios.

How MLO Gets Set Up

When you wanna join an AP MLD, your non-AP MLD needs to include the Basic Multi-Link element in its Association Request. No excuses. That element says “I’m multi-link capable and here’s my setup.”

Also, all APs under the same AP MLD need to advertise the same RSNE – except for a few fields (AKM Suite List and MFPR bit can differ). They all need to share at least one AKM suite though.

Wanna change stuff later? There’s a Reconfiguration Multi-Link element for that. Use it to add or remove links as needed. Flexibility, baby.

Link Management – Who Talks Where?

TID-to-Link Mapping (TTLM)

Decides what stream (TID) goes over which link. It can be set manually, negotiated, or adjusted on the fly. The AP MLD should be smart about this – consider client radio types, if it's single-radio, power constraints, etc.

STR vs NSTR – Simultaneous or Not?

If your device can transmit and receive on multiple links at the same time, that’s STR. If not, it’s NSTR. Your MLD tells the AP MLD this by flipping bits in the NSTR Indication Bitmap in the Basic Multi-Link element:

  • 0 = STR
  • 1 = NSTR

This matters for scheduling – the AP can’t expect you to TX and RX on two links at once if you’re NSTR.

Block Ack in MLO

When two MLDs agree on Block Ack, there’s one shared scoreboard context per TID – but each link can run in full-state or partial-state mode. Keeps it tidy but flexible.

MLO Power Management – Don’t Burn Your Radios

Multi-link needs multi-power-smarts:

  • Listen Interval – Says how often at least one STA in the MLD wakes up to catch beacons.
  • Max Idle – This timeout is applied at the MLD level. As long as the whole MLD isn’t idle past that, you’re good.
  • More Data Subfield – If the AP has more data for you on a specific link, it marks this bit in the frame. No guessing needed.

Why MLO is a Gamechanger

  • One STA, multiple radios, multiple links.
  • Different bands? Sure. Same band? Also fine.
  • Reorder packets, secure per-link, map TID to link, merge frames. All good.
  • MLO isn’t just about speed. It’s about flexibility, resiliency, and spectral efficiency.

MLO isn’t optional for high-performance Wi-Fi anymore. If your device can’t do it, it’s already falling behind. And if you're designing for it – get that upper MAC tight, that TTLM logic solid, and make sure your NSTR/STR flag is dead honest.

Details
Written by: Enrico Aderhold
Created: 25 September 2025

802.11 - Frequency Puncturing or Channel Puncturing

Puncturing in WLAN PHY – What It Really Means

Let’s get this out of the way first: “puncturing” is one of those terms that sounds like you're breaking something. And in a way – you are. You’re chopping out parts of a signal (either in time or frequency) to make the whole thing fit better – either for performance, compatibility, or because the real world just isn’t clean and perfect.

1. Coding-Time Puncturing – Dropping Bits on Purpose

In older and current OFDM PHYs (think 802.11a/n/ac/ax), data is first encoded with a convolutional encoder, typically at a base rate like R = 1/2. Now, if you want to increase the data rate (but keep some error protection), you don’t re-encode – you just skip some of the encoded bits. That’s puncturing. You remove bits according to a pre-defined pattern. Receiver knows that, fills in the blanks (kind of) with soft-decision decoding.

Why? Because we want higher throughput but don’t want to rebuild the whole modulation scheme. Smart hack.

2. Channel Puncturing – Cutting Frequency Holes

Welcome to HE (802.11ax) and EHT (802.11be). We’re working with big channel widths – 80, 160, 320 MHz. But sometimes, parts of that spectrum are full of garbage (interference, DFS, legacy neighbors, or region restrictions). What do we do? We puncture the bad subchannels. Just don’t use them.

Granularity:

  • 20 MHz chunks are the base unit for everything up to 160 MHz
  • 40 MHz chunks when working with 320 MHz

This isn't just "don’t transmit there". The PPDU actually tells the receiver what's being used and what's not – encoded in fields like U-SIG, Bandwidth Indication, and Punctured Channel Information.

3. Preamble Puncturing – Yes, Even the Header Gets Poked

Sometimes it’s not just the data payload – we need to puncture the preamble too. This makes things trickier, because that’s what tells everyone “Hey! I’m transmitting!”

Special modes like HE-CBW-PUNC80-SEC and HE-CBW-PUNC160-PRI20 describe exactly which 20 MHz pieces get cut. And the spectral mask – the shape of your transmission in frequency domain – needs to reflect this. No leaking into forbidden zones.

If two masks (main + puncture) define limits, take the stricter one.

4. Punctured Sounding – Only Beamform What Matters

In beamforming (Sounding, NDP), feedback isn’t useful for parts of the channel we’re not even using. So we tell the receiver “Hey, don’t bother sending CSI for these punctured parts.”

How?

  • HE: Use the Disallowed Subchannel Bitmap in the HE NDP Announcement.
  • Beamformee echoes that in the feedback.
  • EHT: Even tighter. If a subchannel is punctured in U-SIG, it’s off-limits. No feedback requested or allowed.
  • 242-tone RUs overlapping with punctured 20 MHz chunks? Also ignored.

5. Impact on Channel Access – CCA & RTS/CTS Game

When you receive an RTS on a channel that might include punctured bits, you can’t just respond. You need to make sure that all nonpunctured 20 MHz subchannels were clear (CCA idle) for a full PIFS duration before answering with CTS.

Why? Because someone else might be using one of those side channels, and they didn’t hear your RTS if it was punctured. Play fair.

Remember

  • PHY coding puncturing: drop coded bits to get better rates, decoder fills the gaps.
  • Frequency puncturing: skip bad subchannels (interference, DFS, etc.) while keeping wide channels functional.
  • Preamble puncturing: header gets trimmed too – spectral masks must comply.
  • Sounding with puncturing: beamforming feedback ignores dead zones.
  • Channel access: CCA respects only the active subchannels, not the ones you ignore.

Puncturing is clever engineering. Don’t waste spectrum. Work around noise. Respect legacy. Stay fast.

Details
Written by: Enrico Aderhold
Created: 25 September 2025

Wi-Fi - Antennas

The Effect and Usage of Antenna Types in WLAN Design
Antennas are fundamental components operating at the Physical Layer (Layer 1) of the OSI model in Wireless Local Area Networks (WLANs). They function as transducers, converting electrical signals into radio frequency (RF) waves for transmission and vice versa for reception. The choice of antenna significantly impacts a network's coverage area, signal strength, and overall performance, making it a crucial aspect for WLAN professionals involved in design, analysis, and troubleshooting. Various antenna types, including omnidirectional, patch, Yagi, sector, and parabolic dish antennas, possess distinct characteristics tailored for different deployment scenarios.


A key characteristic of an antenna is its gain, typically measured in dBi (decibels isotropic) or dBd (decibels dipole). Gain represents the increase in power achieved by concentrating signal energy in a particular direction compared to a theoretical isotropic radiator (for dBi) or a dipole antenna (for dBd). This concentration is referred to as passive gain and directs existing energy more effectively rather than generating more power. The Equivalent Isotropically Radiated Power (EIRP), a vital metric for compliance and link budget calculations, is the transmitter's output power combined with any gains or losses up to the antenna connection point, plus the antenna's directional gain. The dBi or dBd value must be calculated against the input power supplied to the antenna to determine the actual output power in the direction of propagation.


Another important characteristic is beamwidth, which describes the angular spread of the concentrated RF energy from the antenna's primary lobe. Beamwidth is measured in both horizontal and vertical planes at the points where the signal power is 3 dB lower (half power) than the maximum power point. Azimuth and Elevation diagrams visually depict an antenna's radiation pattern. Azimuth diagrams show the top-down (horizontal) pattern, while Elevation diagrams show the side (vertical) pattern. These diagrams are essential for predicting coverage, understanding propagation, and minimizing interference. The use of detachable or external antennas offers flexibility to position the antenna separately from the Access Point (AP) and select different antenna types or gain levels to optimize coverage (Basic Service Area - BSA) or address specific propagation issues. Antenna selection should consider manufacturer support, gain needs, and connector types.


Antenna selection is a critical component in designing Wireless LANs (WLANs), influencing signal propagation, coverage, capacity, and overall network performance. Different antenna types focus and radiate Radio Frequency (RF) energy in distinct patterns, making certain types more suitable for specific environments and use cases. Antenna gain, referenced in dBi, and directionality, often visualized through Azimuth and Elevation charts, are key characteristics that define how an antenna will perform. Beamwidth, measured horizontally and vertically at the -3 dB (half power) points, provides a quantitative measure of how broad or narrow the antenna's focus is. Understanding these characteristics and the different antenna types—Omnidirectional, Directional, Semi-directional, Patch/Panel, Sector, Yagi, and Parabolic Dish—is essential for effective WLAN design.


Omnidirectional Antennas
Omnidirectional antennas are a primary type of antenna used in WLANs. Characterized by a horizontal beamwidth of 360 degrees, they radiate RF energy outward in all directions within a horizontal plane. While they provide uniform coverage horizontally, their vertical beamwidth can vary significantly, typically ranging from 7 to 80 degrees. In general indoor implementations, internal antennas with omni-optimized patterns are often sufficient to provide coverage across an area. Standard omnidirectional antennas usually have a gain around 2.2 dBi, although higher-gain omni antennas (like 7 or 12 dBi) can be beneficial. Outdoor Access Points (APs) commonly use external omni antennas, often high-gain variants. When performing site surveys, using omni-directional antennas similar to what will be deployed is important for accurate measurements. Mismatched links can occur in bridge configurations if one side uses a high-output power omnidirectional antenna while the other uses a lower-power, high-gain antenna.


Directional and Semi-directional Antennas
Directional and semi-directional antennas are designed to focus RF energy in a specific direction or within a specific area, unlike omnidirectional antennas which spread energy in all horizontal directions. This focus provides higher gain in the desired direction and can be used to minimize Co-channel interference (CCI) by limiting signal propagation into unwanted areas. Beamwidth and Azimuth (top-down view) and Elevation (side view) charts are used to visualize and understand the specific propagation pattern of directional antennas. Semi-directional antennas are often used in environments like manufacturing or warehousing. Several specific types fall under the directional or semi-directional categories, each with distinct characteristics and applications: 

  • Patch/Panel Antennas: These are listed as a type of antenna. Patch/panel antennas typically have a horizontal beamwidth ranging from 30 to 180 degrees and a vertical beamwidth from 6 to 90 degrees. They are often used in manufacturing or warehousing environments more frequently than standard offices. Patch or panel antennas can be mounted on a wall and aimed inward or down a hallway to provide focused coverage. Testing with patch or panel antennas during a site survey allows evaluation of their performance compared to omni antennas.
  • Sector Antennas: Sector antennas are characterized by a horizontal beamwidth between 60 and 180 degrees and a narrow vertical beamwidth ranging from 7 to 17 degrees. These are particularly useful in high-density (HD) and very high-density (VHD) deployments, such as Large Public Venues (LPV). They can also be advantageous for outdoor networks. A sector antenna is intended to propagate its energy in one direction but across a fairly wide path, as illustrated by its Azimuth chart. Like patch/panel antennas, sector antennas are more common in manufacturing or warehousing than in standard offices.
  • Yagi Antennas: Yagi antennas have a horizontal beamwidth of 30 to 78 degrees and a vertical beamwidth of 14 to 64 degrees. They are another type of antenna used in environments like manufacturing or warehousing.
  • Parabolic Dish Antennas: Parabolic dish antennas are a type of highly directional antenna, more likely to be needed for outdoor site surveys. They offer the narrowest beamwidth among the listed types, ranging from 4 to 25 degrees horizontally and 4 to 21 degrees vertically. This focused energy makes them particularly suitable for long-distance outdoor links and bridge links, including Point-to-Point (PtP) and Point-to-Multipoint (PtMP) configurations. When designing bridge links, antenna selection is based on the required link distance, data-rate requirements, and regulatory constraints, with antenna gain impacting the Signal-to-Noise Ratio (SNR) at the receiver.

 

Effect and Usage in WLAN Design
The choice of antenna type has a profound effect on WLAN design and implementation. The propagation pattern of the selected antenna dictates the coverage area of an AP. For instance, omnidirectional antennas are used for broad area coverage in standard office environments, while directional antennas are employed to focus signal in specific areas or directions, which is crucial in environments like warehouses or stadiums.


Antenna gain contributes to achieving the necessary signal strength and SNR for reliable connections and required data rates, especially over distance. High-gain antennas should be used cautiously during site surveys on the survey client, as they might falsely represent sufficient coverage that standard client devices will not experience. Proper antenna selection is vital for mitigating interference. Using directional antennas can help prevent or minimize CCI in specific areas by containing the RF signal.


During site surveys, it is essential to use APs equipped with external antenna connectors to test different power levels and antenna types. Accurate predictive modeling relies on defining the correct antenna types and their properties. Post-installation validation should ensure that APs, including their antennas, are mounted in the correct location and orientation as specified in the design recommendation, because deviation can significantly alter the RF propagation pattern and coverage. Antenna selection is also a key consideration when designing bridge links, impacting link budgets and signal reach. For specific use cases like high-density designs, Large Public Venues, and outdoor deployments, the appropriate selection and placement of antennas, including sector or directional types, are critical for success.


In conclusion, selecting the appropriate antenna type based on its characteristics, such as gain and beamwidth, and understanding its propagation pattern is fundamental to successful WLAN design. The choice of omnidirectional or various directional antennas like Patch/Panel, Sector, Yagi, and Parabolic Dish directly impacts coverage, capacity, interference management, and the accuracy of site surveys and installations, ultimately determining whether the WLAN meets the required performance objectives.


Details
Written by: Enrico Aderhold
Created: 17 June 2025

802.11 - Wi-Fi 4

Wi-Fi 4 – when Wi-Fi got serious about speed

802.11n showed up in 2009, later renamed Wi-Fi 4 so normal humans could keep up. officially it was "Amendment 5" and landed in the big 802.11-2012 standard. also included in 802.11-2016, so yeah – it stuck around.

Details
Written by: Enrico Aderhold
Created: 11 June 2025

Read more: 802.11 - Wi-Fi 4

802.11 - Wi-Fi 8 (802.11bn)

what’s coming with Wi-Fi 8 (802.11bn)

Wi-Fi 8 ain’t just more bars. it’s smarter, tighter, more reliable – and meant for the next-gen stuff. here’s what you’ll probably see baked into 802.11bn once it lands ~2027.

Details
Written by: Enrico Aderhold
Created: 11 June 2025

Read more: 802.11 - Wi-Fi 8...

802.11 - Wi-Fi 7

Wi-Fi 7? Yeah, it's here.

Also called 802.11be or just "Extremely High Throughput" (EHT) if you're into that kind of thing. It’s not just faster Wi-Fi — it’s smarter, meaner, leaner. Built for crazy-dense environments, real-time apps, cloud gaming, AR/VR, and whatever else you throw at it.

Details
Written by: Enrico Aderhold
Created: 09 June 2025

Read more: 802.11 - Wi-Fi 7

  1. 802.11 - Secure Wi-Fi
  2. 802.11 - Design
  3. 802.11 - Wireshark Filters
  4. 802.11 - Modulation P.2

Subcategories

802.11 - Amendments

when random talks turn into blog ideas

some time ago a neighbour dropped by, asking weird stuff about car-to-car communication. turns out he’s doing some nav dev work for Bosch, not the fancy kind, more like boring routing routines. anyway, we ended up chatting about 802.11p and how it’s kinda the silent hero in that field.

and somehow, i got stuck with this idea – what if i just start a blog? not a fancy one, just plain old rambling through all those ieee 802.11 amendments. one by one. break them down like i explain them to a half-interested friend over coffee. and also maybe take a moment to praise the folks who made them happen. i mean, those amendment teams don’t get enough credit.

so yeah – here we go. one amendment at a time.

Page 1 of 6

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6

Impressum / Legal notice · Privacy notice

Privacy Policy

Cookie Policy