How to Change WiFi Channels to Prevent Interference

This comprehensive technical guide provides IT managers, network architects, and venue operations directors with a definitive, step-by-step approach to identifying WiFi interference sources and strategically changing WiFi channels to eliminate them. It covers 2.4 GHz and 5 GHz band planning, spectrum analysis, Radio Resource Management, and DFS considerations, grounded in IEEE 802.11 standards and real-world deployment scenarios. Implementing these strategies delivers measurable improvements in network throughput, client stability, and infrastructure ROI without requiring capital expenditure on new hardware.

📖 7 min read📝 1,647 words🔧 2 worked examples❓ 3 practice questions📚 9 key definitions

Listen to this guide

View podcast transcript

Welcome back to the Purple enterprise networking briefing. I'm your host, and today we are tackling one of the most persistent and costly issues in wireless networking: WiFi interference. If you're an IT director managing a hotel, a stadium, or a large retail chain, you know that poor WiFi isn't just an IT problem — it's a business problem. It impacts guest experience, disrupts mobile point-of-sale systems, and generates a massive volume of helpdesk tickets. Today, we're going to break down exactly how to strategically change WiFi channels to eliminate interference, optimise your RF environment, and get the most out of your infrastructure investment.

Let's start with the context. Why is channel planning so critical? The radio frequency spectrum is a shared medium. When multiple devices try to talk at the same time on the same frequency, they interfere with each other. This interference generally falls into two buckets: Co-Channel Interference, or CCI, and Adjacent-Channel Interference, or ACI.

CCI happens when access points or clients are on the exact same channel. The 802.11 protocol handles this relatively well using a mechanism called CSMA/CA — Carrier Sense Multiple Access with Collision Avoidance. Essentially, devices listen before they talk. They take turns. However, if too many devices are on the same channel, they spend all their time waiting for clear airtime, which means throughput drops and latency spikes. It's essentially a congestion issue — not unlike rush-hour traffic on a motorway.

ACI, on the other hand, is far more destructive. This occurs when devices are on overlapping frequencies — say, channel 2 and channel 4 in the 2.4 GHz band. Because the transmissions overlap but aren't perfectly aligned, the protocol can't decode them. It just sees them as pure RF noise. This raises the noise floor, causes packet collisions, and forces constant retransmissions. In a busy venue, ACI can reduce effective throughput by 60 to 70 percent.

Now, let's get into the technical deep-dive, starting with the 2.4 GHz band. The 2.4 GHz band is excellent for range and wall penetration, which is why it remains popular for IoT devices and legacy hardware. But it is severely spectrum-constrained. The entire band spans roughly 83.5 megahertz. A standard 20 MHz WiFi channel takes up around 22 MHz when you account for the spectral mask. Do the maths, and you'll see there are only three truly non-overlapping channels: Channel 1, Channel 6, and Channel 11.

This is a hard rule. If you are deploying multiple access points, you must only use channels 1, 6, and 11. Full stop. If you try to be clever and use channel 3 because it looks empty on your spectrum scan, you are guaranteeing ACI for yourself and your neighbours. I see this mistake regularly in deployments that have been configured by well-meaning but under-briefed engineers. Furthermore, ensure your channel widths on 2.4 GHz are strictly set to 20 MHz. Some controllers default to 40 MHz on 2.4 GHz, which is a configuration error in any multi-AP deployment.

Now, let's look at the 5 GHz advantage. The 5 GHz band gives us significantly more spectrum and many more non-overlapping channels. This is where you want the bulk of your enterprise traffic. The band is divided into UNII sub-bands — UNII-1, UNII-2, UNII-2e, and UNII-3 — providing access to over 20 non-overlapping 20 MHz channels in most regulatory domains. However, there are two key considerations: channel width and DFS.

