Skip to main content
English (US)

20MHz vs 40MHz vs 80MHz: Which Channel Width Should You Use?

This guide provides a definitive, vendor-neutral technical reference for IT managers, network architects, and venue operations directors on selecting the correct WiFi channel width โ€” 20MHz, 40MHz, or 80MHz โ€” across enterprise deployments in hospitality, retail, events, and public-sector environments. It covers the underlying IEEE 802.11 mechanics, real-world capacity trade-offs, and step-by-step deployment guidance to help teams make the right call this quarter. Understanding channel width selection is one of the highest-leverage decisions in any wireless LAN design, directly impacting throughput, interference, client density support, and the reliability of guest-facing services.

๐Ÿ“– 6 min read๐Ÿ“ 1,264 words๐Ÿ”ง 3 worked examplesโ“ 3 practice questions๐Ÿ“š 9 key definitions

Listen to this guide

View podcast transcript
Welcome to the Purple Technical Briefing. I'm your host, and today we're tackling one of the most persistent debates in enterprise wireless networking: 20 megahertz versus 40 megahertz versus 80 megahertz channel widths. Which one should you actually be using? If you're an IT manager, a network architect, or a venue operations director, you know that getting this wrong means poor user experience, helpdesk tickets, and compromised return on investment on your infrastructure spend. Today, we're cutting through the theory to give you actionable, vendor-neutral deployment guidance. Let's start with the core technical reality. The wider the channel, the higher the theoretical throughput. It's like adding lanes to a motorway. 20 megahertz is a single lane, 40 megahertz is a dual carriageway, and 80 megahertz is a four-lane superhighway. But here's the catch: in wireless networking, adding lanes also means you're more likely to crash into someone else. This is Co-Channel Interference, or CCI. In the 2.4 gigahertz band, you only have three non-overlapping 20 megahertz channels: 1, 6, and 11. If you try to use 40 megahertz in 2.4 gigahertz, you're going to overlap with almost everything, destroying performance. The golden rule here is absolute: never use 40 megahertz in the 2.4 gigahertz band in an enterprise environment. Stick to 20 megahertz. The real debate happens in the 5 gigahertz band. Here, you have significantly more spectrum, especially if you leverage Dynamic Frequency Selection, or DFS channels. DFS opens up a substantial block of additional spectrum that most consumer devices avoid, giving enterprise deployments a meaningful advantage. So, when do you use 20 megahertz on 5 gigahertz? This is your go-to for high-density environments. Think hospitality deployments with hundreds of hotel rooms, or large retail spaces with high footfall. By sticking to 20 megahertz, you maximise the number of non-overlapping channels available, drastically reducing co-channel interference. The throughput per client might be lower, but the overall aggregate capacity of the network is higher because access points aren't shouting over each other. It's about stability over peak speed. What about 40 megahertz? This is the sweet spot for mixed-use enterprise environments. Corporate offices, medium-density public sector buildings, or smaller conference centres. It offers a solid balance, doubling your throughput compared to 20 megahertz while still providing enough non-overlapping channels to design a robust channel plan, assuming you're using DFS. And then there's 80 megahertz. Marketing materials love 80 megahertz because it delivers massive headline speeds. But in the real world, 80 megahertz consumes four standard 20 megahertz channels. In most enterprise deployments, using 80 megahertz will lead to severe co-channel interference because you simply don't have enough spectrum to avoid access points stepping on each other's toes. The only time you should consider 80 megahertz is in very specific, low-density, high-bandwidth scenarios. For example, a dedicated access point in an executive boardroom, or a small remote office with only one or two access points and no noisy neighbours. Let's look at a real-world scenario. A large transport hub recently upgraded their infrastructure. They initially deployed 80 megahertz channels on 5 gigahertz, expecting massive speeds for passengers. Instead, they saw latency spikes and connection drops. The issue? Too many access points operating on the same wide channels. We advised them to drop down to 20 megahertz. Peak speeds per user decreased, but overall network reliability and capacity skyrocketed. The guest WiFi experience improved dramatically, leading to higher engagement with their captive portal and better data capture for their WiFi analytics platform. Now for a quick rapid-fire question and answer session. Question one: Does using wider channels decrease range? Yes. Every time you double the channel width, you increase the noise floor by 3 decibels. This effectively reduces your Signal-to-Noise Ratio, meaning clients need to be closer to the access point to maintain the same modulation rates. In practical terms, a client that could connect at 300 megabits per second at 20 metres on 20 megahertz might only achieve 150 megabits per second at the same distance on 80 megahertz, due to the degraded signal-to-noise ratio. Question two: What about 160 megahertz channels in WiFi 6 and WiFi 6E? Unless you are in the pristine 6 gigahertz band of WiFi 6E, avoid 160 megahertz entirely in enterprise deployments. It's a spectrum hog and will cause massive interference. Even in 6 gigahertz, 80 megahertz is usually the practical maximum for most venue deployments. The 6 gigahertz band is genuinely exciting because it offers up to 1200 megahertz of clean, uncongested spectrum, but we're still in the early stages of widespread client device support. Question three: Should I use automatic channel width selection? With caution. Most enterprise access point vendors offer automatic or dynamic channel width selection, and in theory this sounds ideal. In practice, the algorithms can be aggressive, and you may find access points selecting 80 megahertz channels at peak times, causing interference. Always validate automatic selections against a spectrum analysis, and consider setting a maximum channel width cap in your wireless LAN controller policy. To summarise: For dense deployments like stadiums or large hotels, use 20 megahertz. For standard enterprise offices and mixed-use venues, 40 megahertz is usually optimal. Reserve 80 megahertz for isolated, high-bandwidth, low-density requirements. Always design for capacity and stability first, not peak theoretical speed. And remember: the best WiFi channels are the ones your neighbours aren't already using. Thank you for joining this Purple Technical Briefing. If you'd like to explore how Purple's hardware-agnostic guest WiFi platform and analytics tools can help you optimise your wireless deployment, visit purple dot A I. Ensure your network is built on solid foundations, and your digital initiatives will follow suit.

