Hotel Wi-Fi login and your travel router: separate the checks
A router can join hotel Wi-Fi without having usable internet or a working VPN. Treat those as separate checkpoints so a login problem does not turn into random changes to a working home setup.
Four different things can be called connected
First, your device can join the travel router’s Wi-Fi. Second, the travel router can associate with the venue’s network. Third, the venue can authorize internet access through a login page. Finally, the VPN can establish the intended route home. Progress at one stage does not prove the next stage passed.
A hotel’s sign-in or acceptance page is called a captive portal. GL.iNet’s public-hotspot documentation explains that this authorization may be needed before internet access is available. That makes it worth identifying the stage that failed before changing home-router settings.
Use the documented login process with care
Check the instructions for your actual firmware. Some GL.iNet versions offer a public-hotspot login mode. The manufacturer warns that it can suspend services and change DNS to automatic, which may expose activity to the hotspot provider. Portal assistance is therefore not evidence that the usual VPN protections remain active.
Our recommendation is to keep work devices and sensitive applications idle while resolving a portal. Use a separate administration device where practical. Do not start by broadly disabling a kill switch or making several unrelated security changes. First understand which setting the documented procedure changes, how to restore it, and whether you are permitted to use the venue’s network in that way.
Locate the failure before choosing a fix
- No connection to the venue: recheck the selected network, signal and credentials. A VPN-profile edit does not repair an incorrect Wi-Fi password.
- Venue connected, internet unavailable: check whether authorization, an access purchase or a device limit remains outstanding.
- Internet available, VPN unavailable: inspect the VPN endpoint, handshake and routing state. The portal may already be resolved.
- VPN appears connected, applications fail: examine the actual device and route instead of assuming the status badge proves everything.
These are diagnostic questions, not a universal repair sequence. Record the failing stage and change one relevant thing at a time. If a procedure requires temporary direct internet access, make that temporary exposure deliberate and limited, then restore the intended configuration.
Restore the VPN policy after authentication
After the portal accepts the login, return to the router’s VPN and DNS settings. Check what is actually active. GL.iNet’s VPN Dashboard documentation distinguishes routing modes, device policies and protection controls; menu labels and behavior depend on firmware. A policy covering one device or destination should not be mistaken for a policy covering every connected device.
Our recommended review includes the selected home exit, recent tunnel activity, the public exit observed by the intended device, DNS behavior and IPv6 handling. Check failure behavior only with a recovery plan and another way to communicate. None of these isolated observations is a substitute for the full set of checks relevant to your setup.
Know when to stop changing the router
A venue may require its staff to authorize an additional device, explain a connection limit or resolve an account problem. Ask for permitted access rather than trying to evade its controls. A login that expires later is a different event from a broken VPN installation. Keep a short note of when access stopped and which checkpoint changed.
For help, share the firmware version, failing stage and a brief redacted symptom. Do not post private keys, portal credentials or complete configuration exports. Good notes make the next diagnosis more useful than another round of speculative setting changes.
Keep the setup project for the next stop
AnchorPath organizes setup, ongoing checks and recovery into a Codex-guided project. It costs $29 once, with private ZIP delivery after confirmed payment. Review supported equipment and verification limits before buying. The owner uses the reference system; the packaged adaptations have local checks, and fresh customer-ZIP installation and recovery on hardware remain unverified. Hardware, internet and OpenAI access are separate.