First, channel width. Vendors love to market gigabit WiFi speeds, which are achieved by bonding multiple 20 MHz channels together into 40, 80, or even 160 MHz channels. While this gives a single client impressive throughput, it drastically reduces the number of independent channels available for your venue. In a high-density environment like a conference centre, a stadium, or a busy hospital ward, using 80 MHz channels will cause massive Co-Channel Interference. The best practice? Default to 20 MHz channel widths in high-density deployments. You prioritise overall network capacity and stability over peak single-client speed. Think of it this way: it's better to have 20 lanes of traffic moving at 60 miles per hour than 5 lanes moving at 100 miles per hour — the aggregate throughput is far greater.

Second, DFS — Dynamic Frequency Selection. Many 5 GHz channels share spectrum with radar systems, such as weather radar and aviation radar. If an access point on a DFS channel detects a radar signal, it must legally vacate that channel immediately and remain off it for a period of time. This causes client disconnections and what we call channel churn. If your venue is near an airport, a weather station, or a military installation, you need to carefully audit your DFS channel usage or exclude those channels entirely from your channel plan.

So, what does the implementation look like in practice? Let me walk you through the key steps.

Step one: never guess. Before you touch a single configuration, use a spectrum analyser to get an empirical baseline of your RF environment. This could be a dedicated hardware tool or a software-based survey tool integrated into your wireless LAN controller. You need to identify rogue access points, neighbouring networks, and non-WiFi interferers like microwave ovens, Bluetooth devices, and DECT phones. Establish your baseline noise floor on both bands.

Step two: formulate your channel plan. For 2.4 GHz, restrict the channel pool to 1, 6, and 11 only, and set widths to 20 MHz. If your AP density is very high, consider disabling the 2.4 GHz radio on alternating APs in a checkerboard pattern to reduce Co-Channel Interference. For 5 GHz, use 20 MHz widths in high-density areas. Evaluate DFS channels carefully based on your location. Spread your APs across as many unique channels as possible.

Step three: configure your access points. Most enterprise wireless LAN controllers offer Radio Resource Management, or RRM, which dynamically adjusts channel and power settings. While this is a useful baseline, in highly complex environments — a multi-floor hotel, a stadium with 50,000 concurrent devices, a busy transport hub — a manual, static channel plan based on a predictive site survey often yields the most stable and predictable results. Automated algorithms can sometimes react to transient interference events and cause unnecessary channel changes, which disrupts clients.

And critically: don't forget transmit power. Channel planning and power tuning are inseparable. If your access points are transmitting at maximum power, their RF cells will overlap significantly, causing Co-Channel Interference regardless of how well you've planned your channels. Reduce transmit power to create smaller, more efficient cell sizes. In a dense deployment, aim for access point transmit power in the range of 10 to 14 dBm on 5 GHz.

Step four: validate and monitor. After applying your changes, conduct a post-implementation walkthrough survey to verify the new channel plan is working as intended. Monitor your key performance indicators — retry rates, airtime utilisation, client association counts per AP, and roaming behaviour. A good WiFi analytics platform will surface these metrics clearly and alert you to emerging issues before they become complaints.

Now, let's move to some common pitfalls and a rapid-fire Q&A.

Pitfall one: 'My clients have strong signal but terrible throughput.' This is classic Co-Channel Interference. Your access points are likely transmitting at too high a power, causing significant cell overlap, or your channel widths are too wide. Reduce transmit power and drop channel widths to 20 MHz to free up airtime.

Pitfall two: 'Clients keep dropping off the network randomly, particularly in one zone.' Check your DFS event logs immediately. Your access points may be detecting radar and jumping channels. Identify which DFS channels are triggering and exclude them from your configuration for that zone.

Pitfall three: 'We deployed Auto-RF and the channel plan keeps changing.' This is channel churn. Your RRM algorithm is reacting to transient interference events. Constrain the Auto-RF sensitivity settings or switch to a static channel plan based on your survey data.

Quick question: should I use WiFi 6E's 6 GHz band to avoid all of this? Absolutely, if your client devices support it. The 6 GHz band is pristine spectrum with no legacy devices and no DFS requirements. However, it has shorter range due to higher frequency attenuation, so it requires denser AP deployments. It's the right long-term direction, but it doesn't replace the need for proper 2.4 and 5 GHz channel planning for your existing estate.