header_image.png

Executive Summary

Channel width selection is one of the most consequential โ€” and most frequently misconfigured โ€” parameters in enterprise wireless LAN design. The choice between 20MHz, 40MHz, and 80MHz channels directly governs the trade-off between per-client throughput and aggregate network capacity. Wider channels deliver higher theoretical speeds but consume more spectrum, reducing the number of non-overlapping channels available and increasing co-channel interference (CCI) in dense deployments.

The practical guidance is straightforward: 20MHz on 2.4GHz is non-negotiable in any multi-AP deployment. On 5GHz, the decision depends on client density, venue type, and spectrum availability. High-density environments โ€” hotels, retail floors, stadiums, conference centres โ€” should default to 20MHz on 5GHz to maximise channel reuse. Mixed-use enterprise offices and medium-density venues can leverage 40MHz for a balanced throughput-capacity trade-off. 80MHz should be reserved for isolated, low-density, high-bandwidth scenarios where spectrum is genuinely available.

For venue operators running Guest WiFi at scale, this decision directly impacts the reliability of captive portal authentication, the accuracy of WiFi Analytics data, and the overall guest experience that drives repeat engagement and loyalty.

Technical Deep-Dive

The Physics of Channel Width

In IEEE 802.11 wireless networking, a channel is a defined slice of radio frequency spectrum. The width of that slice โ€” measured in megahertz โ€” determines how much data can be transmitted simultaneously. This relationship is governed by the Shannon-Hartley theorem: channel capacity scales with bandwidth. Doubling the channel width from 20MHz to 40MHz approximately doubles the theoretical maximum data rate, all else being equal.

However, "all else being equal" is the critical qualifier. In a real-world multi-AP deployment, spectrum is a shared, finite resource. Every megahertz you allocate to one channel is a megahertz unavailable to adjacent channels. This creates the central tension in channel width selection: wider channels increase per-client throughput but reduce the number of non-overlapping channels, increasing the probability of co-channel interference.

channel_width_comparison_chart.png

The 2.4GHz Band: A Closed Case

The 2.4GHz ISM band spans 83.5MHz in the UK and most of Europe (2400โ€“2483.5MHz). With 20MHz channels and the standard 5MHz channel spacing, there are only three non-overlapping channels: 1, 6, and 11. This is already a severely constrained environment in any multi-AP deployment.

Attempting to use 40MHz channels in 2.4GHz is a deployment anti-pattern. A single 40MHz channel in 2.4GHz occupies the equivalent of two 20MHz channels plus their guard bands, meaning it overlaps with at least two of the three non-overlapping channels. In practice, this destroys the channel plan entirely. The IEEE 802.11n specification technically permits 40MHz in 2.4GHz, but the Wi-Fi Alliance's enterprise certification programmes and every credible wireless design methodology advise against it.

Rule: Always use 20MHz in the 2.4GHz band in any enterprise or multi-AP deployment. No exceptions.

The 5GHz Band: Where the Real Decision Lives

The 5GHz band (5150โ€“5850MHz in the UK, subject to Ofcom regulation) provides significantly more usable spectrum. With 20MHz channels, there are up to 25 non-overlapping channels available, though the exact number depends on regulatory domain and whether Dynamic Frequency Selection (DFS) channels are enabled.

DFS channels (U-NII-2A and U-NII-2C sub-bands) require access points to detect and avoid radar signals, introducing a mandatory Channel Availability Check (CAC) period of up to 60 seconds before transmission. In practice, most enterprise-grade APs handle DFS gracefully, and enabling DFS channels is strongly recommended as it nearly doubles the available 5GHz spectrum.

