The challenge
What needed fixing
The main staff Wi-Fi was running older security settings, guest Wi-Fi was being used by staff for streaming, and the 2.4 GHz band was congested (high airtime use and retry rates).
My approach
What I did, in order
Modern security without dropping legacy devices
Moved the staff network to WPA2/WPA3 transition mode with Protected Management Frames (PMF) set to optional, so newer devices get WPA3 and older ones keep working.
Tested Fast Roaming, then rolled it back
Enabled 802.11r Fast Roaming. About 50 legacy clients dropped, so I rolled it back right away and ~105 clients recovered. I kept it off and documented why.
Locked down guest Wi-Fi
Applied a 10/10 Mbps speed limit, a business-hours-only schedule, and traffic rules blocking streaming.
Fixed 2.4 GHz congestion
Set a minimum data rate and lowered transmit power so the band stops carrying slow, far-away clients.
Investigated with DPI, planned the next step
Used deep packet inspection to see what traffic was really on the network, and planned a dedicated IoT network next.
Architecture
Sanitized diagram
Results
What changed
Stronger Wi-Fi security with no lasting user impact
Guest network limited to its real purpose
Less congestion on 2.4 GHz
Coming soon. More outcome details are being confirmed.
What I learned
Takeaway
Test changes on a live clinical network with a rollback ready. Security settings have to work with the oldest device on the network, not just the newest.
Tools used
Tools used
- UniFi gateway
- UniFi access points
- WPA3 / PMF
- Traffic rules
- DPI
- Intune Wi-Fi profiles
Contact
Want the full story?
Happy to walk through the details, the trade-offs, and what I would do differently.