WiFi 7 (802.11be) Complete Guide: MLO Deployment, Channel Planning, and Enterprise Reality 2026

Introduction

WiFi 7 (802.11be, Extremely High Throughput) promises 46 Gbps theoretical throughput, sub-10ms latency, and seamless multi-band roaming via MLO. The reality in mid-2026 is more nuanced: 80% of client devices are still WiFi 6 or older, 1 GbE cabling bottlenecks most APs, and only three non-overlapping 320 MHz channels exist in the 6 GHz band. This guide cuts through the marketing to provide concrete deployment guidance — MLO mode selection, channel planning for dense environments, AP cabling requirements, real-world throughput expectations, and a client compatibility cheat sheet.

WiFi 7 Key Features

MLO: The Key Feature

MLO lets a client connect on multiple bands (2.4 + 5 + 6 GHz) simultaneously. Two modes exist:

EMLSR (Enhanced Multi-Link Single Radio)

The client has one radio but can switch between links. Listens on all links, transmits on the best one. This is the only client-side MLO mode widely available in mid-2026.

STR (Simultaneous Transmit and Receive)

The client has multiple radios and transmits/receives on all links simultaneously. Requires more hardware. Rarely supported on client devices in 2026. Expected to become common in late 2026-2027 with Qualcomm and Intel EMLMR chipsets.

# Example: UniFi WiFi 7 AP MLO configuration
# Enable MLO with EMLSR mode
set wireless.mlo=enable
set wireless.mlo_mode=emlsr
# Exclude 2.4 GHz from MLO (it creates more problems than it solves)
set wireless.mlo_exclude_24ghz=1

# Configure MLO group (which bands participate)
set wireless.mlo_group=5ghz,6ghz

Best practice: Exclude 2.4 GHz from MLO groups. It adds latency asymmetry and few clients benefit from 2.4 GHz in an MLO context. Use 5 GHz + 6 GHz only.

Channel Planning for Dense Enterprise

The 6 GHz band has only three non-overlapping 320 MHz channels. In dense deployments, co-channel interference between APs negates the wider channel benefit.

# 6 GHz channel availability (320 MHz):
# Channel 1:  5955-6235 MHz (US, full power)
# Channel 2:  6275-6555 MHz (US, full power)
# Channel 3:  6595-6875 MHz (US, full power)
# Total: 3 non-overlapping channels

# Channel planning rules for dense environments:
# - Use 160 MHz in enterprise with >4 APs per floor
# - Reserve 320 MHz for isolated high-throughput zones (auditoriums, conference centers)
# - Configure channel planning to maximize spatial reuse over raw channel width

Channel Width Decision Matrix

AP Cabling Requirements

Tri-radio WiFi 7 APs (2.4 + 5 + 6 GHz) need significant backhaul bandwidth. A 1 GbE uplink makes MLO pointless.

# Required uplink speeds by configuration
# Single radio (WiFi 6 fallback):     1 GbE sufficient
# Dual radio MLO (5+6 GHz, 160 MHz):  2.5 GbE minimum
# Tri-radio MLO (320 MHz):            5 GbE or 10 GbE

# Verify switch port capabilities
# A 48-port switch with 2.5 GbE on every port requires ~120 Gbps stacking bandwidth
# Many "WiFi 7 ready" switches only provide 2.5 GbE on a subset of ports

Client Compatibility (Mid-2026)

The MLO disappointment: 80% of your client fleet is still WiFi 6 or older and cannot use MLO. Budget for a client hardware refresh alongside the AP upgrade, or delay deployment until your device lifecycle naturally replaces them.

WiFi Generations Comparison

6 GHz Regulatory Status by Country (2026)

For multinational deployments, the EU’s restriction to lower 500 MHz means access points must be configurable to 160 MHz channels — a 320 MHz-only AP cannot operate in most European countries.

Spectrum Analysis Commands

# Linux: check 6 GHz radio support on AP
iw list | grep -A5 "Band 3"
# Look for: * 5955 MHz [1] (30.0 dBm)

# Check channel utilization before deploying 320 MHz
# Install wavemon for real-time spectrum monitoring
sudo apt install wavemon
wavemon

# Survey neighboring APs on 6 GHz
sudo iw dev wlan0 scan -f | grep -E "freq|signal|SSID" | head -40

# Check DFS status (required for 6 GHz standard power)
cat /sys/kernel/debug/ieee80211/phy0/dfs* 2>/dev/null

Vendor AP Selection Criteria

Enterprise Relevance: Ensure the AP supports at least 2.5 GbE uplink and has tri-radio support (2.4 + 5 + 6 GHz). STR mode is only useful if your client fleet includes chipsets that support it — most don’t in 2026.

Deployment Gotchas

# 1. PoE budget: tri-radio APs draw 30-45W
# Verify PoE++ (802.3bt, 60W) on switch ports
show power inline
# Interface PoE(Power)       Status     Power
# Gi1/0/1   PoE++ 802.3bt   On         38.5W

# 2. RADIUS/NAC: MLO clients have dual MAC addresses
# The MLD (Multi-Link Device) has one MAC, each link has its own
# RADIUS must correlate both MACs to the same client session
# Update NAC configuration to handle MLD MAC pairs

# 3. Firmware: MLO stability improves with each driver release
# Aggressively update client WiFi drivers and AP firmware
# Check vendor release notes for MLO-specific fixes

Real-World Throughput

Theoretical: 46 Gbps (320 MHz, 16x16 MIMO, 4K-QAM)
Real-world (lab, optimal conditions):                4-6 Gbps
Real-world (enterprise office, mixed clients):       500-900 Mbps
Real-world (MLO enabled, WiFi 7 client):             1.2-2 Gbps

vs WiFi 6 (enterprise office):                       300-500 Mbps
vs WiFi 6E (enterprise office):                      400-700 Mbps

Resources

• IEEE 802.11be Standard — Official spec
• WiFi 7 Enterprise Deployment Guide — Real-world deployment experience
• WiFi 7 MLO Production Lessons — EMLSR, channel planning, switching upgrades
• WiFi 7 for Enterprise Networks — Vendor evaluation, 6 GHz regulation by country