Channel Width 5GHz Non-Overlapping Channels (with DFS) Typical Max Throughput (802.11ac/Wi-Fi 5, 2SS) Noise Floor Increase vs 20MHz
20MHz ~25 ~300 Mbps Baseline
40MHz ~12 ~600 Mbps +3 dB
80MHz ~6 ~1300 Mbps +6 dB
160MHz ~2โ€“3 ~2600 Mbps +9 dB

The noise floor increase is critical. Every time you double channel width, the noise floor rises by 3dB. This directly degrades the Signal-to-Noise Ratio (SNR) for all clients, reducing the effective range at which a given Modulation and Coding Scheme (MCS) index can be sustained. An AP configured for 80MHz channels will have a materially shorter effective range than the same AP on 20MHz, which has significant implications for coverage planning in large venues.

Co-Channel Interference: The Dominant Failure Mode

Co-Channel Interference occurs when two or more APs transmit on the same channel within range of each other. Unlike Adjacent Channel Interference (ACI), CCI cannot be mitigated by guard bands โ€” it is an inherent consequence of the CSMA/CA (Carrier Sense Multiple Access with Collision Avoidance) medium access mechanism that 802.11 uses.

When an AP detects another transmission on its channel, it must defer its own transmission. In a dense deployment where multiple APs are operating on the same wide channel, this deferral overhead accumulates rapidly, reducing effective throughput and increasing latency. This is why a network with 20 APs all on 80MHz channels will frequently perform worse in aggregate than the same 20 APs on 20MHz channels โ€” despite the theoretical throughput advantage of 80MHz.

WiFi 6, WiFi 6E, and the 6GHz Opportunity

IEEE 802.11ax (Wi-Fi 6) introduces OFDMA (Orthogonal Frequency Division Multiple Access), which partially mitigates the channel width dilemma by allowing a single channel to be subdivided into Resource Units (RUs) serving multiple clients simultaneously. This improves spectral efficiency in dense environments and reduces the penalty of wider channels.

Wi-Fi 6E extends 802.11ax into the 6GHz band (5925โ€“6425MHz in the UK), providing up to 500MHz of additional, largely uncongested spectrum. In 6GHz, 80MHz channels become significantly more viable because the interference environment is cleaner and there are more non-overlapping channels available. However, as of 2026, 6GHz client device penetration in typical enterprise environments remains partial, and the 5GHz design principles above remain the dominant operational reality for most deployments.

For organisations exploring passwordless access and modern onboarding , the underlying radio layer design remains foundational โ€” no amount of authentication sophistication compensates for a poorly designed RF environment.

Implementation Guide

Step 1: Conduct a Pre-Deployment Spectrum Analysis

Before configuring any channel widths, perform a passive spectrum analysis using a dedicated tool (Ekahau, NetAlly AirCheck, or equivalent). Document existing channel utilisation, noise floor levels, and interfering sources (microwave ovens, DECT phones, Bluetooth devices) across both 2.4GHz and 5GHz. This baseline is essential for validating your channel plan post-deployment.

Step 2: Define Your Deployment Tier

Classify your venue against one of three deployment tiers:

Tier 1 โ€” High Density: Hotels (>100 rooms), retail flagships (>500 concurrent users), stadiums, conference centres, transport hubs. Default channel width: 20MHz on both 2.4GHz and 5GHz.

Tier 2 โ€” Medium Density: Corporate offices (50โ€“500 users), medium retail, public sector buildings, smaller hospitality venues. Default channel width: 20MHz on 2.4GHz, 40MHz on 5GHz.

Tier 3 โ€” Low Density: Small offices (<50 users), executive suites, dedicated AV/streaming rooms, single-AP remote sites. Default channel width: 20MHz on 2.4GHz, 80MHz on 5GHz (only where spectrum analysis confirms availability).

Step 3: Design Your Channel Plan

For Tier 1 deployments, assign 20MHz channels across the three non-overlapping 2.4GHz channels and up to 25 non-overlapping 5GHz channels (with DFS enabled). Aim for a minimum of 19dB co-channel separation between APs on the same channel. For Tier 2, design your 40MHz channel plan using the 12 available non-overlapping 40MHz channels on 5GHz. Ensure adjacent APs use different primary channels.

deployment_scenario_diagram.png

Step 4: Configure Your Wireless LAN Controller

