Aventura, Florida · serving clients across the United States (305) 404-9404Toll-free (800) 767-8566Emergency? Get a call within 1 hour
Higher education Illustrative engagement

A campus where 10,000 devices join Wi-Fi 6E securely, and visiting scholars sign in with their home credentials

A private university in the northeastern United States, with residence halls, labs and a teaching hospital partnership, a leader in its segment.

Scale
about 24,000 students and staff, 1,100 access points, 9,800 simultaneous devices at peak, 40 buildings, eduroam roaming
Engagement
Survey, design and phased deployment over one academic year

The challenge

The campus network had been built for laptops. Now every student carried three or four devices, residence halls were full of streaming boxes and game consoles that cannot do 802.1X, lecture halls needed hundreds of simultaneous connections, and visiting researchers from other universities could not get online without a paper voucher. Sign-in used a shared password that had been circulating for years.

A university network serves some of the most varied users anywhere: first-year students with a console and two phones, faculty with managed laptops, researchers with instruments that run decades-old operating systems, and visitors who arrive for a conference. The old design relied on one campus-wide password and a wired network that stopped at the walls of each building. It could not identify who or what was connected, it could not give a visiting scholar a quick way online, and it was struggling in lecture halls with hundreds of simultaneous clients.

The design starts with identity. University-managed laptops and phones get a certificate from device management and authenticate with EAP-TLS under IEEE 802.1X, so the user never types a password into a Wi-Fi dialog. Devices that cannot do 802.1X, such as game consoles and streaming boxes, are registered by the student and receive a per-device pre-shared key tied to that person. The university's RADIUS servers also take part in the eduroam federation: a visiting scholar's request is routed by the realm in the outer identity to their home institution over RadSec, which is RADIUS over TLS (RFC 6614), and the home institution's answer decides access. The university's own students and staff roam the same way at other member campuses.

The radio design uses Wi-Fi 6E. Surveying the buildings with real client counts drove the placement of 1,100 access points; the 6 GHz band, with its 1,200 MHz of clean spectrum and mandatory WPA3, carries the dense lecture halls, while 5 GHz and 2.4 GHz remain for older clients. Switching is multi-gigabit and powered by IEEE 802.3bt PoE++, with 25G uplinks and a redundant 100G core. Behind authentication, RADIUS dynamic authorization (RFC 5176) lets the network move a device between VLANs or tighten its access list the moment its status changes, for example an expired certificate or a malware flag raised by endpoint protection.

Deployment went building by building over one academic year, with residence halls last so students were never offered an unfinished network at the start of term. The old SSID stayed on in parallel until each building had been measured, and a migration profile pushed through device management moved managed devices to the new network without a visit to a help desk. Testing included load tests with hundreds of laptops in a lecture hall, an eduroam test account at partner institutions in both directions, a RADIUS server failure during peak sign-in and a 6 GHz client-compatibility matrix, so that nobody learned in September which devices could not use the new band.

The outcome is a campus where the sign-in method follows the device rather than a shared password, visitors from other universities connect with the credentials they already have, and a lecture hall of 600 laptops keeps working. Research labs, administration, residence halls and building systems are separate segments, and a compromised student device can no longer reach administrative systems. Help desk calls about Wi-Fi fell because registration and certificates are automatic, and the university has a clear record of what is connected, which supports its obligations to protect student records.

What our team delivered

  • Wi-Fi 6E (IEEE 802.11ax with the 6 GHz band) alongside 5 GHz and 2.4 GHz, with WPA3 where required in 6 GHz and a high-density design for lecture halls based on measured client counts
  • IEEE 802.1X with EAP-TLS for university-managed laptops, using certificates issued through device management, and PEAP-MSCHAPv2 on a tightly limited path for unmanaged personal devices during transition
  • eduroam federation: the university's RADIUS servers proxy visiting users' requests to their home institutions over RadSec (RFC 6614, RADIUS over TLS), and authenticate its own users when they visit elsewhere
  • Network access control with device profiling; consoles and streaming boxes registered by the student and placed on a per-device pre-shared key, with Enhanced Open (OWE) for guests
  • RADIUS dynamic authorization (RFC 5176) to change a device's VLAN or access list the moment its status changes, such as an expired certificate or a flagged laptop
  • Separate segments for research labs, administration, residence halls, building systems and a hospital-partner network, enforced by firewalls between them
  • Multi-gigabit PoE++ (IEEE 802.3bt) access switching with 25G and 100G uplinks to a redundant core
  • Central wireless analytics and RADIUS logging, with privacy rules for how long client data is kept

Result

A campus network where the sign-in method follows the device rather than a shared password, visitors from other universities connect with the credentials they already have, and a lecture hall of 600 laptops keeps working. In the modeled year, a predictive and on-site survey set the access-point plan, the summer break was used to install in the residence halls and lecture buildings, and the 600‑seat lecture hall was load-tested with real laptops before the semester. Certificates reached managed laptops through the existing device management, and the shared passphrase network was switched off only after usage dropped to near zero.

Every sign-in, verified

Staff sign in once, but behind the scenes the device, the identity, a phone approval and your access policy are all checked before any app opens, and strangers are turned away.

