Travel Router VPN Setup for Hotel and Airport Wi-Fi
Set up a VPN on a GL.iNet travel router for hotel and airport Wi-Fi: log in to the captive portal first, then connect the VPN, enable the kill switch and test.
A travel router puts your own private Wi-Fi network between your devices and the hotel's, and with a VPN client running on it, every phone, laptop and TV you connect is protected at once. The part most guides skip is the order of operations. Hotel and airport Wi-Fi usually hides the internet behind a login page, a captive portal, and a VPN cannot connect until that login is done. Get the order wrong and you end up with a router that shows a connection but loads nothing. This guide walks through the setup that works, using GL.iNet routers as the example because they are a popular choice for travel and their documentation covers each step.

You will set up the router and the VPN at home, join the hotel network on arrival, log in to the portal, switch the VPN and kill switch on, and then verify the result with a few quick tests. Each step is explained below, along with the fixes for the problems that come up most often.
What a travel router does, and why the VPN belongs on it
A travel router is a pocket-sized router that joins an existing network, wired or wireless, and creates a second, private Wi-Fi network for your own devices. GL.iNet calls joining a Wi-Fi network this way "Repeater" mode. Your devices only ever connect to your router, with your network name and password, so they reconnect automatically in every hotel without you typing anything new.
Running the VPN on the router rather than on each device changes what it protects. Everything behind the router uses the tunnel, including devices that cannot run a VPN app at all, such as many smart TVs, games consoles and streaming sticks. The hotel network sees one device, the router, so it sees one login and one encrypted connection to your VPN server, rather than a list of your devices and the sites each one visits.
| Question | VPN on a travel router | VPN app on each device |
|---|---|---|
| Devices covered | Everything connected to the router, including TVs and consoles | Only devices that can run the VPN app |
| Hotel login pages | Log in once, for the router | Log in on every device |
| Setup effort | Once at home, then a short routine at each hotel | Install and sign in on every device |
| Speed | Limited by the router's processor and the protocol | Limited by each device's own connection |
| Protection away from the router | None; it only covers its own Wi-Fi | Works on any network the device joins |
The last row is the important trade-off. A router only protects its own Wi-Fi. When you leave the room with your phone, the router stays behind, so keep a VPN app on the devices you carry around as well. If you use a travel eSIM for mobile data, our guide to travel eSIM IP addresses explains why that connection often appears to come from another country.
Before you travel: set everything up at home
Hotel rooms are a bad place to troubleshoot. Do the slow parts on your own network, where you know the internet works, so that on the road you only repeat a short routine.
- Update the firmware. Menu names and features change between GL.iNet firmware versions, and several options in this guide only exist on version 4.6 or later.
- Set an admin password. GL.iNet's own captive-portal guide starts here. You reach the admin panel by connecting to the router's Wi-Fi, whose default name and password are printed on the bottom of the router, and opening 192.168.8.1 in a browser.
- Add your VPN provider. Set up the WireGuard or OpenVPN client as described in the next section, connect once, and confirm that sites load through the tunnel.
- Learn where the kill switch lives. The label depends on your firmware version; the table further down shows where to look.
- Note your phone's Wi-Fi address. If a portal refuses to appear later, you may need to clone the MAC address of the phone you used to log in. On an iPhone it is shown under Settings, Wi-Fi, then the network name; remember that phones often use a different private address for each network.
- Pack a short Ethernet cable. If your room has a network socket, plugging the router in by cable avoids the repeater step entirely, and wired connections are often more stable than the hotel's Wi-Fi.
Choosing the protocol and adding your VPN provider
GL.iNet routers have two VPN clients, found in the admin panel under VPN, then WireGuard Client or OpenVPN Client. WireGuard is the modern protocol and usually the better choice on a small router, because it needs less processing power for the same speed. OpenVPN is older but widely supported, and it offers a TCP mode that can help on restrictive networks.
On firmware 4.7 and later, GL.iNet's WireGuard client has built-in logins for a list of providers, so for those you only enter your credentials and choose servers. For everyone else you upload or paste a configuration file using Add Manually. The details differ by provider:
| Provider | Built-in login on GL.iNet firmware 4.7+ | Notes |
|---|---|---|
| NordVPN | Yes, in both the WireGuard and the OpenVPN client | WireGuard uses an access token from your Nord Account; OpenVPN uses the service credentials, not your login. NordVPN's own guide uses OpenVPN files. |
| Surfshark | Yes, in the WireGuard client | Uses a username and password. Surfshark's own guide covers a manual WireGuard setup. |
| hide.me | Yes, in the WireGuard client | Uses a username and password. |
| Proton VPN | No | Add a WireGuard configuration manually; GL.iNet recommends WireGuard over OpenVPN for Proton. |
| PrivadoVPN Premium | Import a configuration manually | Official GL.iNet guides cover OpenVPN and WireGuard. The configuration generator requires Premium. |
| Others listed by GL.iNet | AzireVPN, IPVanish, Mullvad, PIA, PureVPN, Windscribe and X-VPN in the WireGuard client | Any provider that offers WireGuard or OpenVPN files can be added manually. |
Two details trip people up. First, several providers use separate "service credentials" for routers. GL.iNet's guide stresses that for NordVPN these are not your account email and password, and the same applies to Surfshark. You find them in the manual setup section of your provider's web account. Second, NordVPN's own GL.iNet guide downloads OpenVPN files from the "Set up NordVPN manually" page of the Nord Account, offering both UDP and TCP versions. Download one of each for a server near you before you travel; the TCP file is your fallback if a hotel network blocks the UDP one.
Surfshark's own guide, written for GL.iNet's older 3.x firmware, takes the manual route: generate a WireGuard key pair on the manual setup page, download a server's configuration, paste it into the router with your private key in the Interface section, and then run an IP leak test and a DNS leak test. On newer firmware, the built-in Surfshark login does the same work for you.
PrivadoVPN Premium is another option. Its official GL.iNet guides explain importing an OpenVPN or WireGuard configuration generated in your PrivadoVPN account. Those manual configuration downloads require Premium. Check your router model and firmware, import the configuration into the matching VPN client, and verify the IP and DNS results before you travel.
At the hotel: the order that works
This is the routine to repeat in every hotel, airport lounge or holiday rental. The key rule is simple: the login page first, the VPN second.
- Make sure the VPN is off for now. A captive portal has to be reached directly, and GL.iNet's own captive-portal checklist includes making sure all VPN connections are disabled in the VPN Dashboard. If you leave the kill switch on, devices behind the router may have no route to the portal at all.
- Connect a phone or laptop to your router. Use your own Wi-Fi network, then open the admin panel at 192.168.8.1.
- Join the hotel network. Use the Repeater function to scan for the hotel's network and connect, entering its Wi-Fi password if it has one. If your room has an Ethernet socket, use the cable instead.
- Open the login page. GL.iNet's guide says the portal should appear on your phone or laptop after the router connects. If it does not, refresh the page or re-enter the portal address, wait about a minute for the redirect, or turn your phone's Wi-Fi off and on again and reconnect to the router.
- Complete the login. Accept the terms, or enter the room number and surname the hotel asks for.
- Switch the VPN on. Start your WireGuard or OpenVPN connection from the VPN Dashboard and wait for the green status dot.
- Switch the kill switch on. Now that the tunnel is up, turn on the kill switch so a dropped tunnel cannot fall back to the hotel connection.
- Verify. Run the checks in the verification section below before you log in to anything that matters.
When the hotel login page will not appear
Portals are the most common source of trouble, because the router sits between your browser and the hotel's login system. GL.iNet documents several fixes, in roughly this order of effort.
Use the hotspot login options (firmware 4.6 and later)
On the Join Network page, newer firmware offers two settings built for portals. Auto-Enable Login Mode for Public Hotspots puts the router into a login mode when it is connected to a hotspot without internet access. GL.iNet warns that this mode may leak your network activity to the hotspot provider, because some services are suspended and DNS switches to automatic, so use it only for the login itself. Enable Camouflage makes the router emulate the MAC address of the device you are using to open the admin panel, so the portal sees the device it expects.
Clone the MAC address that logged in
Many portals authorize one hardware address. If you logged in on your phone directly, you can make the router present the same address. GL.iNet's steps are to find the Wi-Fi address your phone uses on the hotel network, then, on firmware 4.6 or later, open INTERNET, go to the Repeater section, click Modify, set MAC Mode to Clone, enter the address and click Apply. On firmware 4.5 and earlier the setting is under NETWORK, then MAC Address, in Manual mode. Reboot the router if the change does not take effect.
Relax the settings that block portals
GL.iNet also suggests three checks: under NETWORK, then DNS, disable DNS Rebinding Attack Protection and set the mode to Automatic; in the VPN Dashboard, make sure every VPN connection is disabled; and under APPLICATIONS, make sure AdGuard Home is off. Each of these can stop the portal's redirect from reaching your browser. Once you are logged in and the VPN is running, you can switch your preferred settings back on. Many portals also only redirect pages that do not use HTTPS, so try loading a plain HTTP address if a secure site just times out.
Ask the front desk
If nothing works, GL.iNet's last suggestion is to ask the hotel staff to whitelist the router's MAC address. Give them the factory default address printed on the router, not a randomized one.
Turn on the kill switch, after the portal
A kill switch stops devices behind the router from using the plain hotel connection when the VPN is off or drops. GL.iNet describes it as restricting internet access for all connected devices when the VPN is disabled or disconnected, to prevent DNS leaks, and it recommends setting up the VPN client before enabling the kill switch. Its name and location depend on the firmware:
| GL.iNet firmware | What the kill switch is called | Where to find it |
|---|---|---|
| 4.7 or earlier | Block Non-VPN Traffic (Kill Switch in some builds) | VPN, VPN Dashboard, VPN Client section, Global Options |
| 4.8 | Tunnel Kill Switch per tunnel, plus an Enhanced Kill Switch | VPN Dashboard: gear icon next to the tunnel; Enhanced under All Other Traffic in Policy Mode |
| 4.9 and later | Tunnel Kill Switch per tunnel, plus a router-wide Enhanced Kill Switch | VPN Dashboard: gear icon next to the tunnel; Enhanced under the gear icon in the upper-right corner |
On 4.9 and later, the Enhanced Kill Switch blocks any traffic that does not match a VPN tunnel. GL.iNet notes that it does not override the kill switch set on an individual tunnel. In practice, turn on the tunnel kill switch for your VPN connection, and add the Enhanced Kill Switch if you want a router-wide guarantee that nothing leaves outside the tunnel.
Verify the connection before you use it
A green dot in the dashboard means the tunnel is up, not that every device is using it. Check from a device behind the router:
- Check the public IP address. Our IP address checker should show the VPN server's address and provider, not the hotel's internet company. Is my VPN working runs the same check with more detail.
- Run the leak tests. The DNS leak test should show your VPN provider's resolvers. Add the WebRTC leak test in each browser you use and the IPv6 leak test; GL.iNet notes that some of its routers do not support IPv6, and an address that bypasses the tunnel defeats the point.
- Test the failure case. Disconnect the VPN from the dashboard on purpose. With the kill switch on, devices behind the router should lose internet access instead of falling back to the hotel connection. Reconnect when you have confirmed it.
If the IP checker still shows the hotel's address, the device is probably connected to the hotel network directly rather than to your router, which is easy to do when both networks are in range. Our guide to a VPN that is connected but not changing your IP covers the other causes.
Common problems on hotel and airport Wi-Fi
- The VPN will not connect after the login. Some networks block VPN protocols or ports. Try a different server, then switch from WireGuard to an OpenVPN TCP configuration, which NordVPN and other providers offer alongside UDP.
- Everything stops working after a day. Portal sessions often expire. Turn off the kill switch and the VPN, repeat the login, then switch them back on.
- Speeds are poor. Hotel bandwidth is shared, and a small router's processor limits VPN throughput. Use WireGuard, choose a server close to you, and compare a speed test with the VPN off to see which layer is the bottleneck.
- Your work VPN will not connect through the router. Running a VPN inside another VPN works in many cases but not all. If your employer's client fails, exclude that laptop from the router's tunnel rather than switching protection off for everyone.
- A streaming app complains about your location. It is reacting to the VPN server's country. Choose a server where your subscription is valid, within the service's terms.
- You cannot reach the router's admin page. Make sure you are on the router's own Wi-Fi, not the hotel's, then open 192.168.8.1. Our router login guide lists the default addresses for other brands.
Is a travel router worth it?
It is worth it if you travel with several devices, with devices that cannot run a VPN app, or with family members who will not set up anything themselves. One login, one VPN connection and one familiar network name cover everyone, and the hotel sees a single encrypted connection instead of each device's traffic. It is also useful for remote work, where a stable, private network matters more than convenience.
It is not worth it if you only carry a phone. A VPN app on the phone does the same job, works on every network you join, and costs nothing extra in luggage. Either way, test before you depend on it: the few minutes of checks above are what turn a router with a VPN into a network you can trust, wherever you plug it in.
Primary sources
Standards, registries, and first-party references used to verify this guide:
- GL.iNet router OpenVPN manual setup (opens in a new tab) - PrivadoVPN. Official manual OpenVPN configuration import for GL.iNet routers. Checked November 16, 2026.
- GL.iNet router WireGuard manual setup (opens in a new tab) - PrivadoVPN. Official manual WireGuard configuration for GL.iNet routers. Checked November 16, 2026.
- Generate a WireGuard or OpenVPN configuration for manual setup (opens in a new tab) - PrivadoVPN. Configuration generator requires Premium. Free accounts use the protocols through PrivadoVPN apps. Checked November 16, 2026.
- Connect to a hotspot with captive portal (opens in a new tab) - GL.iNet. Repeater steps, the hotspot login and camouflage options on firmware 4.6+, MAC cloning paths, the DNS rebinding, VPN and AdGuard Home checks, and the whitelist fallback.
- WireGuard Client (opens in a new tab) - GL.iNet. Built-in provider logins on firmware 4.7+, including the NordVPN access token, and manual configuration.
- OpenVPN Client (opens in a new tab) - GL.iNet. The NordVPN login with service credentials, manual .ovpn uploads, the Proton VPN WireGuard recommendation and the IPv6 note.
- Block Non-VPN Traffic (opens in a new tab) - GL.iNet. Kill switch names and locations by firmware version, and the advice to set up the VPN client before enabling it.
- GL.iNet setup with NordVPN (opens in a new tab) - NordVPN. OpenVPN files in UDP or TCP versions and the service credentials from the Nord Account.
- How to set up WireGuard on GL.iNet router (3.x firmware) (opens in a new tab) - Surfshark. Manual WireGuard key pair and configuration, followed by IP and DNS leak tests. Updated September 11, 2026.
Did this article help?
IP Trackers is free with no sign-up. A small contribution helps keep the guides current and the tools running.

