Resolving WiFi Interference in High-Density MDU Buildings

This technical reference guide provides IT managers and property operators with practical strategies for eliminating WiFi interference in high-density Multi-Dwelling Unit (MDU) buildings. It covers the root causes of co-channel and adjacent-channel interference, the architectural shift to centrally managed WLAN infrastructure, and secure tenant isolation techniques. Implementing these strategies reduces support overheads, improves tenant satisfaction, and transforms connectivity into a revenue-generating utility.

📖 6 min read📝 1,481 words🔧 2 worked examples❓ 4 practice questions📚 10 key definitions

Listen to this guide

View podcast transcript

[0:00 - 1:00] Introduction & Context
Host: Welcome to the Purple Technical Briefing. Today we're tackling one of the most persistent headaches for IT directors and property managers: WiFi interference in high-density Multi-Dwelling Units, or MDUs. Whether you're managing a luxury apartment complex, a student accommodation block, or a sprawling resort, the problem is the same. Hundreds of tenants, hundreds of consumer-grade routers, all screaming over each other on the same frequencies. It's a recipe for dropped connections, frustrated residents, and endless support tickets. Today, we're cutting through the noise. We'll explore the technical realities of channel overlap, why standard deployment strategies fail in these environments, and how to architect a managed WiFi solution that actually delivers on its promises.

[1:00 - 6:00] Technical Deep-Dive
Host: Let's get straight into the technical architecture. The core issue in any MDU is co-channel interference and adjacent-channel interference. In a typical unmanaged scenario, every resident brings their own ISP-provided router. These devices are usually configured out-of-the-box to blast at maximum transmit power, often defaulting to the two-point-four gigahertz band on overlapping channels.

In the two-point-four gigahertz spectrum, we only have three non-overlapping channels: one, six, and eleven. When you have twenty routers in close proximity trying to use channel six, they aren't just creating noise; they are actively competing for airtime. Eight-oh-two-dot-eleven is a listen-before-talk protocol. If an access point hears another transmission on its channel, it waits. This CSMA/CA mechanism means that high density doesn't just reduce speed; it grinds throughput to a halt as devices constantly defer transmission.

Now, the solution isn't just throwing more access points at the problem. In fact, that often makes it considerably worse. The architectural shift required is moving from unmanaged, tenant-owned hardware to a centrally managed, property-wide infrastructure.

By deploying enterprise-grade access points — typically one per unit or one every other unit, depending on wall attenuation — you gain genuine control over the RF environment. A central controller can dynamically manage channel assignments and transmit power levels across the entire building.

We also need to aggressively steer clients towards the five gigahertz and six gigahertz bands. Five gigahertz offers significantly more non-overlapping channels, and six gigahertz, with WiFi six-E and WiFi seven, provides massive swaths of clean, interference-free spectrum. However, these higher frequencies attenuate faster through walls and floors. This is precisely why a proper predictive site survey — accounting for the specific construction materials of the MDU — is non-negotiable. You need to model the RF propagation accurately to ensure coverage without excessive overlap.

Let me give you a concrete example. We worked with a property management company overseeing a two-hundred-and-fifty-unit residential tower in central Manchester. Before the managed deployment, their maintenance team was logging an average of forty-seven connectivity complaints per month. The airspace audit revealed sixty-three unique SSIDs on channel six alone. After deploying a managed architecture with in-room access points, PPSK-based tenant isolation, and a checkerboard two-point-four gigahertz radio plan, monthly complaints dropped to fewer than three. That's a ninety-four percent reduction in support overhead.

[6:00 - 8:00] Implementation Recommendations & Pitfalls
Host: So, how do we implement this successfully? First, mandate the managed network. The ROI model for MDUs increasingly relies on offering WiFi as a built-in utility — bundled into the service charge or premium rent tier.

A critical implementation step is configuring micro-segmentation. Residents expect their devices — smart TVs, wireless speakers, IoT gadgets — to communicate with each other securely, just like they would on a home router. In a managed MDU environment, you must use Private Pre-Shared Keys, or PPSK, or similar technologies. This assigns a unique passphrase to each tenant, placing all their devices into a secure, isolated VLAN. They get the home network experience, but you retain full control over the RF spectrum.