In your WLC or cloud management platform, set channel width policies at the radio profile level rather than per-AP. This ensures consistency and simplifies ongoing management. Key configuration parameters:

  • Channel Width: Set explicitly; do not rely on auto-selection without validation.
  • Maximum TX Power: Reduce transmit power to match your coverage cell design โ€” over-powered APs increase CCI.
  • Band Steering: Enable to push dual-band clients to 5GHz, reducing 2.4GHz congestion.
  • RRM (Radio Resource Management): If using vendor RRM (Cisco RRM, Aruba ARM, Ruckus SmartZone), set a maximum channel width cap to prevent automatic escalation to 80MHz.

For organisations managing complex multi-site deployments, the principles around centralised control are well covered in our guide on What is a WLC (Wireless LAN Controller) and Do You Still Need One? .

Step 5: Validate and Iterate

Post-deployment, run a predictive validation survey against your as-built configuration. Key metrics to validate: channel utilisation per AP (target <70% at peak), client SNR distribution (target >25dB for >80% of clients), and retry rates (target <10%). Use your WiFi Analytics platform to correlate RF performance metrics with guest experience data โ€” connection duration, session counts, and portal completion rates are leading indicators of RF quality.

Real-World Case Studies

Case Study 1: 350-Room Hotel โ€” Hilton-Category Property, UK

A 350-room full-service hotel was experiencing persistent guest WiFi complaints: slow speeds in corridors, frequent disconnections during check-in peak hours, and poor performance in the conference suite. The existing deployment used 80MHz channels on 5GHz across all 140 APs.

Spectrum analysis revealed severe co-channel interference throughout the guest room floors, with channel utilisation exceeding 85% on multiple APs during peak hours. The channel plan had effectively collapsed โ€” APs were deferring constantly, and actual throughput was a fraction of theoretical capacity.

The remediation involved reconfiguring all guest room and corridor APs to 20MHz on 5GHz, redesigning the channel plan to use 22 of the 25 available non-overlapping 5GHz channels, and reducing transmit power by 3dB to tighten coverage cells. Conference suite APs were retained at 40MHz given their lower density and higher per-session bandwidth requirements.

Post-remediation results: average client throughput increased by 34%, channel utilisation dropped to below 55% at peak, and helpdesk tickets related to WiFi fell by 61% in the following quarter. The Guest WiFi portal completion rate improved from 67% to 84%, directly increasing the volume of first-party data captured for the property's CRM integration. This aligns with the broader principle that network reliability is a prerequisite for improving guest satisfaction at scale.

Case Study 2: 120-Store Retail Chain โ€” UK Fashion Retailer

A national fashion retailer with 120 stores was rolling out a unified Retail WiFi platform to support both customer-facing guest access and back-of-house operational systems (EPOS, stock management, digital signage). Store sizes ranged from 2,000 to 15,000 square feet, with AP counts of 4โ€“18 per site.

The initial configuration used 80MHz channels on 5GHz across all stores, driven by a vendor recommendation focused on maximising throughput for the digital signage use case. In the 12 largest stores (>8,000 sq ft, >10 APs), this created significant CCI, with EPOS terminals experiencing intermittent connectivity during peak trading hours โ€” a direct operational and PCI DSS compliance risk, as transaction timeouts were triggering manual fallback procedures.

The solution was a tiered channel width policy deployed via the central WLC: stores with >8 APs were configured to 20MHz on 5GHz; stores with 5โ€“8 APs to 40MHz; stores with <5 APs retained 80MHz. Digital signage APs in all stores were placed on a dedicated 5GHz radio with 40MHz channels, isolated from the guest and EPOS SSIDs via VLAN segmentation.

Post-deployment, EPOS connectivity incidents dropped by 78% across the large-store estate, and the guest WiFi engagement rate (measured via the captive portal analytics) increased by 22% as connection reliability improved. The segmented approach also simplified PCI DSS scope management by ensuring cardholder data environments were on dedicated, non-shared radio resources.

Best Practices

The following vendor-neutral best practices represent the consensus of IEEE 802.11 working group guidance, Wi-Fi Alliance certification requirements, and operational experience across enterprise deployments.

Always enable DFS channels. Regulatory reluctance to use DFS channels is understandable but counterproductive. Modern enterprise APs handle radar detection reliably, and the additional spectrum is essential for any 40MHz or 80MHz channel plan to be viable. Verify your regulatory domain settings are correctly configured for your country of deployment.

Separate guest and corporate traffic at the radio level where possible. Using dedicated SSIDs on separate VLANs is standard practice, but in high-density environments, consider dedicating specific radios or APs to guest traffic. This prevents guest device behaviour (aggressive roaming, legacy 802.11b/g clients) from degrading corporate network performance.

Implement minimum RSSI thresholds. Configure your WLC to reject client associations below a minimum Received Signal Strength Indicator (RSSI) threshold (typically -75 to -70 dBm). This prevents "sticky client" behaviour where devices hold onto distant APs at low data rates, consuming airtime inefficiently.