To summarise today's briefing: optimising your WiFi channels is fundamentally a zero-cost infrastructure upgrade that delivers immediate, measurable returns. By enforcing the 1-6-11 rule on 2.4 GHz, managing channel widths intelligently on 5 GHz, tuning transmit power, and validating with proper tooling, you can dramatically reduce helpdesk tickets, improve application performance, and extend the lifecycle of your existing hardware.

The key takeaways are these: interference is a spectrum management problem, not a hardware problem. You don't need to buy new access points — you need to configure the ones you have correctly. Prioritise capacity over peak speed in high-density environments. And always, always base your decisions on empirical spectrum data, not assumptions.

For detailed implementation guides, architecture references, and WiFi analytics tooling, visit the Purple resources hub at purple dot ai. Thank you for joining this briefing, and we'll see you in the next session.

Key Takeaways

✓Interference is the primary cause of poor WiFi performance in enterprise environments, manifesting as Co-Channel Interference (CCI — congestion) or Adjacent-Channel Interference (ACI — noise).
✓In the 2.4 GHz band, strictly use only channels 1, 6, and 11 with 20 MHz widths. Any other channel configuration in a multi-AP deployment guarantees destructive ACI.
✓Prioritise the 5 GHz band for enterprise client traffic due to its abundance of non-overlapping channels, but carefully manage DFS channel usage near radar sources such as airports.
✓In high-density environments, enforce 20 MHz channel widths to maximise the number of independent channels and aggregate network capacity, rather than optimising for peak single-client throughput.
✓Channel planning and transmit power tuning are inseparable. Reducing AP TX power in dense deployments improves spatial reuse and reduces CCI, counter-intuitively increasing overall throughput.
✓Always base channel planning decisions on empirical spectrum analysis data, not assumptions. Validate changes with a post-implementation survey and ongoing KPI monitoring.
✓Correct RF configuration is a zero-cost upgrade that frequently eliminates the perceived need for additional AP hardware, delivering direct ROI from existing infrastructure investment.

Executive Summary

For enterprise environments — from expansive Hospitality venues to dense Retail spaces — reliable WiFi is no longer a perk; it is critical infrastructure. Interference remains the primary culprit behind dropped connections, high latency, and poor throughput, directly impacting both operational efficiency and the Guest WiFi experience. This guide provides network architects and IT managers with a definitive, step-by-step approach to identifying interference sources and strategically changing WiFi channels to mitigate them.

By implementing vendor-neutral best practices for spectrum management, organisations can maximise their infrastructure ROI, ensure seamless client roaming, and support the growing density of IoT and user devices without compromising security or compliance standards including PCI DSS and GDPR. The core principle is straightforward: interference is a spectrum management problem, not a hardware problem. Correct configuration of existing infrastructure will, in most cases, resolve performance issues that organisations mistakenly attribute to insufficient AP density or outdated equipment.

Technical Deep-Dive

Understanding the physical layer of IEEE 802.11 networks is essential before making any configuration changes. The radio frequency (RF) spectrum is a shared medium governed by the CSMA/CA (Carrier Sense Multiple Access with Collision Avoidance) protocol, and interference generally falls into two distinct categories: Co-Channel Interference (CCI) and Adjacent-Channel Interference (ACI).

Co-Channel Interference (CCI) occurs when multiple access points or clients transmit on the exact same channel. While 802.11 protocols use CSMA/CA to manage this — devices listen before transmitting — excessive CCI forces devices to wait for clear airtime, drastically reducing throughput and increasing latency. It is fundamentally a congestion problem rather than true RF noise, and the CSMA/CA mechanism can handle a degree of it gracefully.

Adjacent-Channel Interference (ACI) is far more destructive. It happens when APs operate on overlapping frequencies — for example, channels 2 and 4 in the 2.4 GHz band. Because the transmissions overlap but cannot be decoded by CSMA/CA, they are treated as pure noise, raising the noise floor and causing packet loss and retransmissions. In a busy venue, ACI can reduce effective throughput by 60–70% and is the most common misconfiguration error encountered in enterprise deployments.

The 2.4 GHz Conundrum