The biggest pitfall? Ignoring legacy devices. While you want to push everyone to five gigahertz, you still need a two-point-four gigahertz strategy for older IoT devices — smart plugs, older printers, that sort of thing. The trick is to disable two-point-four gigahertz radios on a subset of your access points to prevent co-channel interference, creating a checkerboard pattern of two-point-four gigahertz coverage while maintaining dense five gigahertz coverage everywhere.

[8:00 - 9:00] Rapid-Fire Q&A
Host: Let's hit a few common questions quickly.

Question one: Can we just use WiFi extenders?
Absolutely not. Extenders halve your throughput and double your interference footprint. They are the enemy of high-density deployments. Full stop.

Question two: What about DFS channels in five gigahertz?
Use them cautiously. Dynamic Frequency Selection channels are excellent for capacity, but if you are near an airport or weather radar, your access points will be forced to change channels frequently, causing client disconnects. Always audit your local airspace before committing to DFS channels.

Question three: What's the business case for the capital expenditure?
The managed network pays for itself through reduced support costs, improved tenant retention, and the ability to offer tiered bandwidth packages as a revenue stream. In hospitality environments, reliable connectivity is consistently ranked as the number one amenity by guests. The ROI calculation is straightforward.

[9:00 - 10:00] Summary & Next Steps
Host: To wrap up: unmanaged WiFi in an MDU is a liability, not an asset. To solve interference, you must take control of the airspace with a centrally managed architecture. Focus on dynamic channel planning, aggressive five gigahertz and six gigahertz steering, and secure tenant isolation using Private Pre-Shared Keys.

For IT leaders, the next step is conducting a thorough RF audit of your existing properties. Quantify the interference, build the business case for a managed upgrade, and stop fighting a losing battle against hundreds of rogue routers.

Thanks for tuning in to this Purple Technical Briefing. If you'd like to explore how Purple's platform can support your MDU deployment, visit purple dot ai.

Key Takeaways

✓Unmanaged tenant routers cause severe Co-Channel Interference (CCI) in 2.4GHz, the primary driver of poor WiFi performance in MDU buildings.
✓The solution is a centrally managed, enterprise-grade WLAN architecture — not adding more consumer APs.
✓Aggressively steer clients to 5GHz and 6GHz bands to utilise the far greater number of non-overlapping channels available.
✓Implement a 'checkerboard' 2.4GHz radio plan by disabling 2.4GHz on alternating APs to prevent managed-network self-interference.
✓Use Private Pre-Shared Keys (PPSK) to provide each tenant with a secure, isolated VLAN for their smart home devices on a single shared SSID.
✓Always conduct a predictive RF site survey before deployment; for concrete-walled buildings, deploy APs inside units, not in corridors.
✓Managed MDU WiFi delivers measurable ROI through reduced support costs, improved tenant retention, and tiered bandwidth revenue streams.

Executive Summary

For IT managers and venue operations directors managing high-density Multi-Dwelling Units (MDUs) — apartment blocks, student housing, luxury resorts — unmanaged WiFi is a critical operational liability. When hundreds of tenants deploy consumer-grade routers in close proximity, the resulting co-channel and adjacent-channel interference degrades performance across the entire property. This guide outlines the technical architecture required to transition from chaotic, tenant-managed networks to a centrally controlled, enterprise-grade WiFi infrastructure. By implementing dynamic RF management, aggressive band steering, and secure micro-segmentation via Private Pre-Shared Keys (PPSK), operators can mitigate interference, reduce support overheads, and transform WiFi from a persistent complaint into a value-added utility. This approach aligns with broader connectivity strategies in Hospitality and Retail where seamless, reliable connectivity is foundational to the guest experience and directly impacts revenue.

Technical Deep-Dive

The fundamental challenge in high-density MDU environments is the intersection of RF propagation physics and the limitations of the 802.11 protocol. Understanding this is the prerequisite to resolving it.

The 2.4GHz Problem: A Spectrum Under Siege

In unmanaged scenarios, tenant routers typically default to maximum transmit power on the 2.4GHz band. With only three non-overlapping channels available — channels 1, 6, and 11 — access points inevitably share spectrum. When multiple APs operate on the same channel within radio range of each other, they create Co-Channel Interference (CCI).

Because WiFi uses CSMA/CA (Carrier Sense Multiple Access with Collision Avoidance) — a "listen-before-talk" protocol — devices must wait for the channel to be clear before transmitting. In a building where sixty routers are all competing for airtime on channel 6, devices spend far more time waiting than transmitting. This contention, not mere signal noise, is the primary driver of throughput degradation in wifi interference apartment block scenarios.

