2.4GHz vs 5GHz en entreprise : quand utiliser quelle bande

2.4GHz vs 5GHz in the Enterprise: When to Use Which A Purple WiFi Intelligence Podcast — Approximately 10 Minutes --- INTRODUCTION AND CONTEXT — approximately 1 minute Welcome to the Purple WiFi Intelligence podcast. I'm your host, and today we're cutting straight to one of the most persistent decision points in enterprise wireless networking: the 2.4 gigahertz versus 5 gigahertz debate. If you're an IT director, a network architect, or a venue operations lead, you've almost certainly had this conversation — whether it's a hotel GM asking why guests are complaining about slow WiFi in the rooms, or a retail operations director wondering why their handheld scanners keep dropping off the network. The answer, more often than not, comes back to band allocation and band steering configuration. So let's get into it. --- TECHNICAL DEEP-DIVE — approximately 5 minutes Let's start with the physics, because the physics dictates everything downstream. The 2.4 gigahertz band operates on a lower radio frequency. Lower frequency means longer wavelength, and longer wavelength means better penetration through physical obstacles — concrete walls, steel shelving, elevator shafts, the kind of structural elements you find in every commercial venue. If you're deploying in a listed building, a multi-storey car park, or a hospital ward with thick internal walls, 2.4 gigahertz is your coverage workhorse. It will reach where 5 gigahertz simply cannot. The trade-off is congestion. The 2.4 gigahertz band has only three non-overlapping channels in most regulatory domains — channels 1, 6, and 11. In a high-density environment like a conference centre or a shopping mall, you are competing for those three channels with every neighbouring network, every Bluetooth device, every baby monitor, and every microwave oven in the vicinity. The result is co-channel interference and adjacent-channel interference, which degrades throughput and increases latency even when signal strength looks perfectly acceptable on paper. The 5 gigahertz band is a different story. You have up to 25 non-overlapping 20-megahertz channels available, depending on your regulatory domain and whether you're using DFS channels. You can run 40, 80, or even 160-megahertz channel widths to achieve dramatically higher throughput. Under IEEE 802.11ac — Wi-Fi 5 — you're looking at theoretical maximums of around 3.5 gigabits per second on a single spatial stream configuration, and with Wi-Fi 6 and 802.11ax, that extends further still. In practice, real-world throughput in a well-designed 5-gigahertz deployment will be three to five times what you'd achieve on 2.4 gigahertz under equivalent load. The limitation is range and penetration. The 5 gigahertz signal attenuates more rapidly through building materials. Free-space path loss is higher at 5 gigahertz than at 2.4 gigahertz. So you need more access points to achieve equivalent coverage, which has direct implications for your capital expenditure and your structured cabling budget. Now, where does this leave you from a deployment strategy perspective? The answer for most enterprise environments is: you need both, and you need them working together intelligently. This is where band steering becomes critical. Band steering is the mechanism by which your wireless infrastructure encourages — or in some implementations, forces — capable dual-band client devices to associate on the 5 gigahertz band rather than defaulting to 2.4 gigahertz. The logic is straightforward: if a device is within adequate range of a 5 gigahertz signal, it should be using it. Keeping capable devices on 2.4 gigahertz wastes airtime, increases co-channel interference, and degrades the experience for the devices that genuinely need 2.4 gigahertz — your IoT sensors, your legacy point-of-sale terminals, your access control readers. The implementation of band steering varies by vendor. The most common approach is to suppress probe responses on the 2.4 gigahertz radio for clients that are also visible on 5 gigahertz, effectively nudging them toward the higher band. More sophisticated implementations use RSSI thresholds — typically around minus 70 dBm on 5 gigahertz — to determine whether a client is genuinely within usable range before steering it. If the 5 gigahertz signal is too weak, the client falls back to 2.4 gigahertz gracefully. One important nuance: band steering is not a substitute for good RF design. If your 5 gigahertz coverage has gaps, band steering will create association failures and client frustration. You need to validate your RF survey before enabling aggressive band steering policies. On the security side, there are important considerations as well. The 2.4 gigahertz band is more susceptible to certain types of deauthentication attacks and rogue AP interference simply because of the congested channel environment. If you're running WPA3 with Protected Management Frames — which you should be, for any network carrying sensitive data — this mitigates much of the management frame vulnerability. For environments subject to PCI DSS compliance, particularly retail and hospitality, your wireless security posture needs to account for band-specific attack vectors. Your guest network and your payment network should be on separate SSIDs with VLAN segregation regardless of which band they operate on. --- IMPLEMENTATION RECOMMENDATIONS AND PITFALLS — approximately 2 minutes Let me give you the practical guidance. For a hotel deployment, the typical recommendation is to use 2.4 gigahertz for in-room coverage where you have thick concrete or masonry walls between access points and guest devices, and to use 5 gigahertz as the primary band in common areas — lobbies, conference rooms, restaurants — where density is high and devices are modern. Band steering should be enabled with a conservative RSSI threshold of around minus 72 dBm on 5 gigahertz to avoid steering clients into marginal coverage zones. If you're running Purple's Guest WiFi platform, your analytics will show you band association distribution in real time, which lets you tune these thresholds based on actual client behaviour rather than guesswork. For retail environments, the picture is more complex because you're managing two distinct populations: guest consumer devices and operational devices. Your handheld scanners, your electronic shelf labels, your EPOS terminals — many of these are 2.4 gigahertz only, and they need clean, dedicated airtime. The recommendation here is to run a separate SSID on a dedicated 2.4 gigahertz radio for operational devices, and use the 5 gigahertz band for guest WiFi. This prevents consumer devices from polluting the operational band and gives you clear QoS boundaries. The most common pitfall I see in enterprise deployments is over-reliance on band steering without validating the underlying RF design. Band steering does not fix coverage gaps. If you're seeing high rates of band steering failures in your controller logs, the first thing to check is your 5 gigahertz coverage map, not your steering configuration. The second pitfall is channel width misconfiguration. Running 80-megahertz channels in a high-density environment sounds appealing on paper — more throughput per channel — but it actually reduces the number of available non-overlapping channels and increases co-channel interference. In high-density deployments, 40-megahertz channels on 5 gigahertz typically deliver better aggregate throughput than 80-megahertz channels. --- RAPID-FIRE Q AND A — approximately 1 minute Let me run through a few questions I hear regularly. Should I disable 2.4 gigahertz entirely? Almost never. You'll break IoT devices, legacy hardware, and clients at the edge of your coverage zone. The exception is a purpose-built high-density environment like a sports arena press box where every device is modern and within close range of an access point. Does Wi-Fi 6 change this calculus? Partially. Wi-Fi 6 introduces OFDMA and BSS Colouring, which significantly improve 2.4 gigahertz efficiency in dense environments. But the fundamental physics of frequency still apply — 5 gigahertz will always offer more channel capacity. What about 6 gigahertz? Wi-Fi 6E and Wi-Fi 7 add the 6 gigahertz band, which offers even more channel capacity than 5 gigahertz. But client device penetration is still limited, and the range characteristics are even shorter than 5 gigahertz. Plan for it in new deployments, but don't bet your current infrastructure on it. --- SUMMARY AND NEXT STEPS — approximately 1 minute To summarise: 2.4 gigahertz gives you range and penetration at the cost of capacity. 5 gigahertz gives you throughput and channel availability at the cost of range. In any enterprise venue, you need both, configured deliberately, with band steering tuned to your specific RF environment and client population. The practical next steps are: run or commission an RF survey if you haven't done one in the last 18 months; audit your band steering configuration against your controller logs; and segment your operational and guest device populations onto separate SSIDs with appropriate QoS policies. If you want to go deeper on how telemetry data from your wireless infrastructure can inform these decisions, I'd recommend reading Purple's guide on the hidden cost of telemetry data on corporate WLANs — the link is in the show notes. Thanks for listening. We'll be back with more practical enterprise WiFi guidance shortly. --- END OF SCRIPT