The 2.4 GHz band provides better range and wall penetration but is severely constrained by limited spectrum — approximately 83.5 MHz in total. Although there are 11 to 14 channels depending on the regulatory domain, only three are truly non-overlapping: Channels 1, 6, and 11. Using any other channel in a multi-AP deployment guarantees ACI. Furthermore, this band is crowded with non-WiFi interferers including Bluetooth devices, microwave ovens, and DECT cordless phones operating in the same spectrum. For a detailed analysis of how Bluetooth Low Energy coexists with WiFi infrastructure, see our guide on BLE Low Energy Explained for Enterprise . For a broader treatment of frequency band selection, refer to Wi Fi Frequencies: A Guide to Wi-Fi Frequencies in 2026 .

The 5 GHz Advantage

The 5 GHz band offers significantly more spectrum, providing numerous non-overlapping 20 MHz channels across the UNII-1, UNII-2, UNII-2e, and UNII-3 sub-bands. This band is the correct default for enterprise client traffic. However, it introduces two key complexities: channel bonding trade-offs and Dynamic Frequency Selection (DFS).

Channel bonding — combining 20 MHz channels into 40, 80, or 160 MHz widths — increases peak single-client throughput but reduces the total number of independent channels available. In high-density environments, this causes severe CCI. DFS channels (primarily UNII-2 and UNII-2e) require APs to monitor for radar signals and immediately vacate the channel if detected, causing client disconnections. This is a critical consideration for venues near airports, weather stations, or military installations.

Implementation Guide

Changing WiFi channels should never be based on guesswork. It requires a systematic, data-driven approach.

Step 1: Conduct a Spectrum Analysis

Before making any configuration changes, establish an empirical baseline. Deploy a spectrum analyser — either dedicated hardware or the built-in tooling within your enterprise WLAN controller — to survey the RF environment across both bands. Document the following: rogue or neighbouring APs and their channel assignments, the noise floor on each channel, the presence of non-WiFi interference sources, and current AP transmit power levels. This baseline is your reference point for measuring the impact of subsequent changes.

Step 2: Formulate a Channel Plan

For the 2.4 GHz band: Restrict the channel pool strictly to channels 1, 6, and 11. Set all channel widths to 20 MHz — this is non-negotiable. If AP density is high enough to cause significant CCI even with the 1-6-11 scheme, consider disabling the 2.4 GHz radio on alternating APs in a checkerboard pattern, effectively halving the 2.4 GHz AP density while maintaining coverage through the remaining APs.

For the 5 GHz band: Maximise the use of available non-overlapping channels. In high-density deployments — conference centres, stadia, Transport hubs — enforce 20 MHz channel widths to maximise the number of independent channels. Only increase to 40 MHz in low-density areas where CCI is not a concern. Carefully evaluate DFS channel inclusion based on your specific location and proximity to radar sources. Consult your national regulatory authority's channel availability list for your specific region.

Step 3: Configure Access Points

Access your wireless LAN controller (WLC) or cloud management dashboard to apply the channel plan. Most enterprise platforms offer Radio Resource Management (RRM) or Auto-RF features that dynamically assign channels and power levels.

Approach	Best For	Risk
Manual Static Plan	Complex, high-density, or radar-adjacent venues	Requires periodic re-survey as environment changes
Auto-RF / RRM	Simpler, lower-density deployments	Can cause channel churn in volatile RF environments
Hybrid	Most enterprise deployments	Requires careful constraint configuration

In highly complex environments, a manual static channel plan based on a predictive survey typically yields better stability than relying solely on Auto-RF. Transmit power must be tuned in parallel — reduce AP TX power to 10–14 dBm on 5 GHz in dense deployments to shrink cell sizes and reduce inter-AP interference.

Step 4: Validate and Monitor

After applying changes, conduct a post-implementation walkthrough survey to validate the new channel plan. Monitor key performance indicators (KPIs) via your WiFi Analytics platform, focusing on retry rates, airtime utilisation per AP, client association counts, and roaming behaviour. A well-tuned RF environment should show retry rates below 10% and airtime utilisation below 70% during peak periods.

Best Practices

