Guest Wi-Fi and your controller: portals, per-room keys and gateways
Guest Wi-Fi has two halves: the controller, which runs the access points, and the guest platform, which decides who gets online and how. They have to agree with each other, which is why a controller move is the time to look at both.
The CloudWLC team at Optaro · · 6 min read
When a guest opens a laptop in their room, two systems decide what happens next. The wireless controller owns the radio side: which WLANs exist, on which VLANs, with what security. The guest access platform owns the rest: the sign-in page, the check against the booking, the bandwidth they get and the network their devices land on. Change one, and you need to be sure of the other.
What the guest platform does
Optaro Connect is Optaro’s cloud-managed platform for hotel and hospitality Wi-Fi. In practical terms it provides:
- Cloud-managed gateways with automatic failover between two internet connections, zero-touch set-up and bandwidth policy.
- Branded guest portals for each property, with sign-in against the property management system (Opera, Mews, Stayntouch and others), social login, vouchers and event codes.
- A private network per room: each room gets its own VLAN and its own Wi-Fi key, issued at check-in and revoked at check-out.
- Personal area networks, so a guest’s phone can find the TV and speaker in their room and nobody else’s.
- Conference and event networks, marketing campaigns and surveys timed to the stay, and a Digital Concierge that answers Wi-Fi questions in several languages.
Where the two halves meet
| Guest feature | What the controller must provide |
|---|---|
| Captive portal sign-in | An open or portal-enabled WLAN that redirects new devices to the gateway |
| Per-room keys | A WLAN that checks each device’s key against RADIUS (ePSK) |
| A network per room | Dynamic VLAN assignment from the RADIUS reply |
| Conference networks | WLANs that can be created, scheduled and removed without touching the rest |
| Reliable roaming | Consistent WLAN and radio settings on every access point |
None of this is exotic, but all of it lives in controller configuration. That is why guest access deserves a line of its own in any controller migration plan: carry the WLAN and RADIUS settings across exactly, test one room end to end, then move the floor.
How it fits with CloudWLC
If you are moving a Cambium estate to hosted cnMaestro, your guest WLANs and their RADIUS settings come across with the rest of your configuration, and the portal shows you what has been prepared before anything switches.
CloudWLC Control, our own controller, builds guest access in by phase. Control covers open and WPA2-PSK WLANs with VLAN assignment, which is what portal-based guest access needs. CloudWLC Manage adds WPA2/WPA3 Enterprise, external RADIUS with accounting, dynamic VLANs, RADIUS-driven ePSK, client isolation, captive portal integration and WLAN schedules, which is the full per-room model.
Because Connect, Assure and CloudWLC come from one team, the guest’s journey can be followed from the sign-in page to the access point and back, and a guest who cannot get online becomes a traceable event rather than a complaint at reception.
Quick answers
Does changing Wi-Fi controller affect the guest portal?
It can, because the portal relies on WLAN, VLAN and RADIUS settings held in the controller. Carry those settings across exactly and test one room end to end before moving the rest.
What is a per-room Wi-Fi network?
Each room has its own key and its own VLAN, so a guest’s devices can see each other and the room’s TV or speaker, and nobody else’s. Keys are issued at check-in and revoked at check-out.
Sources
CloudWLC is an independent service from Optaro. It is not affiliated with, endorsed by or operated by Cambium Networks, HPE Aruba Networking, RUCKUS Networks, Ubiquiti or any other equipment vendor.