How to Configure Your Travel Router as a WireGuard Client

Your home server is running. Now the travel half: turning your pocket router into a WireGuard client that funnels everything back home. This travel router WireGuard client setup guide covers the import, the connection, the verification, and the kill switch, on GL.iNet firmware (the same ideas apply to any OpenWrt-based travel router).

Importing your home server config

You need the client config file your home server generated for this router (one key pair per device; don't reuse the laptop's).

On GL.iNet firmware:

1. Connect to the router's WiFi or plug in via Ethernet, and open the admin panel (default 192.168.8.1).
2. Go to VPN → WireGuard Client.
3. Click to add a profile, then upload the .conf file your home server generated. (Some firmware versions also accept pasting the config text or scanning a QR code with your phone to transfer it.)
4. Name it clearly: "Home WireGuard" beats "wg0" when you're troubleshooting at midnight.

Getting the file onto the router: the admin panel's file upload is the simplest path. If your home server generated a QR code, display it on your laptop screen and use the phone-app bridge some firmware offers, or just copy the text. Avoid exotic transfer methods; the file is small and the panel upload is reliable.

Double-check one line in the imported config before connecting: the Endpoint should be your DDNS hostname (not a raw home IP that may have changed), and AllowedIPs should be 0.0.0.0/0 for full-tunnel. PersistentKeepalive = 25 should be present so hotel NAT doesn't drop the idle tunnel.

Connecting and verifying

1. In the WireGuard Client panel, select your "Home" profile and hit Connect. Status should flip to connected within seconds.
2. Verify from the router: the panel usually shows the tunnel status and sometimes the exit IP. Better: connect your laptop to the router's WiFi and check an IP-lookup site. Home IP and home city means the tunnel is real.
3. Verify DNS: run a DNS leak test from a device behind the router. You should see your home ISP's resolvers (or your configured DNS), never the hotel's.
4. Test roaming: unplug the router's uplink (or switch it from hotel WiFi to phone tether) and confirm the tunnel re-establishes on its own. This is the moment that separates a good setup from a fragile one.

If it won't connect: endpoint hostname correct? Port right? Home server actually running? Port forwarding intact? The WireGuard troubleshooting checklist applies here exactly as on any client.

The kill switch (do not skip this)

On GL.iNet firmware it's VPN → VPN Dashboard → "Block Non-VPN Traffic" (wording varies slightly by version): one toggle. What it does: if the tunnel drops for any reason, the router blocks all internet access rather than letting devices fall back to the raw hotel connection.

Then test it like you mean it: with everything connected, stop the WireGuard server at home (or block the port temporarily). Your devices should lose internet entirely. Browse something; it should fail. Restore the server; connectivity should return through the tunnel. If devices kept browsing during the outage, the kill switch isn't working and your location leaked. Fix it before the trip, not during.

Why this matters so much: a dropped tunnel without a kill switch doesn't announce itself. You keep working, and every service you touch logs your real location. The kill switch converts a silent leak into a loud, obvious outage, which is exactly what you want.

Quick questions

Need help setting this up?

Travel-router client config, kill-switch verification, fallback profiles: we do all of it as part of our done-for-you home IP VPN setup, tested before you pack. https://homeipvpn.com.