GL.iNet Slate AX: A Travel Router That Doubles as a WireGuard Gateway

A palm-sized box that turns any hotel Wi-Fi into your own network

Contents

The real problem with hotel and airport Wi-Fi is that every device you own has to independently trust that network and independently run whatever VPN client you want active — the network’s own security is only part of it. A phone, a laptop, and a games console (which typically can’t run a VPN client at all) all end up either exposed or requiring separate, per-device configuration every time you connect somewhere new. A travel router sits between you and the untrusted network once, and everything behind it — phone, laptop, console, whatever you brought — is protected without touching a single client app. The GL.iNet Slate AX is the specific model I’ve settled on for this after trying a couple of others, mainly because it runs a genuinely capable version of OpenWrt with a properly integrated WireGuard client, rather than a stripped-down consumer firmware with a VPN checkbox bolted on.

What a Travel Router Actually Solves

The core job is protocol translation and trust isolation. You connect the Slate AX to the untrusted network — hotel Wi-Fi, an Ethernet jack in a shared office, a mobile hotspot — as its WAN uplink, and it presents its own trusted Wi-Fi network (and a couple of Ethernet ports) to everything you actually own. From the perspective of your laptop and phone, they’re on your network, behind your firewall rules, regardless of how sketchy the actual uplink is. If you’re additionally routing that uplink through WireGuard to a VPN provider or your own home network, every device behind the router inherits that tunnel automatically, with zero per-device configuration.

PhoneLaptopConsoleTravelrouterUntrusteduplinkVPN serveryour networkany networktunnel end
One tunnel on the router covers every device behind it.

This matters most for devices that can’t run a VPN client themselves at all — a smart TV, a game console, a streaming stick — which are otherwise stuck trusting whatever network they’re plugged into directly.

Setting It Up

The Slate AX ships with GL.iNet’s own web UI layered over OpenWrt, which handles the common cases (WAN uplink selection, Wi-Fi client mode to join an existing network as WAN, basic firewall rules) without needing the OpenWrt CLI at all. WireGuard configuration is the part worth walking through, because it’s the whole point of the device for most people using it as a security tool rather than just a Wi-Fi range extender.

Under the GL.iNet UI’s VPN section, adding a WireGuard client tunnel is a matter of importing a configuration file — generated by your own WireGuard server, or provided by a commercial VPN service that supports the protocol:

1
2
3
4
5
6
7
8
9
[Interface]
PrivateKey = <client-private-key>
Address = 10.10.0.2/24
DNS = 10.10.0.1

[Peer]
PublicKey = <server-public-key>
Endpoint = vpn.example.com:51820
AllowedIPs = 0.0.0.0/0, ::/0

Import that through the UI (or drop it in via SSH at /etc/config/network for a manual setup), enable the tunnel, and set it as the default route. Every device connecting to the router’s Wi-Fi from that point on has its traffic tunnelled without any further configuration on the device itself.

Using It as a Gateway to Your Own Network, Not Just a Commercial VPN

The more interesting homelab use case is running the WireGuard tunnel to your own home network rather than a commercial VPN provider — turning the travel router into a portable extension of your LAN. Point the AllowedIPs at your home subnet specifically rather than 0.0.0.0/0, and only traffic destined for your home network routes through the tunnel, while everything else goes out the local uplink directly (a split-tunnel setup):

1
2
3
4
[Peer]
PublicKey = <home-server-public-key>
Endpoint = home.example.com:51820
AllowedIPs = 192.168.1.0/24

That configuration means you can reach a NAS, a self-hosted service, or a Home Assistant instance sitting on your home LAN from anywhere, on any device you brought with you, without installing WireGuard on each one — a genuinely different experience from setting up WireGuard per-device, and closer to the flexibility discussed in routing every device through a home WireGuard endpoint, just from the opposite end of the tunnel.

The only line that differs between the two modes is AllowedIPs:

Full tunnelSplit tunnel
AllowedIPs0.0.0.0/0, ::/0192.168.1.0/24
Goes through the tunnelAll trafficOnly traffic for the home subnet
Everything elseAlso tunnelledLeaves via the local uplink
SuitsA commercial VPN or a full home exitReaching a NAS or Home Assistant at home

Where This Sits Against a Phone-Only VPN

A phone or laptop running its own WireGuard client directly is simpler for a single device and doesn’t require carrying extra hardware. The travel router earns its keep specifically when you’re travelling with more than one device, or with a device that structurally can’t run a VPN client — and it earns it further by giving you one shared, trusted Wi-Fi network for everything, rather than every device separately negotiating the untrusted network’s captive portal and Wi-Fi password.

The Hardware, Briefly

The specifics that actually matter for a travel router: dual-band Wi-Fi 6, a Gigabit WAN port plus a couple of Gigabit LAN ports, USB-A/USB-C ports usable for tethering to a phone’s mobile hotspot over USB rather than Wi-Fi-to-Wi-Fi (which avoids the awkward “one radio uplinking while trying to also host a second network” compromise cheaper travel routers make), and power over USB-C, so a normal phone charger and cable is all you need to pack rather than a dedicated power brick. It’s small enough to disappear into a laptop bag’s side pocket, which is the entire point of the category — a travel router that’s inconvenient to carry defeats its own purpose. Weight and size specifics vary slightly by hardware revision, but every version in this line has stayed comfortably within “fits next to a phone charger in a pocket” territory, which is the practical bar that matters more than a precise gram count.

