GL.iNet VPN Router Setup Guide

GL.iNet routers occupy a niche that ordinary home routers do not: small boxes you slip into a bag, plug in at a hotel desk and use to share one protected network with all your gadgets. If you search "vpn on gl inet router", you are probably one of the people who travels with a laptop, a tablet and a streaming stick and does not want to sign in to a VPN app on each of them every time.

This guide follows that travel use case from start to finish: getting the router online through unfamiliar Wi-Fi, adding a VPN client profile, locking down leaks with a kill switch, deciding which devices go through the tunnel, and fixing the usual hotel and cafe problems. Menu names and layout depend on your model and firmware version, so treat the steps as a pattern. XPASS has not verified router setups, and the supported route is the free VPNclient app. For the broader picture of routers and VPNs, see our router VPN guide.

Why people choose a travel router

A travel router solves a different problem from a home router.

• One tunnel for many devices. Phones are easy; e-readers, handheld consoles and TV sticks are not. Put them all on the travel router's Wi-Fi and they share its tunnel.
• Known Wi-Fi name and password. Your devices connect once to a network you control, then the router handles whichever hotel or cafe network is in front of it. You do not need to re-enter hotel passwords on six devices.
• Wired ports. Many hotels have a wired socket that is more stable than the Wi-Fi. A travel router can use it as its uplink.
• A layer between devices and the shared network. On shared networks your devices are less exposed to other guests, which fits the advice in the FTC's guide to public Wi-Fi networks.

The costs are real. It is another thing to charge and pack, another admin panel to maintain, and it cannot protect a phone that has wandered off the router's Wi-Fi onto mobile data. A VPN app remains the better choice for a single phone. Our comparison of a VPN router and a VPN app goes through that trade-off.

First connection and choosing a mode

Most of these routers behave the same way on first use.

1. Power it and join its own Wi-Fi. The default network name and password are printed on the label. Change them as soon as you can.
2. Open the admin panel in a browser. The address is on the label and is a private address of the kind explained in RFC 1918.
3. Set an admin password and update the firmware over a trusted connection, before your trip, ideally at home.
4. Pick how the router gets its internet. The common modes are:

Mode	How it connects	When to use it
Router (cable)	Plug a network cable from the wall or modem into the WAN port	Hotel room with a wired socket, or home use
Repeater (Wi-Fi)	Joins an existing Wi-Fi network and re-shares it	Hotels, cafes, rented apartments
Tethering	Uses your phone's connection through a cable or hotspot	When no Wi-Fi is trusted or available
Access point or extender	Adds Wi-Fi to an existing wired network	Rarely needed on trips

Different firmware versions word these differently, but the idea does not change. In repeater mode you scan for the hotel network, select it, and type its password. If the hotel gives you a room-specific code or a login page, jump ahead to the section on captive portals before you enable the VPN.

What to prepare before adding a VPN profile

A router VPN client works with raw connection details rather than the friendly app. Before travelling, check two things.

Which tunnel types the router offers. GL.iNet-style firmware usually has client pages for the common modern tunnel types and OpenVPN. The formats are described on the WireGuard site and in the OpenVPN community resources. If you do not know which type suits you, our comparison of WireGuard and OpenVPN lists the differences in plain language.

What details your VPN service supplies. The router usually imports a configuration file or accepts pasted values. The service must provide data in a format the router recognises. With XPASS, the My Pass page shows setup instructions and the connection methods that apply to your pass, and the app signs in with the username and password displayed there. Router use is untested by us, so try it at home before relying on it in a hotel with a deadline.

Treat configuration files as secrets. Keep them out of cloud notes and group chats.

Adding the VPN client profile

Look for a VPN entry in the side menu. Newer firmware has a dashboard page with separate client sections for each tunnel type. Older firmware has a single client page with a type selector.

1. Open the client page for the tunnel type that matches your details.
2. Choose the option to add a new profile or upload a configuration file. Many of these panels also let you paste the contents directly.
3. Give the profile a plain name that includes the date or purpose, such as "trip-test".
4. Save, then turn the profile on with its switch.
5. Wait for the status to change to connected. Some firmware shows a small timer or a traffic counter that begins to move.
6. Open a device on the router's Wi-Fi and check that its public address has changed.

If you have several profiles, keep the list tidy. An old profile with expired details is a common cause of "it worked last month".

Kill switch and other protective options