Audit your channel plan quarterly. The RF environment changes as new APs are deployed in neighbouring premises, building usage patterns shift, and new interference sources are introduced. A channel plan that was optimal at deployment may be suboptimal 12 months later. Quarterly spectrum audits are a low-cost, high-value operational practice.

For Healthcare and public-sector deployments, additional constraints apply. Medical devices often use 2.4GHz exclusively and may be sensitive to channel changes. Coordinate channel plan changes with clinical engineering teams and schedule them during low-activity windows. GDPR and NHS data security requirements also mandate network segmentation that should be reflected in your SSID and VLAN architecture.

For Transport hubs and stadiums, the combination of extremely high client density and rapid client turnover (passengers boarding/alighting, crowds entering/exiting) creates unique RF challenges. 20MHz channels on 5GHz are essentially mandatory, and directional antenna patterns should be used to tighten coverage cells and reduce inter-AP interference.

Troubleshooting and Risk Mitigation

Symptom: High Channel Utilisation Despite Low Client Count

This typically indicates CCI from neighbouring APs on the same channel. Verify your channel plan using a spectrum analyser โ€” look for APs (yours or neighbouring) on the same channel within range. Remediation: reassign channels to increase separation, or reduce transmit power to shrink coverage cells.

Symptom: Good RSSI but Poor Throughput

High RSSI with low throughput is a classic CCI signature. Clients are receiving a strong signal from their associated AP but are experiencing high retry rates due to medium contention. Check retry rates in your WLC dashboard (target <10%). If retries are high, reduce channel width or redesign the channel plan.

Symptom: Clients Failing to Roam Between APs

This is often caused by mismatched channel widths between APs, or by minimum RSSI thresholds that are too aggressive. Verify that all APs in a roaming domain use consistent channel width configurations, and that 802.11r (Fast BSS Transition) and 802.11k (Neighbour Reports) are enabled to facilitate smooth roaming.

Symptom: DFS Channel Instability

If APs on DFS channels are frequently changing channels (visible in WLC logs as radar detection events), verify that the interference source is genuine radar (airport, weather station, military) rather than a false positive from another AP or device. Some enterprise APs have known false-positive issues with specific DFS channels โ€” consult vendor release notes and consider excluding problematic channels from your DFS pool.

Risk: Automatic Channel Width Escalation

Many enterprise WLC platforms include Radio Resource Management (RRM) algorithms that can automatically increase channel width during low-utilisation periods. This is a known risk: the algorithm may escalate to 80MHz during off-peak hours, and the wider channel plan may persist into peak hours when it causes CCI. Set a maximum channel width cap in your RRM policy to prevent this. This is one of the most common misconfiguration patterns seen in enterprise deployments.

ROI and Business Impact

The business case for correct channel width configuration is compelling and measurable. The cost of remediation โ€” primarily engineer time for spectrum analysis and WLC reconfiguration โ€” is typically 1โ€“3 days of effort for a medium-sized deployment. The returns are immediate and multi-dimensional.

Reduced helpdesk overhead: WiFi connectivity complaints are among the highest-volume helpdesk categories in hospitality and retail. A well-configured channel plan typically reduces WiFi-related tickets by 40โ€“70%, freeing IT resource for higher-value activities.

Improved guest data capture: For venues running Guest WiFi with captive portal authentication, network reliability directly drives portal completion rates. A 10-percentage-point improvement in completion rate across a 1,000-daily-user venue translates to 36,500 additional data records per year โ€” each representing a marketable, consented customer profile.

Operational continuity: For retail environments where EPOS, inventory management, and digital signage depend on WiFi, CCI-induced connectivity failures carry direct revenue impact. A single EPOS outage during peak trading can cost a large-format retailer thousands of pounds per hour.

Analytics fidelity: WiFi Analytics platforms that use probe request data for dwell time analysis and footfall measurement are directly dependent on AP radio performance. CCI increases the noise floor, reducing the effective range at which probe requests are captured and degrading the accuracy of location analytics. Correct channel width configuration is therefore a prerequisite for reliable venue intelligence.

For public-sector organisations exploring smart city and digital inclusion initiatives โ€” an area Purple is actively investing in โ€” the same RF design principles apply at infrastructure scale. Reliable, well-designed public WiFi is the foundation on which digital services are delivered, as explored in our recent announcement around public sector growth .

Key Definitions

Channel Width

The amount of radio frequency spectrum (measured in MHz) occupied by a single WiFi channel. Wider channels carry more data simultaneously but consume more spectrum, reducing the number of non-overlapping channels available in a given band.

The primary configuration parameter governing the throughput-versus-capacity trade-off in any wireless LAN design. Configured at the radio profile level in enterprise WLCs.

Co-Channel Interference (CCI)