Every sign-in, verifiedDiagram of user authentication. A user signs in; the device is checked for MDM and Intune compliance; the identity provider, Active Directory or Entra ID, verifies the account; an MFA push is approved on the user's phone; conditional access evaluates the policy; and access is granted to email, ERP and files. On a second pass, a sign-in from an unknown device in a new location is blocked by the conditional access policy. VERIFIED SIGN-INUserSigns inDevice checkMDM · IntuneIdentityAD · Entra IDMFA pushPhone approvalConditionalaccessPolicy checkEmailERPFilesUnknown deviceNew locationApprove?Blocked

Roaming without dropping the call

Time from leaving one access point to the first data frame on the next, split by phase. A full WPA2/WPA3‑Enterprise re-authentication repeats the 802.1X exchange; 802.11r (Fast BSS Transition) reuses cached keys, 802.11k (neighbour reports) removes the blind scan, and 802.11v (BSS transition management) lets the network steer the client. Illustrative figures.

Roaming without dropping the callStacked horizontal bars of handoff time in milliseconds. Full re-authentication 580: scan 180, authentication and association 10, 802.1X 350, four-way handshake 40. PMK caching 230. 802.11r only 200. 802.11r with k and v 40, under the 50 millisecond voice target.Handoff time by roaming method (ms)Channel scanAuth + association802.1X / EAP4-way handshake0100200300400500600ms50 ms: a voice call does not noticeFull re-authenticationno roaming aids580 msPMK caching / OKCkeys reused, still scans230 ms802.11r onlyfast transition, still scans200 ms802.11r + k + vtargeted scan, fast transition40 msIllustrative: scan 20 to 250 ms depending on channel count; EAP depends on the RADIUS round trip.

Separate by region and by business unit

Each business unit lives in its own VRF and VLAN in every region, so a problem in retail cannot reach finance. Traffic between units has to pass a firewall that denies by default and allows only what is written down.

Separate by region and by business unitA grid with three regions, Americas, EMEA and APAC, and three business units, Finance, Retail and R&D. Each cell is a separate VRF with its own VLAN and VNI. Each business unit has one overlay running across its three regional cells, shown as a row. On the right a firewall zone enforces a zero-trust policy that denies by default. A red packet from Retail trying to reach Finance is blocked at the firewall. A teal packet from R&D to the shared DNS and identity services is allowed. AMERICASEMEAAPACFinanceVRF fin · VLAN 110VNI 10110VRF fin · VLAN 110VNI 10110VRF fin · VLAN 110VNI 10110RetailVRF retail · VLAN 120VNI 10120VRF retail · VLAN 120VNI 10120VRF retail · VLAN 120VNI 10120R&DVRF rnd · VLAN 130VNI 10130VRF rnd · VLAN 130VNI 10130VRF rnd · VLAN 130VNI 10130Firewallzoneszero trustdeny bydefaultSharedDNS · IdPdenyallowVRF · L3 isolationVLAN to VNI · L2Default-deny policyEVPN-VXLAN fabricWireGuard + IPsec WANLogs to one SIEM

Per-rack bandwidth, 10G to 100G

Aggregate uplink capacity from one rack to the spine, with four uplinks per rack. 10G SFP+ (10GBASE-SR, IEEE 802.3ae) gives 40 Gb/s, 25G SFP28 (25GBASE-SR, 802.3by) gives 100 Gb/s, and 100G QSFP28 (100GBASE-SR4, 802.3bm) gives 400 Gb/s. Illustrative.

Per-rack bandwidth, 10G to 100GBar chart of per-rack uplink bandwidth: 40 gigabits per second with 10G SFP+, 100 with 25G SFP28, 400 with 100G QSFP28, four uplinks per rack in each case.Rack-to-spine capacity by optic generation0100200300400Gb/s40 Gb/s10G SFP+4 × 10G100 Gb/s25G SFP284 × 25G× 2.5400 Gb/s100G QSFP284 × 100G× 4

Frequently asked questions

Direct answers to the questions we hear most. Something else on your mind?

Send us a message
How do visiting scholars connect?

Through eduroam. The university's RADIUS servers proxy visiting users' requests to their home institutions over RadSec (RFC 6614, RADIUS over TLS), and authenticate its own users when they visit elsewhere. Visitors connect with credentials they already have, not a paper voucher.

How are devices that cannot do 802.1X handled?

Consoles and streaming boxes are registered by the student and placed on a per-device pre-shared key, and guests use Enhanced Open (OWE). Managed laptops use EAP-TLS with certificates issued through device management. RADIUS dynamic authorization (RFC 5176) changes a device's VLAN or access list when its status changes, such as an expired certificate.

How does the network handle large lecture halls?

The Wi-Fi 6E design (IEEE 802.11ax with the 6 GHz band, alongside 5 GHz and 2.4 GHz) is based on measured client counts, so a hall of 600 laptops keeps working. Access switching is multi-gigabit PoE++ (IEEE 802.3bt) with 25G and 100G uplinks to a redundant core. The network peaks at about 9,800 simultaneous devices.

Do you know if your company is safe?

Speak with a security engineer today. The first assessment call is free and confidential.

CallFree assessment