For a deeper exploration of how frequency bands interact, see our guide on Wi Fi Frequencies: A Guide to Wi-Fi Frequencies in 2026 .

Why Adding More Access Points Makes It Worse

A common instinct is to add more APs to improve coverage. In high-density MDUs, this is often counterproductive. Each additional AP broadcasting on an already-congested channel increases the total interference floor. The solution is not density of hardware; it is control of the RF environment.

The Architectural Shift: From Unmanaged to Centrally Controlled

The correct approach requires deprecating individual tenant routers in favour of a unified, centrally managed WLAN architecture. Deploying enterprise-grade APs — typically one per unit or every other unit depending on wall attenuation — allows a central controller to orchestrate the entire RF environment.

Key architectural components of a managed MDU deployment include the following.

Component	Function	Impact
Dynamic Radio Management (DRM)	Continuously monitors RF and adjusts channel assignments and transmit power	Eliminates CCI by ensuring adjacent APs never share channels
Band Steering	Pushes dual-band clients to 5GHz/6GHz	Reduces congestion on the saturated 2.4GHz band
2.4GHz Checkerboard Pruning	Disables 2.4GHz radio on alternating APs	Prevents 2.4GHz CCI while maintaining IoT device coverage
Private Pre-Shared Keys (PPSK)	Assigns unique passphrase per tenant, mapping to isolated VLAN	Provides secure "home network" experience on shared infrastructure
Minimum Basic Rate Tuning	Raises the minimum connection data rate (e.g., to 12 or 24 Mbps)	Forces sticky clients to roam to closer APs, freeing airtime

5GHz and 6GHz: The Path Forward

The 5GHz band offers significantly more non-overlapping channels — up to 25 in the UNII-1, UNII-2, and UNII-3 bands. WiFi 6E and WiFi 7 extend this further into the 6GHz band, providing up to 59 additional 20MHz channels of clean, largely interference-free spectrum. However, higher frequencies attenuate faster through walls and floors, which is why a predictive site survey modelling the specific construction materials of the MDU is non-negotiable before deployment.

Implementation Guide

Step 1: RF Audit and Predictive Design

Before a single AP is mounted, conduct a full RF audit of the existing airspace using a spectrum analyser. Document every SSID, channel, and signal strength. Then use predictive site survey tools (Ekahau, Hamina) to model AP placement, factoring in wall attenuation values specific to the building's construction. Design for capacity, not just coverage.

Step 2: Tenant Micro-Segmentation with PPSK

Tenants expect their devices — smart TVs, wireless speakers, IoT gadgets — to communicate locally, just as they would on a home router. Implementing PPSK or Multiple PSK (MPSK) is critical. Each tenant receives a unique passphrase; the controller uses this to dynamically assign all their devices to an isolated VLAN. This delivers the home network experience on shared infrastructure without broadcasting hundreds of separate SSIDs, which would itself create significant management overheads. This approach also supports ccompliance considerations discussed in Explain what is audit trail for IT Security in 2026 .

Step 3: AP Placement and Radio Configuration

For concrete-walled buildings, deploy APs inside the units rather than in corridors. Placing APs where the clients are minimises the signal path through attenuating materials. Configure the following.

Channel widths: 20MHz on 2.4GHz; 40MHz on 5GHz in standard density; 20MHz on 5GHz in extreme density to maximise non-overlapping channel count.
Transmit power: Set to auto or medium. High power increases interference range; lower power encourages proper client roaming.
802.11k/v/r: Enable these roaming assistance protocols to ensure clients transition smoothly between APs without dropping connections.

Step 4: Ongoing Monitoring and Optimisation

Deploy continuous RF monitoring via the controller's built-in tools or a dedicated platform. Key metrics to track include airtime utilisation per channel (alert threshold: >70%), client SNR distribution, and rogue AP count. Platforms offering WiFi Analytics can surface these insights alongside guest behaviour data, providing a unified operational view.

Best Practices

Leverage 6GHz for Future-Proofing. Where budget allows, deploy WiFi 6E or WiFi 7 APs. The 6GHz band is currently free of legacy device interference, making it ideal for high-bandwidth, latency-sensitive applications.

