All field notes
Hospitality
Hotel guest WiFi checklist before peak season
Asif Khan 16 May 2026#Hospitality#WiFi#pfSense
Peak season is the worst time for your guest WiFi to fail — and the most likely time for it to fail. Here are twelve things to check before the May bank holiday rush.
Network design
- Guest VLAN is fully isolated. No route to back-office, PMS, POS, CCTV, or staff devices. Test it by trying to ping your PMS server from a phone on guest WiFi. If you get a reply, you have a problem.
- Bandwidth caps per device. One guest streaming 4K at 25 Mbps shouldn't ruin the night for the other 47. We typically set 8 Mbps down / 4 Mbps up per device with burst.
- DNS isn't pointing at your router. Your router shouldn't be the recursive resolver for guests. Point them at Cloudflare (1.1.1.1) or Google (8.8.8.8). This avoids the cache-poisoning issue that took down half of Irish independent hotels in August 2024.
- Captive portal works from every access point. Test by walking through every public area with a fresh device. Reception. Bar. Restaurant. Each bedroom floor. Garden seating. The 'fresh device' part matters — a phone that's already been on the network will skip the portal.
Compliance & guest experience
- GDPR T&C banner with consent capture. Required since 2018. Most captive portals we inspect haven't been updated since.
- Email-on-portal opt-in is genuinely optional. Ticking a 'consent to marketing' box can't be required to access the WiFi. We see this wrong in 60% of hotels we audit.
- Connection-log retention set deliberately. Irish guidance is 12 months for B&B / hotel guest authentication logs, automatically purged thereafter. Set the retention in the captive portal config, don't leave it at infinity.
- Session timeout is reasonable. 24-hour sessions for hotel guests. Not 'forever'. Not '30 minutes' (the second-worst experience).
Resilience
- 4G/5G failover is configured and tested. Most Irish hotels have a backup SIM that nobody has ever actually failed over to. Test it. The day a JCB cuts your fibre is too late.
- Access point firmware is current. Schedule firmware updates outside the August rush. We've seen properties go to peak season with 18-month-old firmware containing known vulnerabilities.
- One person knows the captive-portal admin password. And it's not the GM, who's on a beach in Lanzarote. We're surprised how often a guest WiFi outage at 9pm becomes a 2am scramble because the credentials are locked in someone's head.
The big one
- You know who you'd call at 11pm on a Sunday in August. Your broadband provider doesn't take responsibility for the captive portal. Your captive-portal vendor doesn't answer at 11pm. We do. Get hospitality IT on a retainer.
More field notes
Something here resonate? Talk to us →
