What is a travel router? How one box puts all your devices behind a single hotel login

The short version: one connection in, one private network out

A travel router sits between the venue's internet and your devices. On one side it takes a single upstream connection. On the other it broadcasts its own Wi-Fi name and password, which never change from trip to trip. Your laptop, phone, tablet and streaming stick remember that network once and reconnect to it in every hotel.

GL.iNet describes Router mode as the default operating mode for most home and small office routers: it enables NAT, DHCP and a built-in firewall, and assigns private addresses to the devices connected to it. [1] NAT (network address translation) is the trick that matters: many devices inside share one outside address, so the network you are visiting deals with one client instead of six.

This guide is research from GL.iNet documentation and product pages. It is not a record of our own hotel testing.

Where the internet comes from, and what your devices see

GL.iNet's setup guide lists four ways to give the router internet: an Ethernet cable, an existing Wi-Fi network (Repeater), USB tethering, or a USB modem. [9] Whatever the source, your devices always see the same private network, by default at 192.168.8.1. [9]

Why one captive-portal login covers every device

A captive portal is the hotel page that asks for a room number or a click on Accept before the internet opens. Each phone or laptop that joins hotel Wi-Fi directly has to pass it. Behind a travel router only the router is on the hotel network, so you complete the portal once, from any one device connected to the router, and the access applies to the router's connection.

GL.iNet's captive-portal help shows the mechanism indirectly. When the portal will not open, its fixes include cloning the MAC address your phone used on the hotel network onto the router, or asking hotel staff to whitelist the router's factory MAC address. [3] In both cases the hotel is identifying one address, the router's, not every device behind it.

Firmware 4.6 and later adds Auto-Enable Login Mode for Public Hotspots. When it is on, the router uses a login mode for public hotspots in which some services are suspended and DNS switches to automatic. GL.iNet warns this may expose network activity to the hotspot provider. [2] If the portal still fails, the step-by-step fixes are in our captive-portal checklist.

What a travel router cannot do

It cannot add bandwidth. Every device shares the one upstream link. When a repeater connection shows as connected but has no internet, GL.iNet's first check is whether the upstream Wi-Fi itself has internet. [2]

It can slow a VPN. Running a VPN on the router moves the encryption work onto a small processor. Beryl AX lists maximums of 300 Mbps for WireGuard and 150 Mbps for OpenVPN. [6] Opal's product page lists up to 65 Mbps WireGuard and 12 Mbps OpenVPN in client mode from a local test, and says server mode is slower. [7]

It cannot always hide from venue controls. If the venue's own network uses the same address range as the router's private network, GL.iNet shows a subnet-conflict warning and asks you to change the LAN subnet, for example to 192.168.10.1. [8] And it does not change the venue's rules: if your booking or the network's terms limit how a connection may be used, a router does not lift those limits.

Two GL.iNet examples, spec for spec

Both are pocket routers that take USB-C power. The differences that matter for most travellers are Wi-Fi generation, VPN speed and the Ethernet ports. All figures below are vendor-listed, not measured by us.

Who needs one, and who can skip it

Worked example (hypothetical numbers): a family of four travels with two phones each for the adults, two tablets, two laptops and a streaming stick, nine devices in total. Without a router, each device joins the hotel Wi-Fi and passes the portal itself, and the stick may have no browser to do it. With a router, the nine devices join one familiar network at home before the trip, and someone completes the portal once per hotel.

The case is weaker for a solo traveller with one laptop and a phone. Both can pass the portal directly, and the phone's own hotspot covers the occasional gap.

• Likely worth it: several devices per room, devices with no browser for the portal, a wall Ethernet port and Wi-Fi-only laptops, or a VPN you want on every device without installing apps.
• Likely worth it: long stays where you want your devices to reconnect automatically to the same network name every time.
• Probably skip: one or two devices that pass the portal on their own, short trips, or a fast phone plan you already tether from.
• Probably skip: when the venue line is the bottleneck. The router shares that line; it does not improve it.

Sources & verification

Product details and prices can change. Check the linked provider before buying.

1. GL.iNet Router Docs 4: Network Mode Accessed 30 Oct 2026
2. GL.iNet Router Docs 4: Repeater Accessed 30 Oct 2026
3. GL.iNet Router Docs 4: How to connect a GL.iNet router to public hotspots with a Captive Portal Accessed 30 Oct 2026
4. GL.iNet Router Docs 4: Tethering Accessed 30 Oct 2026
5. GL.iNet Router Docs 4: Ethernet Accessed 30 Oct 2026
6. GL.iNet: GL-MT3000 (Beryl AX) datasheet, ver. 20250320 Accessed 30 Oct 2026
7. GL.iNet: Opal (GL-SFT1200) product page Accessed 30 Oct 2026
8. GL.iNet Router Docs 4: How to resolve a subnet conflict? Accessed 30 Oct 2026
9. GL.iNet Router Docs 4: First time setup Accessed 30 Oct 2026