A small white GL.iNet travel router with folded-out antennas, powered from an Anker USB power bank.
A GL.iNet travel router running from a USB power bank, a model from the same family rather than the Slate AX itself. Photo: Travel router and power bank by Danielrosehill, CC BY 4.0, via Wikimedia Commons.

Beyond WireGuard: Ad Blocking and a Guest Network on the Road

GL.iNet’s firmware bundles AdGuard Home, which is worth turning on regardless of whether you’re also running a VPN tunnel — it blocks ad and tracker domains at the DNS level for every device behind the router, the same way a home AdGuard Home or Pi-hole instance would, just extended to wherever you’re travelling. It’s a genuinely pleasant bonus on top of the VPN gateway functionality, and it costs nothing extra to enable since the router is already sitting in the traffic path for every device. On a hotel network already loaded with intrusive ad injection on its own captive portal and landing pages, having DNS-level blocking active from the moment you connect is a noticeably better experience than tolerating it for the length of the stay.

The router also supports a separate guest Wi-Fi network, isolated from your main one — useful in the fairly common travel scenario of sharing a room with someone who needs internet access but shouldn’t be on the same network segment as your own devices and home-network tunnel. Guest clients get internet access through whatever uplink is active without being able to see or reach your other connected devices.

Troubleshooting Notes

Hotel captive portals don’t load. This is the most common complaint with any travel router, and it’s inherent to the architecture, not a Slate AX bug: a captive portal expects to see the actual client device’s browser session, and a router acting as a client-mode Wi-Fi bridge sometimes confuses the portal’s device-fingerprinting logic. GL.iNet’s UI includes a “Repeater” mode with a captive-portal-friendly client isolation setting for exactly this; if it still fails, connecting one device directly to the hotel Wi-Fi first to click through the portal, then switching that device over to the router once the MAC address is already authorised, works around it.

WireGuard handshakes but no traffic passes. Check AllowedIPs first — a common mistake is setting it to your home subnet on the client but forgetting the corresponding routing/NAT rule on the server side to actually forward that traffic back out. This is a large enough category of WireGuard mistakes that it’s worth reading through systematically rather than guessing at the fix.

Wi-Fi throughput is disappointing compared to the router’s advertised Wi-Fi 6 speeds. The uplink is almost always the bottleneck, not the Slate AX’s own wireless radios — hotel Wi-Fi bandwidth is frequently oversubscribed and rate-limited per client. Test raw uplink speed with the router’s own uplink client connected directly to a laptop before assuming the travel router itself is underperforming.

Hardening It Before You Travel

A travel router is itself a device sitting on an untrusted network, which makes a few basic hardening steps worth doing once, before the first trip, rather than mid-journey:

  • Change the default admin password immediately. GL.iNet devices ship with a setup wizard that forces this on first boot, but it’s worth double-checking on a unit that’s been sitting in a drawer since a previous firmware version, since old defaults can survive a factory reset to an earlier firmware state.
  • Keep firmware current. OpenWrt-based devices receive security patches at a reasonable cadence, and a travel router — by definition connecting to networks you don’t control — is exactly the device you don’t want running months-old firmware with known CVEs.
  • Disable remote (WAN-side) admin access if it’s enabled by default in your firmware version; the admin UI should only be reachable from the trusted LAN side, never from whatever untrusted network is plugged into WAN.
  • Consider a kill-switch setting if your firmware version supports one — some GL.iNet models can be configured to drop all traffic rather than fail open to the raw uplink if the WireGuard tunnel drops, which matters if the entire reason you’re using the tunnel is to avoid exposing traffic on networks you don’t trust.

None of this is unique to GL.iNet hardware — it’s the same baseline you’d apply to any router — but it’s easy to skip on a device you only touch a few times a year between trips, right up until the one trip where it actually matters and you find the firmware three versions behind.

Is It Worth Carrying

For solo travel with just a phone, arguably not — a phone’s own WireGuard client does the same job with less to pack and charge. For anyone travelling with multiple devices, a game console, or wanting reliable access back into a home network without configuring VPN clients on every device individually, it’s a genuinely useful piece of kit that’s paid for itself in reduced setup friction alone. The Slate AX specifically earns its price over cheaper travel routers by running real OpenWrt underneath the friendly UI — when you eventually want to do something the GL.iNet interface doesn’t expose, the underlying system is there, capable and ready for exactly that kind of work. That’s the detail that separates it from the disposable travel routers sold mainly on Wi-Fi range: a device you’ll still find useful a year later, once you’ve outgrown the setup wizard and started reaching for the CLI underneath it.

Smarc
Written by Smarc

Founder and editor of Aside House. A lifelong tinkerer who self-hosts far more than is sensible, hardens Linux boxes for fun, and prods the latest AI tools to see what they can really do. The how-to guides here are the notes Smarc wishes had existed the first time round.

Smarc is the editor of Aside House. The homelab, the hardware and the opinions are real; the guides are drafted with AI assistance. Infrastructure details are genericised on purpose.