Audit DFS Channels Before Use. Dynamic Frequency Selection (DFS) channels in the 5GHz band provide additional capacity but require APs to vacate the channel immediately if radar activity is detected. In urban environments near airports or weather stations, DFS hits can cause frequent client disconnects. Always monitor for radar before enabling DFS channels in production.

Enforce Acceptable Use Policies. Even with a managed network, tenants may attempt to plug in their own routers. Use Wireless Intrusion Prevention System (WIPS) capabilities to identify and classify rogue APs. While active de-authentication of tenant devices raises legal considerations, the data provides grounds for policy enforcement.

Align with Compliance Standards. For MDUs in the public sector or those offering shared guest access, ensure the network architecture aligns with IWF Compliance for Public WiFi Networks in the UK and relevant GDPR data handling obligations. For Spanish-language markets, see Cumplimiento IWF para redes WiFi públicas en el Reino Unido .

Troubleshooting & Risk Mitigation

The Sticky Client Problem. If clients are not roaming to closer APs, the primary cause is usually transmit power set too high. A client will remain associated with a distant AP as long as it can hear it, even at a low data rate. Reduce AP transmit power and verify 802.11v BSS Transition Management is enabled.

High Airtime Utilisation with Few Clients. If a channel shows 80%+ utilisation with only a handful of connected clients, the culprit is almost certainly CCI from rogue APs or neighbouring managed networks. Use a spectrum analyser to identify the interference source and adjust channel assignments accordingly.

IoT Device Connectivity Failures. Many smart home devices are 2.4GHz-only and do not support WPA3. Maintain a dedicated 2.4GHz SSID with WPA2 compatibility mode enabled, but ensure this SSID is broadcast only from the pruned checkerboard APs to limit its interference footprint. For broader network security architecture considerations, the principles outlined in Office Wi Fi: Optimise Your Modern Office Wi-Fi Network apply equally to MDU environments.

ROI & Business Impact

Transitioning to a managed MDU WiFi solution shifts connectivity from a cost centre to a revenue-generating utility. The financial case is built on three pillars.

Value Driver	Metric	Typical Outcome
Reduced Support OpEx	Monthly connectivity complaints	80-94% reduction post-deployment
Tenant Retention	Lease renewal rate	WiFi quality is a top-3 retention factor in residential surveys
Revenue Generation	Tiered bandwidth packages	£5-£15/month premium tier adoption rates of 20-35%
Property Value	Smart building certification	Managed connectivity supports BREEAM and WELL Building Standard credits

For Healthcare and Transport operators managing MDU-style environments such as hospital wards or transit hubs, the compliance and operational benefits are equally compelling. A managed network provides the audit trail and access control necessary for regulatory compliance, while Guest WiFi platforms layer on the data capture and engagement capabilities that drive measurable commercial returns.

Key Definitions

Co-Channel Interference (CCI)

Interference caused when multiple access points and clients operate on the exact same frequency channel, forcing them to contend for airtime via CSMA/CA.

The primary cause of slow WiFi in unmanaged MDUs where dozens of routers default to channel 6. High CCI is identified by high airtime utilisation with few connected clients.

Adjacent-Channel Interference (ACI)

Interference caused by overlapping signals from channels that are not fully separated in frequency (e.g., using channel 4 and channel 6 simultaneously in 2.4GHz).

Often caused by tenants manually selecting channels they believe are 'un-crowded' but which actually partially overlap with the standard non-overlapping channels.

Private Pre-Shared Key (PPSK)

A security mechanism where multiple unique passphrases are configured on a single SSID. The controller uses the specific passphrase entered by a user to dynamically assign their devices to a pre-defined VLAN.

Essential for MDU deployments to provide secure, isolated per-tenant networks on shared infrastructure without broadcasting hundreds of separate SSIDs.

CSMA/CA (Carrier Sense Multiple Access with Collision Avoidance)

The fundamental medium access protocol of 802.11 WiFi. A device listens to the channel; if it hears another transmission, it waits a random backoff period before attempting to transmit.

Explains why high AP density on a shared channel causes slowness: devices spend more time waiting for clear airtime than actually transmitting data.

Band Steering

A controller or AP feature that discourages dual-band capable clients from connecting to the 2.4GHz band by delaying or withholding probe responses, encouraging them to associate with the less congested 5GHz or 6GHz radio instead.

