I'm planning to create a guest Wi-Fi network for visitors in our office. I want to use a captive portal that requires users to submit their name, email address, and phone number. After they do this, they would receive a one-time access code via email or SMS to authenticate their connection. Plus, I'd like them to enter a second access code that we post inside the building for added security—especially since we have a lot of foot traffic around here. The Wi-Fi access would expire after 24 hours or at the end of the day, whichever is sooner.
We haven't purchased any wireless access points yet, so I'm open to hardware recommendations; I'm considering Netgear, FortiAP, and Aruba, but I'm not interested in Meraki. Just to clarify, the personal information we collect isn't for marketing reasons—it's just to help identify anyone who might misuse the network. Any suggestions or advice would really help!
5 Answers
It sounds like you might be going overboard with the setup! For a guest network, I recommend using a system like Unifi. You can set up a separate VLAN with network isolation so guests can't see each other. You don't need to go as far as a captive portal; a simple password-protected access with the code posted in the building might be an easier solution for everyone involved.
For a more serious setup, you might explore something like Aruba Clearpass, but it might be more than you need. In the hospitality sector, something like RGNets rXg is used, which provides a ton of control without making the guest experience terrible. With that said, don't forget that there are limits to what devices will allow with a captive portal; keep it user-friendly!
Honestly, requiring that much personal info seems excessive. You might want to consider just gathering basic information or maybe setting up a password that changes regularly. Plus, enforcing a couple of usage rules could help keep misuse down rather than making it so complicated for users to log in.
The idea of email verification might backfire since guests won’t have internet access initially to receive their emails. Also, separating the guest Wi-Fi on a VLAN is crucial for security. Ruckus and Cisco gear are solid choices if you're still looking for hardware. Just remember, collecting too much data can complicate things without adding much value!
Totally! Ruckus has a great reputation—definitely worth considering for your setup.
If you're looking to provide a secure guest network, focus on creating a separate VLAN that prevents guests from accessing your internal network. Ask for a simple password instead of a complicated login process. Overthinking it might lead to frustration for guests. Also, consider your usage limits for each guest to ensure no single user hogs the bandwidth.
I couldn't agree more! Simplicity is key. Blocking known bandwidth hogs and requiring a password can streamline the whole experience for both you and your guests.
Yeah, changing the password often can really help prevent unauthorized access, and it keeps things simpler! Plus, you won't have to deal with any issues with users connecting without approval.