Setup guide
GL.iNet travel router and VPN setup guide
A research walkthrough of putting a WireGuard client on a GL.iNet travel router, written from official documentation. No product test log yet.
This is a documentation-based setup guide for GL.iNet travel routers that include a VPN client in the stock firmware. It is not a run log, and it is not a ranking of models.
What you need
- A GL.iNet router whose official firmware documents a WireGuard or OpenVPN client (not only a server). Popular travel models in the current lineup are sold under names such as Beryl and Slate; confirm the exact model and firmware on the unit’s label and in the admin interface, not from memory.
- A VPN provider that lets you download a WireGuard configuration (a
.conffile or a set of keys, endpoint, and allowed IPs) or an OpenVPN profile. Some providers also ship a GL.iNet-specific app or instructions. - A computer or phone to open the router’s admin page, usually over the router’s own Wi-Fi.
Official GL.iNet documentation describes the admin interface as reachable at the default LAN address printed on the device (commonly 192.168.8.1 on many models, but check the label). Change the default admin password on first use. Apply the firmware update the vendor recommends before you depend on the device on a trip.
Where the router sits
In the usual travel setup the router’s WAN side joins the hotel, airport, or RV park Wi-Fi (or a phone’s USB or Wi-Fi tether, if the model documents that). Your devices then join the router’s LAN Wi-Fi. The VPN client, when configured, starts on the router so that LAN clients do not each need their own VPN app.
That design has two consequences:
- You configure the tunnel once. Guests and devices with no official VPN app can still use it.
- If the router’s tunnel drops and there is no kill-switch or policy you have actually confirmed, LAN clients may start using the hotel network directly. Official firmware has settings around this; we will log how they behave only when a test exists. Until then, treat “what happens on disconnect” as a question to verify in the interface and in the vendor docs, not as a solved problem.
WireGuard client, in outline
GL.iNet’s official help pages describe a WireGuard client under the VPN or similar menu. The usual documented path is:
- Join the router’s Wi-Fi and sign in to the admin page.
- Open the WireGuard client screen and add a new configuration.
- Paste or upload the profile your VPN provider gave you. Some interfaces also let you type the private key, peer public key, endpoint, and allowed IPs by hand.
- Start the client and confirm the interface shows a handshake or a connected state.
- From a device on the LAN, visit a “what is my IP” page, or our leak-test tool, and compare the public address with the VPN off. This is a check you run for yourself. It is not a Privacy Proven product log.
If the handshake never starts, official troubleshooting usually points at: a typo in the endpoint or keys, a system clock that is badly wrong (WireGuard is sensitive to time), or a hotel network that is blocking the UDP port your profile uses. Some providers offer an alternate endpoint or port; that is a provider question, not something we can invent here.
OpenVPN client
Many GL.iNet models also document an OpenVPN client that accepts a .ovpn profile. OpenVPN is often slower to bring up and can be easier for a network to throttle, but it is sometimes the fallback when WireGuard’s UDP port is blocked. Use the profile and protocol (UDP or TCP) your provider documents.
Provider apps and third-party packages
Some VPN brands publish their own instructions or packages for GL.iNet firmware. Others expect you to use a generic WireGuard profile. We keep a separate research page on VPNs that run on a GL.iNet router. Until we have a log, that page also stays in the documentation lane.
Do not install unofficial firmware or random packages to “get a VPN working” unless you understand that you are leaving the vendor’s documented path. This guide does not cover unofficial firmware.
Before you travel
- Update firmware at home, on a network you trust, and keep a note of the version.
- Set a strong admin password and a unique LAN Wi-Fi password.
- Confirm you can start and stop the VPN client, and that you know how to fall back to the hotel Wi-Fi if the tunnel will not start.
- Download any provider profiles you will need while you still have a reliable connection. Do not put those files in a public folder.
Sources
- GL.iNet official product and help documentation for travel-router models and the WireGuard / OpenVPN client screens (confirm the page that matches your exact model and firmware).
- Your VPN provider’s official “router” or WireGuard setup documentation.
- Our travel-router protocol and leak-test tool.
What we did not test
No Privacy Proven product test has been run for this page. Figures and feature lists come from official documentation or cited public sources and should be read as such. We do not invent results, rankings from measurements we did not take, or quotes.