A key tool for reducing 2.4GHz congestion in MDUs. Must be implemented carefully to avoid breaking connectivity for 2.4GHz-only IoT devices.

Dynamic Frequency Selection (DFS)

A regulatory requirement for 802.11 devices operating in certain 5GHz channels (UNII-2 and UNII-2 Extended) to detect radar signals and vacate the channel within 10 seconds, switching to an alternative channel.

Provides access to additional 5GHz channels for capacity, but can cause client disconnects if deployed near airports, military installations, or weather radar stations.

Minimum Basic Rate

The lowest data rate at which an AP will accept a client association or transmit management frames. Raising this value (e.g., from 1 Mbps to 12 or 24 Mbps) forces clients operating at low data rates to disconnect and roam to a closer AP.

A critical tuning parameter for high-density deployments. Low-rate clients consume airtime disproportionately, degrading performance for all other users on the channel.

Airtime Utilisation

The percentage of time a specific WiFi channel is occupied by transmissions (data, management frames, or interference). Measured per radio on each AP.

The most important metric for diagnosing MDU interference. Utilisation above 70% on any channel indicates severe congestion. Utilisation above 90% renders the channel effectively unusable.

Dynamic Radio Management (DRM)

A controller feature that automatically and continuously adjusts the channel assignments and transmit power levels of managed APs based on real-time RF environment monitoring.

The engine of a managed MDU deployment. DRM eliminates the need for manual channel planning and adapts to changes in the RF environment (e.g., new rogue APs appearing).

Wireless Intrusion Prevention System (WIPS)

A system that monitors the wireless airspace for unauthorised or rogue access points and clients, classifying them and generating alerts for network administrators.

Used in MDU environments to detect tenant-deployed rogue routers that undermine the managed channel plan and create interference.

Worked Examples

A 300-unit luxury apartment building is experiencing severe connectivity issues during evening peak hours (6pm-10pm). Tenants are using ISP-provided routers, most defaulting to 2.4GHz. An RF audit reveals 47 unique SSIDs on channel 6 alone. The property manager wants to deploy a managed solution without requiring tenants to change their devices.

Phase 1 — RF Design: Commission a predictive site survey using Ekahau, modelling the specific wall attenuation of the building (drywall vs. concrete). Design for one AP per unit, placed inside the unit near the main living area. Phase 2 — Hardware Deployment: Deploy dual-band WiFi 6 APs. Connect all APs to a central cloud-managed controller. Phase 3 — Radio Configuration: Disable the 2.4GHz radio on 50% of APs in a staggered checkerboard pattern. Set 5GHz channel widths to 40MHz. Configure the controller's Dynamic Radio Management to auto-assign channels and power levels. Phase 4 — Tenant Segmentation: Implement PPSK. Issue each tenant a unique passphrase. All tenant devices authenticate to a single SSID but are dynamically assigned to isolated VLANs. Phase 5 — Transition: Communicate to tenants that the building WiFi is now included in service charges. Provide a simple guide for connecting their devices. Phase 6 — Monitoring: Set alerts for airtime utilisation exceeding 70% on any channel. Review rogue AP reports weekly for the first month.

Examiner's Commentary: This approach directly addresses the root cause — unmanaged CCI — by taking control of the RF environment rather than trying to work around it. The checkerboard 2.4GHz pruning is the critical technical decision that prevents the managed network from recreating the same interference problem it is solving. PPSK is the differentiator that makes the enterprise network viable for residential use cases, eliminating the need for hundreds of separate SSIDs while providing genuine tenant isolation.

A 450-bed student accommodation provider is receiving complaints that WiFi speeds are acceptable during the day but unusable after 9pm. The existing infrastructure uses hallway-mounted APs on a flat-rate channel plan. The building has concrete walls between rooms.

The hallway AP placement is the primary architectural flaw. Concrete walls are attenuating the signal between the AP and the student's device, forcing connections at low data rates. Low data rate connections consume disproportionate airtime, degrading performance for all users on the channel. Recommended remediation: 1. Relocate APs to inside the rooms (one per room or one per two rooms depending on room size). 2. Increase the minimum basic rate to 24 Mbps to force clients onto higher data rates. 3. Implement band steering to push 5GHz-capable devices off the congested 2.4GHz band. 4. Enable 802.11k/v to assist roaming between in-room APs. 5. Introduce a PPSK-based per-room VLAN structure to prevent cross-room device discovery.

