Interface reference
A separate public deployment screenshot is not used here because it would be misleading or expose account details. The official project page below is the authoritative visual reference.
Open GL.iNet documentation →Why I use a travel router
A travel router lets laptops, phones and other devices connect to one private Wi-Fi network while the router handles the upstream hotel, mobile or guest network. This gives me one place to apply VPN routing, DNS settings and device separation instead of configuring every client independently.
How it connects to the lab
The router can establish a WireGuard or OpenVPN tunnel back to a controlled endpoint. I then permit only the internal services required for that trip or test. The exact router model is intentionally not published until I have confirmed it, but the project focuses on the network design rather than a product specification.
What I test
- Captive-portal and hotel-network behaviour
- WireGuard and OpenVPN failover
- DNS routing and leak checks
- Guest versus trusted client separation
- Access to selected home-lab services
- Recovery when the upstream network changes
What this demonstrates
This project combines wireless networking, VPN clients, route control, DNS policy and practical troubleshooting on networks I do not manage.
Verify DNS, kill-switch behaviour and fallback connectivity before relying on it away from home.
Update the travel router through its supported interface, create separate trusted and guest wireless networks, and configure a WireGuard or OpenVPN client profile using test credentials.