Interference that occurs when two or more access points transmit on the same channel within range of each other. Unlike adjacent channel interference, CCI cannot be mitigated by guard bands โ€” it forces APs to defer transmission via CSMA/CA, reducing effective throughput and increasing latency.

The dominant performance failure mode in dense enterprise WiFi deployments. CCI is the primary reason why wider channels degrade performance in multi-AP environments despite their higher theoretical throughput.

Dynamic Frequency Selection (DFS)

An IEEE 802.11h mechanism that allows access points to use radar-protected 5GHz channels (U-NII-2A and U-NII-2C sub-bands) by detecting and avoiding radar signals. DFS channels require a Channel Availability Check (CAC) period of up to 60 seconds before use.

Enabling DFS channels nearly doubles the available 5GHz spectrum in most regulatory domains, making it essential for any 40MHz or 80MHz channel plan to be viable. Enterprise APs handle DFS reliably; consumer-grade APs often avoid DFS channels entirely.

Signal-to-Noise Ratio (SNR)

The ratio of the desired signal power to the background noise power at a receiver, measured in decibels. Higher SNR enables higher Modulation and Coding Scheme (MCS) indices, which translate to higher data rates.

Wider channels increase the noise floor (by 3dB per doubling of width), reducing SNR for all clients. IT teams should target >25dB SNR for >80% of clients in any enterprise deployment.

Modulation and Coding Scheme (MCS) Index

A numerical index (0โ€“11 in 802.11ax/Wi-Fi 6) that defines the combination of modulation technique and forward error correction coding rate used for a given transmission. Higher MCS indices deliver higher data rates but require better SNR.

The MCS index is dynamically negotiated between AP and client based on current SNR. Channel width changes that degrade SNR will cause clients to fall back to lower MCS indices, reducing actual throughput even if the channel is theoretically wider.

OFDMA (Orthogonal Frequency Division Multiple Access)

A multi-user version of OFDM introduced in IEEE 802.11ax (Wi-Fi 6) that subdivides a channel into Resource Units (RUs), allowing a single AP to serve multiple clients simultaneously within a single transmission opportunity.

OFDMA is the primary mechanism by which Wi-Fi 6 improves performance in dense environments. It partially mitigates the channel width dilemma by improving spectral efficiency within a given channel width, reducing the pressure to use wider channels for throughput.

BSS Colouring

An IEEE 802.11ax feature that assigns a colour identifier to each Basic Service Set (BSS). APs and clients can identify transmissions from overlapping BSSs by their colour and, if the signal is below a threshold, proceed with their own transmission rather than deferring โ€” effectively implementing spatial reuse.

BSS Colouring is a key Wi-Fi 6 feature for dense deployments. It reduces the CCI penalty of overlapping coverage cells without requiring physical channel separation, making it particularly valuable in environments where the channel plan is constrained.

Radio Resource Management (RRM)

An automated system in enterprise wireless LAN controllers that dynamically adjusts AP radio parameters โ€” including channel assignment, transmit power, and channel width โ€” based on observed RF conditions.

RRM is a powerful tool but requires careful policy configuration. Without a maximum channel width cap, RRM algorithms may escalate to 80MHz channels during low-utilisation periods, creating CCI problems at peak hours. Always validate RRM decisions against spectrum analysis data.

Non-Overlapping Channels

Channels whose frequency ranges do not overlap with each other, allowing simultaneous transmission without mutual interference. In 2.4GHz with 20MHz channels, there are only three non-overlapping channels (1, 6, 11). In 5GHz with 20MHz channels and DFS enabled, there are up to 25.

The number of non-overlapping channels available is the fundamental constraint on channel plan design. It determines how many APs can operate simultaneously without CCI, and therefore the maximum achievable density of a wireless deployment.

Worked Examples

A 350-room full-service hotel is experiencing widespread guest WiFi complaints โ€” slow speeds in corridors, frequent disconnections during check-in peaks, and poor performance in the 800-seat conference suite. The existing deployment has 140 APs, all configured to 80MHz on 5GHz. How should the network team approach this remediation?

Step 1: Conduct a passive spectrum analysis across all floors during peak hours (typically 08:00โ€“10:00 and 18:00โ€“21:00 for a hotel). Document channel utilisation per AP, noise floor, and retry rates. Step 2: Identify APs with >70% channel utilisation โ€” these are your primary CCI victims. In an 80MHz deployment with 140 APs, expect to find widespread utilisation above 80% on guest room floors. Step 3: Redesign the channel plan. For guest room corridors and floors, reconfigure all APs to 20MHz on 5GHz. Enable DFS channels to access up to 25 non-overlapping 20MHz channels. Assign channels using a minimum co-channel separation of 19dB. Step 4: For the conference suite, retain 40MHz on dedicated conference APs (not the corridor APs). The conference suite has controlled access and lower concurrent AP density. Step 5: Reduce transmit power by 3dB across guest room APs to tighten coverage cells and reduce inter-AP interference. Step 6: Enable 802.11r and 802.11k for fast roaming support. Step 7: Validate post-deployment with a survey โ€” target <55% channel utilisation at peak, >25dB SNR for >80% of clients, <10% retry rate.

