A hospital upgraded to WiFi 6 expecting better performance. Instead, their IoT devices couldn't connect, and throughput dropped in high-density areas. The problem? They deployed WiFi 6 APs without a proper site survey and kept the old channel plan.
WiFi 6 (802.11ax) isn't just 'faster WiFi.' It's fundamentally different technology designed for dense environments. Deploying it wrong wastes the investment. Here's how to do it right.
What is WiFi 6 (802.11ax)?
WiFi 6 is the latest WiFi standard, designed for high-density environments with many connected devices. Key technologies include OFDMA (simultaneous multi-user communication), MU-MIMO (multiple simultaneous streams), BSS Coloring (reduced interference), and Target Wake Time (improved battery life for IoT).
The practical difference: WiFi 6 handles 4x more devices per AP than WiFi 5, with 40% faster throughput in congested environments.
Why WiFi 6 Matters for Enterprise
Modern offices have 3-5 WiFi devices per person: laptop, phone, tablet, smartwatch, IoT badge. Conference rooms pack 30+ devices into a small space. WiFi 5 struggles with this density.
WiFi 6 solves this with OFDMA. Instead of one device at a time per channel, OFDMA lets multiple devices communicate simultaneously. It's like adding more lanes to a highway.
How to Deploy WiFi 6: Best Practices
Step 1: Site Survey
Before deploying any APs, conduct a thorough site survey. Measure: signal strength in all areas, existing interference sources, physical obstacles (walls, floors), and expected device density.
Use tools like Ekahau or NetSpot for predictive surveys. Walk the site with a survey tool for validation. Don't skip this step - it's the difference between a successful deployment and a disaster.
Step 2: AP Placement
WiFi 6 APs have different radiation patterns than WiFi 5. Mount them at the right height (ceiling mount, 3-4 meters optimal). Space them based on survey results, not a fixed grid.
High-density areas (conference rooms, auditoriums) need more APs with lower transmit power. This creates smaller cells with less interference.
Step 3: Channel Planning
WiFi 6 operates on 2.4 GHz, 5 GHz, and 6 GHz (WiFi 6E) bands. Plan channels to minimize interference:
2.4 GHz: Use only channels 1, 6, 11. Avoid overlapping channels. 5 GHz: Use DFS channels when possible (less crowded). 6 GHz (WiFi 6E): Clean spectrum with 59 new channels.
Enable automatic channel selection on your APs. Modern WiFi 6 controllers optimize channels dynamically.
Step 4: Security Configuration
Enterprise WiFi 6 security: Use WPA3-Enterprise (not WPA2). Deploy 802.1X authentication with RADIUS. Enable protected management frames (PMF). Segment corporate and guest traffic on separate VLANs.
WPA3 provides stronger encryption and protection against offline dictionary attacks. If your devices don't support WPA3, use WPA2-Enterprise as a fallback.
Step 5: Performance Optimization
Enable band steering to push capable devices to 5 GHz/6 GHz. Configure minimum data rates to prevent slow clients from consuming airtime. Enable OFDMA and MU-MIMO (they're on by default on most WiFi 6 APs).
Set transmit power appropriately. Higher power isn't always better - it creates larger cells that cause more interference.
Best Practices
1. Don't mix WiFi 6 and WiFi 5 in the same area without planning. WiFi 6 APs can serve WiFi 5 clients, but the reverse isn't true.
2. Plan for IoT. WiFi 6's Target Wake Time improves IoT battery life by 7x. Enable it for compatible devices.
3. Use a WiFi controller. Managing 50+ APs without centralized management is impossible. Fortinet's FortiAP with FortiGate is a solid choice.
4. Monitor continuously. WiFi performance changes as users move, devices connect, and interference sources shift. Monitor and adjust ongoing.
Common Mistakes
Mistake 1: Deploying without a site survey. Every building is different. What worked in one office may not work in another.
Mistake 2: Using too much transmit power. High power creates large cells that interfere with each other. Low power, more APs is usually better.
Mistake 3: Ignoring 6 GHz (WiFi 6E). If your APs support it, use 6 GHz for high-bandwidth devices. It's clean spectrum with no legacy interference.
Conclusion
WiFi 6 transforms wireless performance in dense environments, but only if deployed correctly. Start with a site survey, plan your channels, use WPA3 security, and optimize for your specific environment. The investment pays off in user satisfaction and reduced WiFi complaints.
Want to go deeper? Explore [Run infrastructure services](/en/products/run), [industry solutions](/en/solutions), or [contact our team](/en/contact).
FAQ
Q: Do I need to replace all my APs for WiFi 6? A: Not immediately. WiFi 6 APs serve older devices. Upgrade in phases, starting with high-density areas where the improvement is most noticeable.
Q: What's the difference between WiFi 6 and WiFi 6E? A: WiFi 6E adds 6 GHz band support. It's cleaner spectrum with more channels. WiFi 6E APs also support WiFi 6 on 2.4/5 GHz.
Q: How many APs do I need? A: Depends on density and building materials. General rule: 1 AP per 25-30 users in an office. More for high-density areas.
Q: Is WiFi 6 backward compatible? A: Yes. WiFi 6 APs support WiFi 5, 4, and 3 clients. But older clients won't benefit from WiFi 6 features.
Threat Landscape and Current Attack Vectors
Understanding the current threat landscape is essential for making informed security decisions. In 2025, the most common attack vectors include ransomware (up 150% from 2024), supply chain attacks (targeting software vendors and managed service providers), credential stuffing (exploiting password reuse across services), and zero-day exploits (targeting unpatched vulnerabilities).
According to the 2025 Verizon Data Breach Investigations Report, 68% of breaches involve a human element (phishing, stolen credentials, or errors). This means technology alone is not enough - you need people, processes, AND technology working together.
Implementation Roadmap
We recommend a phased approach to implementation. Phase 1 (Weeks 1-4): Assessment and design. Document current state, identify gaps, design target architecture. Phase 2 (Weeks 5-8): Deploy core components. Install and configure the primary solution in a test environment. Phase 3 (Weeks 9-12): Pilot testing. Deploy to 20-30% of users, collect feedback, refine configuration.
Phase 4 (Weeks 13-16): Full deployment. Roll out to remaining users with minimal disruption. Phase 5 (Weeks 17-20): Optimization. Fine-tune policies, optimize performance, and document procedures. This timeline works for most medium enterprises (200-500 users).
Compliance and Regulatory Considerations
If your organization is subject to regulatory requirements (PCI DSS, HIPAA, ISO 27001, GDPR), ensure your implementation addresses these requirements from the start. Retrofitting compliance is significantly more expensive than building it in. We recommend creating a compliance matrix that maps each regulatory requirement to specific technical controls.
Common compliance gaps we see: insufficient audit logging (PCI DSS requires 12 months of logs), missing encryption at rest (required by HIPAA and GDPR), inadequate access controls (required by ISO 27001), and missing incident response procedures (required by all frameworks).