Enforce 20 MHz widths in high density. In environments like conference centres or stadia, prioritise capacity — more non-overlapping channels — over peak single-client throughput from wider channels. The aggregate network performance will be significantly higher.

Implement band steering aggressively. Configure band steering to push 5 GHz-capable clients away from the congested 2.4 GHz band. Most modern enterprise controllers support this natively. Reserve 2.4 GHz for IoT devices and legacy hardware that cannot operate on 5 GHz.

Disable legacy data rates. Disable 802.11b data rates (1, 2, 5.5, 11 Mbps) on all SSIDs. These legacy rates consume disproportionate airtime and slow down the entire network. Setting a minimum data rate of 12 or 24 Mbps forces clients to roam earlier and reduces management frame overhead.

Schedule regular RF audits. The RF environment is dynamic. New neighbouring networks, building modifications, and new equipment all change the interference landscape. Schedule quarterly RF audits to keep your channel plan current.

Integrate security and network management. Ensure rogue AP detection and mitigation are enabled to prevent unauthorised devices from causing interference or security breaches. For broader network security context, including content filtering on guest networks, review What is DNS Filtering? How to Block Harmful Content on Guest WiFi . For office-specific optimisation strategies, see Office Wi Fi: Optimize Your Modern Office Wi-Fi Network .

Troubleshooting & Risk Mitigation

Symptom: Strong signal, poor throughput. This is the hallmark of Co-Channel Interference. The noise floor is low but airtime is saturated. Audit channel assignments and AP transmit power. Reduce TX power and enforce 20 MHz channel widths to free up airtime and improve spatial reuse.

Symptom: Random client disconnections in specific zones. Check DFS event logs immediately. If APs in that zone are on UNII-2 or UNII-2e channels and are near a radar source, they will be legally required to vacate the channel, disconnecting clients. Exclude those specific DFS channels from the channel plan for affected zones.

Symptom: Channel plan keeps changing automatically. This is channel churn caused by an overly sensitive Auto-RF algorithm reacting to transient interference. Constrain the RRM sensitivity settings, increase the hold-down timer, or migrate to a static channel plan based on survey data.

Symptom: Poor performance in specific areas despite good signal. Non-WiFi interference from microwave ovens, DECT phones, or industrial equipment may be raising the noise floor. A spectrum analyser will identify these sources. The remediation is to either remove the source or migrate affected APs to the 5 GHz or 6 GHz band, which is immune to most non-WiFi 2.4 GHz interferers.

ROI & Business Impact

Optimising WiFi channels is a zero-cost infrastructure upgrade that yields immediate, measurable returns. Organisations that implement proper RF channel planning typically report a 30–40% reduction in WiFi-related helpdesk tickets within the first quarter. In Healthcare environments, a properly tuned RF environment ensures uninterrupted flow of critical telemetry data and supports compliance with clinical device communication requirements. In Retail , it guarantees seamless operation of mobile point-of-sale systems, accurate location analytics, and reliable inventory management applications.

From a capital expenditure perspective, correct channel planning frequently eliminates the perceived need for additional AP hardware. Many organisations that believe they have an AP density problem actually have a channel planning problem. Resolving the RF configuration first — before procuring additional hardware — is standard practice in any rigorous network assessment. A properly tuned RF environment also extends the operational lifecycle of existing infrastructure, deferring costly hardware refresh cycles and delivering a direct, quantifiable return on the existing capital investment.

Key Definitions

Co-Channel Interference (CCI)

Interference that occurs when multiple access points or client devices transmit on the exact same frequency channel simultaneously.

Managed by CSMA/CA, but causes congestion and reduced throughput when excessive. The primary symptom is high airtime utilisation with low throughput.

Adjacent-Channel Interference (ACI)

Interference caused by devices transmitting on overlapping but non-identical frequency channels, creating RF noise that CSMA/CA cannot decode or manage.

More destructive than CCI. Raises the noise floor, causes packet loss, and forces retransmissions. Caused by using channels other than 1, 6, and 11 on 2.4 GHz.

Dynamic Frequency Selection (DFS)