Examiner's Commentary: The key insight here is that 80MHz was the root cause, not a symptom. The instinct to 'add more APs' or 'increase power' would have made the CCI worse, not better. The tiered approach โ€” 20MHz for density, 40MHz for controlled-access high-bandwidth spaces โ€” is the correct architectural response. The conference suite retention of 40MHz is justified because it has a lower AP density and higher per-session bandwidth requirement (video conferencing, large file transfers). The transmit power reduction is often overlooked but is essential: over-powered APs extend their CCI footprint unnecessarily.

A 120-store UK fashion retailer is rolling out a unified WiFi platform covering both guest access and operational systems (EPOS, stock management, digital signage). Store sizes range from 2,000 to 15,000 sq ft with 4โ€“18 APs per site. EPOS terminals are experiencing intermittent connectivity in the 12 largest stores. How should the channel width policy be structured across the estate?

Step 1: Segment the estate by AP count as a proxy for density: <5 APs (small stores), 5โ€“8 APs (medium stores), >8 APs (large stores). Step 2: Apply tiered channel width policies via the central WLC: large stores (>8 APs) โ€” 20MHz on 5GHz; medium stores (5โ€“8 APs) โ€” 40MHz on 5GHz; small stores (<5 APs) โ€” 80MHz on 5GHz. Step 3: In all stores, configure EPOS and cardholder data traffic on a dedicated SSID mapped to a separate VLAN, isolated from guest traffic. This is a PCI DSS requirement (Requirement 1.3: restrict inbound and outbound traffic to that which is necessary). Step 4: For digital signage, deploy dedicated 5GHz radios (where APs support tri-radio or dual 5GHz configurations) at 40MHz, separate from both guest and EPOS SSIDs. Step 5: Implement minimum RSSI thresholds of -72 dBm on EPOS SSIDs to prevent sticky client behaviour on EPOS terminals. Step 6: Deploy the configuration via WLC templates to ensure consistency across all 120 sites, with per-store overrides only where spectrum analysis justifies deviation.

Examiner's Commentary: The tiered approach by store size is pragmatic and scalable โ€” it avoids the operational overhead of per-site channel planning while still addressing the density-driven CCI problem in large stores. The PCI DSS segmentation point is critical: EPOS connectivity failures are not just an operational problem, they are a compliance risk. The digital signage isolation on a dedicated radio prevents high-bandwidth streaming traffic from competing with EPOS transactions on the same medium. The RSSI threshold on EPOS SSIDs addresses the sticky client problem that is particularly common with fixed-location devices like tills.

A major UK transport hub (large rail terminus, 50,000+ daily passengers) is planning a WiFi infrastructure refresh. The existing deployment uses 40MHz channels on 5GHz across 200 APs covering concourses, platforms, and retail units. The operations team wants to upgrade to WiFi 6 hardware and is asking whether they should move to 80MHz to take advantage of the new hardware's throughput capabilities.

Recommendation: Do not increase to 80MHz. Retain 20MHz on 5GHz for all concourse and platform APs, and consider 40MHz only for retail unit APs where client density is lower and per-session bandwidth is higher. Rationale: A transport hub with 50,000 daily passengers represents one of the highest-density WiFi environments in the enterprise world. Client density on platforms during peak hours can exceed 500 concurrent devices per AP coverage zone. At this density, CCI is the dominant performance constraint โ€” not per-client throughput. WiFi 6's OFDMA capability is the correct tool for this environment: it allows a single 20MHz channel to serve multiple clients simultaneously via Resource Unit (RU) allocation, improving spectral efficiency without requiring wider channels. Configure WiFi 6 APs with 20MHz channels and enable OFDMA, BSS Colouring (to reduce CCI via spatial reuse), and Target Wake Time (TWT) to reduce contention. For the retail units, 40MHz on 5GHz is appropriate given lower density and the need to support higher-bandwidth applications (contactless payments, inventory scanning). Ensure all APs support 802.11r, 802.11k, and 802.11v for seamless roaming as passengers move through the terminal.

Examiner's Commentary: This scenario tests the ability to resist the marketing pull of wider channels on new hardware. WiFi 6's value in high-density environments comes primarily from OFDMA and BSS Colouring, not from wider channels. The correct answer is to use WiFi 6 features to improve efficiency within 20MHz channels, not to widen channels and introduce more CCI. The retail unit differentiation demonstrates understanding that channel width policy should be context-specific, not estate-wide. The roaming protocol references (802.11r/k/v) are appropriate given the mobile nature of the user population.