The most useful safety setting on a travel router is the internet kill switch. Menus may call it something like "block non-VPN traffic". The idea is simple: while the option is on, devices on the router have no internet unless the tunnel is up. A dropped tunnel then cannot silently send traffic over the hotel network. Our article on the VPN kill switch explains the concept and the trade-offs.

Be aware of two side effects. First, you must switch the kill switch off to complete a hotel login page, because the router cannot reach the portal while it is blocking everything outside the tunnel. Second, if the tunnel keeps dropping, devices lose internet repeatedly. That is the intended behaviour but it can feel like a fault.

Other options worth a look:

• DNS settings. Make sure name lookups travel through the tunnel rather than going to the hotel network.
• Change the default Wi-Fi name and password, and use a modern encryption mode.
• Switch off remote administration unless you truly need it.
• MAC address cloning, offered by some firmware, for hotels that tie access to one registered device. Use it only where the hotel's rules allow.
• Automatic reconnect, so the tunnel returns after a short outage.

Choosing which devices use the tunnel

Newer firmware lets you decide who goes through the tunnel and who does not. The idea is the router-level version of split tunneling. Policies are often based on device, on destination or on both.

A sensible traveller policy:

• Laptop, tablet and e-reader: inside the tunnel.
• Phone: inside the tunnel while it is on the router's Wi-Fi; on mobile data it follows the app or nothing.
• A work laptop with a company VPN: outside the home tunnel, so the two VPNs do not clash.
• Banking or payment apps: run them on mobile data, or outside the tunnel, if they complain.
• A local device you want to reach, such as a travel hard drive on the router's network: keep it local so file copies stay fast.

Keep the policy simple. Complicated rules are hard to debug in a hotel corridor at midnight.

Hotel captive portals and awkward networks

Many hotels, airports and cafes show a login page before the internet works. That page can confuse a travel router.

1. Connect the router to the hotel network in repeater mode with the VPN and kill switch off.
2. Look for a captive portal option in the router's interface. Many GL.iNet-style panels offer a way to open the hotel's page directly. If not, connect a laptop to the router's Wi-Fi and browse to any plain web address to trigger the page.
3. Complete the login: room number, surname, a voucher code or accepted terms.
4. Check that the router now has internet, then turn the VPN on.
5. Re-check the kill switch. Turn it back on once the tunnel is up.

If the hotel limits how many devices may register, the router counts as one, which is a quiet advantage. Read our guide on using a VPN on hotel Wi-Fi for more on hotel networks, and stick to the hotel's own rules.

Sometimes a network blocks VPN tunnels altogether. Try another tunnel type if the router has one, use the hotel's wired socket, or fall back to your phone's mobile data as the router's uplink.

Troubleshooting

The router cannot see the hotel Wi-Fi. Move closer, check that you chose the right band, and rescan. Some hotel networks hide behind a login that needs a wired connection.

Joined the network, no internet. The captive portal is probably waiting. Complete the login with the VPN off.

The VPN stays at connecting. Check the router's date and time, re-import the profile and confirm the details match the tunnel type. Test the profile at home to separate a profile fault from a hotel network fault.

Connected, but pages are slow. Travel routers have small processors, and hotel Wi-Fi is often congested. Compare speeds with the tunnel off, and avoid peak evening hours if you can.

Local devices vanish. A strict policy or kill switch may be blocking local traffic. Revisit your rules.

Everything broke after an update. Firmware updates can reset settings. Keep a backup file of your configuration and update at home, not on the road.

Limits and good habits

• The router protects the devices on its Wi-Fi only. A phone on mobile data is on its own.
• A VPN does not stop phishing or weak passwords, and it does not make you anonymous.
• Do not expect a travel router to match a desktop for speed.
• Keep the firmware current, the admin password strong and the configuration backed up.
• Hotel and venue rules still apply, and some apps dislike VPN addresses.
• If a router VPN turns out to be more hassle than benefit, the VPNclient app on each device is a legitimate alternative.

Summary

A GL.iNet-style travel router lets you share one protected network among all the devices in your bag. Set it up at home first: update the firmware, change default passwords, add and test the VPN client profile and enable the kill switch. On the road, join the venue network in repeater mode, deal with any captive portal with the VPN off, then switch the tunnel back on and verify your public address. Keep policies simple, and remember that XPASS has not verified router setups.

If apps on your devices suit you better, the pricing page explains how a fixed-length prepaid pass works.