Why Campus Planners in Australia Need to Think About Wi-Fi 6E and Wi-Fi 7 Now
Enterprise campuses across Australia are hitting a decision point. Wi-Fi 5 access points are reaching end-of-life, Wi-Fi 6 deployments are maturing, and two newer standards — Wi-Fi 6E and Wi-Fi 7 — are competing for the next refresh cycle budget. The stakes are higher than a simple speed upgrade. These newer standards introduce fundamentally different spectrum, channel widths, and multi-radio architectures that reshape how you plan coverage, backhaul, and power delivery.
For network teams managing university campuses, hospital precincts, multi-floor office towers, or logistics facilities, the question is not just which access point to buy. It is whether your wired infrastructure, PoE budget, and management strategy can support what these new radios demand.
This guide walks through the practical planning considerations for Wi-Fi 6E and Wi-Fi 7 enterprise access point deployments, with a focus on the Australian regulatory and market environment. It also explores how open networking principles — including OpenWiFi-aligned access points and SONiC-based campus switching — can reduce vendor lock-in and give you more flexibility across refresh cycles.
Wi-Fi 6E and Wi-Fi 7: What Changes for Campus Decision-Makers
Wi-Fi 6E (IEEE 802.11ax extended to the 6 GHz band) and Wi-Fi 7 (IEEE 802.11be) represent two distinct steps forward from Wi-Fi 6. Understanding what each standard actually introduces helps you plan the right deployment for your campus.
Wi-Fi 6E opens access to the 6 GHz frequency band, which in most regulatory domains adds up to 1200 MHz of additional spectrum. For enterprise campuses, this means more non-overlapping channels, less co-channel interference, and the ability to support high-density environments without the congestion that plagues 2.4 GHz and 5 GHz deployments. Wi-Fi 6E radios operate exclusively on 6 GHz — they do not fall back to 5 GHz. This is a clean-spectrum environment.
Wi-Fi 7 builds on Wi-Fi 6E with several key enhancements:
- 320 MHz channel width: Double the maximum channel width of Wi-Fi 6E, enabling higher single-client throughput.
- 4096-QAM modulation: A denser modulation scheme that increases data rates in good signal conditions.
- Multi-Link Operation (MLO): Allows a single client to transmit and receive across multiple frequency bands simultaneously, reducing latency and improving reliability.
- Preamble puncturing: Enables use of wider channels even when parts of the spectrum are occupied by interference.
For campus planners, the practical takeaway is this: Wi-Fi 6E gives you cleaner spectrum today. Wi-Fi 7 adds throughput headroom and latency improvements that matter for real-time applications, AR/VR, and high-density environments. Many campuses will deploy both standards across different zones based on density and application requirements.
Spectrum Planning in the Australian Regulatory Context
Spectrum planning is where regulatory context directly shapes your deployment. The Australian Communications and Media Authority (ACMA) governs how the 6 GHz band can be used in Australia.
In many countries, the 6 GHz band (5925-7125 MHz) has been opened for Wi-Fi use under different power categories: Low Power Indoor (LPI), Very Low Power (VLP), and Standard Power (with Automated Frequency Coordination, or AFC). The specific ranges and power levels vary by regulatory domain.
What this means for planning:
| Consideration | Wi-Fi 6E Impact | Wi-Fi 7 Impact |
|---|---|---|
| Available spectrum | Depends on ACMA allocation (likely 500-1200 MHz) | Same as Wi-Fi 6E for 6 GHz; also uses 2.4/5 GHz |
| Channel widths | 20, 40, 80, 160 MHz | Up to 320 MHz |
| Non-overlapping channels (80 MHz) | Up to 7 in full 1200 MHz allocation | Same, but MLO uses multiple simultaneously |
| Outdoor deployment | May be restricted depending on ACMA rules | MLO may enable multi-band outdoor use |
| Interference environment | Clean (6 GHz only, no legacy devices) | Multi-band, but preamble puncturing helps |
The key planning insight for Australian campuses: if ACMA has opened only the lower 6 GHz range (5925-6425 MHz), you have fewer non-overlapping channels than in regions with the full 1200 MHz allocation. This makes AP density planning and channel assignment more critical. Confirm the regulatory details before finalising your AP count and placement.
Backhaul, PoE, and the Wired Infrastructure Behind Your Wireless
Every new generation of wireless access points demands more from the wired network beneath it. This is where many campus refresh projects stall — the APs arrive, but the switches and cabling cannot keep up.
Power over Ethernet (PoE) requirements increase with each Wi-Fi generation. Wi-Fi 6E access points with tri-radio configurations (2.4 GHz, 5 GHz, 6 GHz) typically require PoE+ (802.3at, 30W) as a minimum, with some high-performance models needing PoE++ (802.3bt, 60W or higher). Wi-Fi 7 access points with MLO and 320 MHz radios push power demands further.
Backhaul bandwidth matters just as much. A tri-radio Wi-Fi 7 access point operating at 320 MHz channel widths can theoretically deliver aggregate wireless throughput that exceeds a 1 Gbps uplink. For campus deployments, this means:
- Minimum backhaul: 2.5 GbE per AP for Wi-Fi 6E deployments with 160 MHz channels.
- Recommended backhaul: 5 GbE or 10 GbE per AP for Wi-Fi 7 deployments with 320 MHz channels and MLO.
- Uplink to aggregation: 25 GbE or higher from access switch stacks to the distribution or core layer.
This is where your campus switching infrastructure becomes the bottleneck or the enabler. Access and aggregation switches that support multi-gigabit (mGig) ports, 802.3bt PoE, and 25 GbE uplinks give you headroom for Wi-Fi 7 APs without a forklift upgrade of the wired network.
Open networking campus switches — such as those running Enterprise SONiC — provide the flexibility to match switching hardware to your exact port density, PoE budget, and uplink speed requirements without being locked into a single vendor’s pricing or feature roadmap. SONiC (Software for Open Networking in the Cloud) is an open-source network operating system originally developed for hyperscale data centres and now increasingly adopted in enterprise campus environments. Its container-based architecture and multi-vendor hardware support allow campus teams to select switching platforms based on operational fit rather than vendor allegiance.
For campus refresh planning, the wired and wireless decisions are inseparable. Plan them together.
Related xSONiC Resources
Sources Reviewed
- Connect to a Wi-Fi network in Windows - Microsoft Support: https://support.microsoft.com/en-us/windows/connect-to-a-wi-fi-network-in-windows-1f881677-b569-0cd5-010d-e3cd3579d263
- Supports: input source for finding, recommendation, claim, and evidence review.
- SONiC Foundation: https://sonicfoundation.dev/
- Supports: input source for finding, recommendation, claim, and evidence review.
- SONiC GitHub: https://github.com/sonic-net/SONiC
- Supports: input source for finding, recommendation, claim, and evidence review.
- Azure SONiC Documentation: https://azure.github.io/SONiC
- Supports: input source for finding, recommendation, claim, and evidence review.
- Open Compute Networking: https://www.opencompute.org/projects/networking
- Supports: input source for finding, recommendation, claim, and evidence review.
- Broadcom Ethernet Switching: https://www.broadcom.com/products/ethernet-connectivity/switching
- Supports: input source for finding, recommendation, claim, and evidence review.
- Marvell Switching: https://www.marvell.com/products/switching.html
- Supports: input source for finding, recommendation, claim, and evidence review.
- NVIDIA Ethernet Switching: https://www.nvidia.com/en-us/networking/ethernet-switching
- Supports: input source for finding, recommendation, claim, and evidence review.