An IEEE 802.11h mechanism that requires WiFi access points to monitor for radar signals on certain 5 GHz channels and immediately vacate the channel if radar is detected.

Affects UNII-2 and UNII-2e channels. Critical consideration for venues near airports, weather stations, or military sites, where frequent radar detection causes client disconnections.

Radio Resource Management (RRM)

Automated algorithms within enterprise WLAN controllers that dynamically adjust channel assignments and transmit power levels based on real-time RF conditions.

Useful for adapting to changing RF environments, but can cause 'channel churn' — frequent channel changes — in volatile environments, disrupting client connectivity.

Channel Bonding

The process of combining multiple adjacent 20 MHz channels into wider 40, 80, or 160 MHz channels to increase peak single-client throughput.

Reduces the total number of available non-overlapping channels, increasing CCI risk in dense deployments. Should be avoided in high-density enterprise environments.

Band Steering

A WLAN controller feature that encourages dual-band capable client devices to associate with the 5 GHz band rather than the congested 2.4 GHz band.

Essential for load balancing in enterprise deployments. Preserves the limited 2.4 GHz spectrum for IoT devices and legacy hardware that cannot operate on 5 GHz.

CSMA/CA

Carrier Sense Multiple Access with Collision Avoidance. The medium access control protocol used by IEEE 802.11 WiFi, requiring devices to listen for clear airtime before transmitting.

The mechanism that governs how WiFi devices share the RF medium. High CCI forces devices to wait longer for clear airtime, directly reducing throughput and increasing latency.

Noise Floor

The aggregate level of background RF energy present in a given frequency band, measured in dBm. A higher noise floor reduces the effective Signal-to-Noise Ratio (SNR) for WiFi transmissions.

Raised by ACI, non-WiFi interference, and poor channel planning. A high noise floor forces devices to use lower modulation schemes and data rates, reducing throughput.

Spatial Reuse

The ability of multiple access points to simultaneously transmit on the same channel without interfering with each other, enabled by physical separation and appropriate transmit power levels.

The fundamental mechanism that allows high-density WiFi networks to scale. Maximised by reducing AP transmit power and using the minimum necessary channel widths.

Worked Examples

A 200-room hotel is experiencing widespread complaints of slow WiFi during the evening peak. The current deployment uses 40 MHz channels on the 2.4 GHz band across 80 APs, and Auto-RF is enabled. The WLAN controller logs show frequent channel changes throughout the evening.

Phase 1 — Immediate remediation: Reconfigure all 2.4 GHz radios to 20 MHz channel widths immediately. Restrict the 2.4 GHz channel pool to channels 1, 6, and 11 only within the controller. This alone will eliminate ACI across the deployment.

Phase 2 — Stabilise Auto-RF: Review the Auto-RF event logs. If APs are changing channels more than once per hour, the algorithm is reacting to transient interference. Increase the RRM hold-down timer and reduce the sensitivity threshold. If churn persists, migrate to a static channel plan.

Phase 3 — Band steering: Enable aggressive band steering to push dual-band devices to 5 GHz. This reduces 2.4 GHz load significantly during peak periods.

Phase 4 — Validation: Deploy a spectrum analyser post-change and monitor retry rates and airtime utilisation via the WiFi analytics dashboard for 48 hours to confirm improvement.

Examiner's Commentary: Using 40 MHz widths on 2.4 GHz is a critical configuration error in any multi-AP enterprise deployment. It consumes two-thirds of the available spectrum, guaranteeing severe Adjacent-Channel Interference across the entire venue. Restricting widths to 20 MHz and enforcing the 1-6-11 rule immediately reduces the noise floor and improves airtime availability. The channel churn from Auto-RF is a secondary issue — the algorithm is reacting to the ACI it is itself causing. Fixing the channel width resolves both problems simultaneously.

A large retail chain has deployed APs every 12 metres across a 4,000 sq metre distribution centre. Even on the 5 GHz band using 20 MHz channels, CCI is high, throughput is poor, and mobile scanning devices are experiencing frequent disconnections during peak shift hours.