Examiner's Commentary: The evening peak hours pattern is a classic indicator of capacity exhaustion rather than coverage failure — students are present and active in their rooms. The concrete wall attenuation issue is a common mistake when adapting enterprise AP placement guidelines (designed for open-plan offices) to residential MDU environments. Moving APs inside the rooms is a significant operational change but is the only architecturally sound solution.

Practice Questions

Q1. You are deploying WiFi in a 10-storey student accommodation block with thick concrete walls between rooms. Your initial design places APs in the corridors, one per floor. Residents are complaining of poor speeds inside their rooms. What is the root cause and what is the correct remediation?

Hint: Consider the impact of concrete wall attenuation on signal strength and data rate, and how low data rates affect shared airtime.

View model answer

The root cause is that concrete walls are severely attenuating the signal between the corridor AP and the student's device. Devices inside rooms are connecting at very low data rates (e.g., 6 Mbps or lower). Because WiFi is a shared medium, a device transmitting at 6 Mbps consumes far more airtime than a device at 300 Mbps, degrading performance for all users on that AP. The correct remediation is to relocate APs inside the rooms (in-room deployment), placing the AP where the clients are and eliminating the concrete wall from the primary signal path. Additionally, raise the minimum basic rate to 24 Mbps to prevent low-rate associations, and enable band steering to push 5GHz-capable devices off the 2.4GHz band.

Q2. A property manager wants to offer a 'Home Network' experience where a tenant can cast from their phone to their Apple TV and control their smart plug, but Tenant A must not be able to see or access Tenant B's devices. The property has a single managed SSID. What technology must be implemented and how does it work?

Hint: Think about how to segment users on a single shared wireless infrastructure without creating hundreds of separate SSIDs.

View model answer

Implement Private Pre-Shared Keys (PPSK) or Multiple PSK (MPSK). The property broadcasts a single SSID. Each tenant is issued a unique passphrase. When a tenant's device connects and enters their passphrase, the controller validates it and dynamically assigns all devices using that passphrase to a dedicated, isolated VLAN. Devices within the same VLAN can communicate locally (enabling casting and smart home control), while devices in different VLANs are isolated from each other at Layer 2. This provides the home network experience without the management overhead of hundreds of separate SSIDs and without the security risk of a single shared passphrase.

Q3. Your controller dashboard shows 87% airtime utilisation on Channel 6 in the east wing of a 200-unit apartment building, despite only 8 clients being actively connected to your managed APs on that channel. What is the most likely cause and what are your next two diagnostic steps?

Hint: Airtime utilisation reflects all 802.11 activity on the channel, not just traffic from your managed clients.

View model answer

The most likely cause is severe Co-Channel Interference (CCI) from rogue APs — tenant-owned routers — operating on Channel 6 in the east wing. Your managed APs are hearing these rogue transmissions and deferring their own transmissions via CSMA/CA, driving up utilisation even with few active managed clients. Diagnostic step 1: Use the controller's WIPS or a spectrum analyser to identify and count rogue APs operating on Channel 6 in the east wing. Diagnostic step 2: Instruct the controller's Dynamic Radio Management to reassign your managed APs in the east wing to Channel 1 or Channel 11 to escape the interference. Monitor airtime utilisation after the channel change to confirm improvement.

Q4. You are advising a property manager on whether to enable DFS channels in the 5GHz band to increase capacity in a 180-unit apartment complex located 2km from a regional airport. What is your recommendation and why?

Hint: Consider the regulatory requirements of DFS and the operational impact of radar-triggered channel changes.

View model answer

Recommend against enabling DFS channels without first conducting a 48-72 hour passive radar monitoring scan of the airspace. DFS channels (UNII-2 and UNII-2 Extended) require APs to vacate the channel within 10 seconds of detecting radar activity. A regional airport 2km away is highly likely to generate radar returns that trigger DFS events. Each DFS hit forces all clients on that channel to disconnect and reconnect on a new channel, creating a poor user experience. The recommendation is to first maximise the use of non-DFS 5GHz channels (UNII-1: channels 36, 40, 44, 48) and the 6GHz band if WiFi 6E APs are deployed. Only enable DFS channels if the radar monitoring confirms the airspace is clean.