Practice Questions

Q1. You are the network architect for a 500-room conference hotel. The property has 220 APs deployed across guest room floors, corridors, a 1,200-seat ballroom, 20 breakout meeting rooms, and a business centre. The current configuration uses 40MHz channels on 5GHz estate-wide. During a large conference event (800 delegates), guests are reporting slow speeds and frequent disconnections on the guest room floors, while the ballroom WiFi is performing well. What is the most likely cause, and what channel width changes would you recommend?

Hint: Consider the AP density on guest room floors versus the ballroom. What is the channel utilisation likely to be on each? How many non-overlapping 40MHz channels are available on 5GHz?

View model answer

The most likely cause is co-channel interference on the guest room floors. With 220 APs across the property, the guest room floors will have the highest AP density โ€” potentially 15โ€“20 APs per floor in a 500-room hotel. With 40MHz channels on 5GHz, there are only 12 non-overlapping channels available (with DFS). At 15โ€“20 APs per floor, multiple APs will inevitably share channels, creating CCI that degrades performance under high load. The ballroom performs well because it has a lower AP density (likely 2โ€“4 APs in a large open space) and the 40MHz channel plan can be maintained without significant CCI. Recommended changes: reconfigure all guest room floor and corridor APs to 20MHz on 5GHz, enabling up to 25 non-overlapping channels. Retain 40MHz for the ballroom APs (low density, high per-session bandwidth for video conferencing and presentations) and the meeting rooms. The business centre can remain at 40MHz given its typically low concurrent user count. Validate with a post-change spectrum survey targeting <60% channel utilisation at peak.

Q2. A retail operations director asks why the WiFi in the company's flagship 20,000 sq ft store is performing worse since a recent AP firmware upgrade that enabled 'automatic channel optimisation'. The store has 16 APs. Before the upgrade, all APs were on 40MHz channels on 5GHz. After the upgrade, the WLC logs show most APs have been automatically reconfigured to 80MHz. What is happening, and how do you resolve it?

Hint: What does the automatic channel optimisation algorithm optimise for? How many non-overlapping 80MHz channels are available on 5GHz? What is the likely impact on CCI?

View model answer

The automatic channel optimisation algorithm has escalated channel width from 40MHz to 80MHz, likely during a low-utilisation period when the algorithm detected spare capacity and prioritised throughput. With 16 APs in a single store, 80MHz channels are creating severe CCI: there are only 6 non-overlapping 80MHz channels on 5GHz (with DFS), meaning multiple APs are inevitably sharing channels. Under load, these APs are deferring to each other constantly, degrading aggregate throughput below what the previous 40MHz configuration achieved. Resolution: immediately set a maximum channel width cap of 40MHz in the WLC RRM policy for this store. Revert all APs to 40MHz channels and redesign the channel plan using the 12 available non-overlapping 40MHz channels. Document the RRM cap in the site configuration standard to prevent recurrence after future firmware upgrades. Consider whether the automatic channel optimisation feature should be disabled entirely for high-density stores, with manual channel assignment preferred.

Q3. You are advising a public sector organisation deploying free public WiFi across a city centre library network (8 branches, each with 6โ€“10 APs). The IT team has specified WiFi 6 APs and wants to use 160MHz channels to 'future-proof' the deployment and maximise speeds for users accessing digital services. How do you respond, and what channel width would you recommend?

Hint: How many non-overlapping 160MHz channels are available on 5GHz? What is the likely client device support for 160MHz? What are the implications for the noise floor and effective range?

View model answer

Advise strongly against 160MHz channels. On 5GHz, there are only 2โ€“3 non-overlapping 160MHz channels available, which is entirely insufficient for a 6โ€“10 AP deployment โ€” every AP in a branch would be on the same channel, creating catastrophic CCI. Additionally, 160MHz increases the noise floor by 9dB compared to 20MHz, severely reducing effective range and SNR for all clients. Client device support for 160MHz on 5GHz remains limited in 2026, meaning most users would see no benefit. The recommended configuration is 40MHz on 5GHz for these branches. With 6โ€“10 APs per branch and DFS enabled, 40MHz provides 12 non-overlapping channels โ€” sufficient for a clean channel plan with good separation. WiFi 6's real value in this environment comes from OFDMA and BSS Colouring, which improve efficiency within 40MHz channels, not from wider channels. If 6GHz-capable client devices become prevalent in future, 80MHz on 6GHz can be considered at that point โ€” but 5GHz 160MHz is not the answer. Frame this to the IT team as: WiFi 6 on 40MHz channels will outperform WiFi 5 on 80MHz channels in this environment, because OFDMA and BSS Colouring address the real bottleneck (spectral efficiency and CCI), not raw channel width.