Step 1 — Audit transmit power: The APs are almost certainly configured at maximum TX power (typically 20–23 dBm). At 12-metre spacing, this creates massive cell overlap. Reduce TX power to 10–12 dBm on 5 GHz to shrink cell sizes and reduce inter-AP interference.

Step 2 — Disable legacy data rates: Disable all 802.11b/g data rates below 12 Mbps. This forces scanning devices to roam to the nearest AP rather than staying associated with a distant AP at a low data rate, which consumes disproportionate airtime.

Step 3 — Review channel plan: Ensure the 5 GHz channel plan uses the maximum number of non-overlapping channels available. With high AP density, every unique channel matters.

Step 4 — Validate with post-change survey: Conduct a walkthrough survey with a spectrum analyser to confirm reduced inter-AP overlap and improved SNR across the floor.

Examiner's Commentary: In high-density deployments, excessive transmit power is the most common cause of CCI even when the channel plan is technically correct. When APs can hear each other clearly, CSMA/CA forces them to take turns, saturating airtime. Reducing TX power is the correct architectural response — it improves spatial reuse, which is the fundamental mechanism that allows high-density WiFi to scale. Disabling legacy data rates is a complementary measure that reduces airtime waste from slow management frames and sticky client associations.

Practice Questions

Q1. You are deploying a new wireless network in a multi-tenant office building. Your spectrum scan shows heavy utilisation on channels 1, 6, and 11 from neighbouring tenants. A junior engineer suggests using channels 3, 8, and 13 to 'avoid the congestion'. How do you respond, and what is the correct configuration?

Hint: Consider the difference between Co-Channel Interference (CCI) and Adjacent-Channel Interference (ACI), and which is more harmful to network performance.

View model answer

The junior engineer's suggestion is incorrect and would cause severe performance degradation. Channels 3, 8, and 13 overlap with channels 1, 6, and 11 respectively, which would introduce Adjacent-Channel Interference — the most destructive form of WiFi interference. ACI manifests as pure RF noise that CSMA/CA cannot manage, causing packet loss and retransmissions. The correct configuration is to deploy on channels 1, 6, and 11. While this will cause Co-Channel Interference with the neighbouring tenants, CSMA/CA can handle CCI gracefully by having devices take turns. The aggregate performance will be significantly better than with ACI.

Q2. A stadium deployment is using 80 MHz channels on the 5 GHz band to advertise 'Gigabit WiFi' speeds during events. Users report slow loading times, frequent disconnections, and poor video streaming quality during peak occupancy. The AP hardware is modern WiFi 6 equipment. What is the architectural flaw, and what is the remediation?

Hint: Evaluate the trade-off between peak single-client throughput and overall network capacity in a high-density environment.

View model answer

The architectural flaw is the use of 80 MHz channel widths in a high-density environment. Each 80 MHz channel bonds four 20 MHz channels together, drastically reducing the total number of non-overlapping channels available across the deployment. With many APs forced to reuse the same wide channels, Co-Channel Interference becomes severe. The solution is to reduce channel widths to 20 MHz across all APs. This increases the number of independent channels available, reduces CCI, and significantly improves aggregate network capacity. The peak throughput per client will decrease, but the number of clients that can be served simultaneously — and the quality of their experience — will increase substantially.

Q3. Your hospital network experiences intermittent client disconnections affecting medical devices in wards near the hospital's rooftop helipad. The affected APs are configured to use channels 52, 56, 60, and 64. What is the most likely cause, and what is the correct remediation?

Hint: Consider the regulatory requirements for the specific 5 GHz channels in use and what systems operate near a helipad.

View model answer

Channels 52, 56, 60, and 64 are UNII-2 DFS channels. The helicopters using the helipad, or associated aviation radar systems, are likely triggering DFS radar detection events on the APs in that zone. When radar is detected, the APs are legally required to immediately vacate those channels, causing client disconnections. The correct remediation is to exclude all DFS channels from the channel plan for APs in the zones near the helipad. Reconfigure those APs to use UNII-1 channels (36, 40, 44, 48) or UNII-3 channels (149, 153, 157, 161, 165), which are not subject to DFS requirements.