GL.iNet VPN setup: OpenVPN and WireGuard with VPN Tracker

GL.iNet VPN setup is a practical way to access your home, office, or travel-router network from your Mac, iPhone, or iPad when you are away. This guide shows the recommended flow for using a GL.iNet router as your VPN gateway and creating the matching OpenVPN or WireGuard connection in VPN Tracker 365.

GL.iNet routers are popular with remote workers, consultants, and small teams because many models include built-in OpenVPN and WireGuard support. The exact screens can vary by model and firmware version, so use the placeholders in this guide for your own server address, remote network, and exported configuration file.

• Before You Start
• Choose OpenVPN or WireGuard
• Set Up WireGuard on Your GL.iNet Router
• Set Up OpenVPN on Your GL.iNet Router
• Create the Connection in VPN Tracker
• Test Your GL.iNet VPN Connection
• Common Issues

Before You Start

To connect to your GL.iNet router from outside the local network, your router needs to be reachable from the internet. In most setups, that means one of these conditions must be true:

• Your GL.iNet router is the main router for the internet connection and has a public IP address.
• Your GL.iNet router is behind another router, and port forwarding is configured on the upstream router.
• Your internet connection uses a dynamic public IP address, and you have set up Dynamic DNS on the GL.iNet router.

If your ISP uses CGNAT or does not provide a public IP address, a direct inbound VPN server on the GL.iNet router may not be reachable from the internet. In that case, check with your ISP or consider an alternative remote-access design.

You will also need admin access to the GL.iNet web Admin Panel, the current router firmware, and VPN Tracker 365 installed on the Mac, iPhone, or iPad you want to use for remote access.

Choose OpenVPN or WireGuard

GL.iNet routers support both OpenVPN and WireGuard. VPN Tracker 365 can import both OpenVPN configuration files and WireGuard configuration files or QR codes, so the best choice depends on the gateway setup and your team’s requirements.

WireGuard is usually the first option to try for a new GL.iNet VPN setup. It is designed to be lean and fast, and GL.iNet’s current router interface includes a dedicated WireGuard Server section. It is a strong fit when you are setting up a modern remote-access connection and can export a WireGuard profile for each user or device.

OpenVPN is a good choice when your organization already standardizes on OpenVPN, when you need compatibility with an existing configuration process, or when you have an exported .ovpn profile from the GL.iNet router. It is also familiar to many admins, which can make troubleshooting easier.

Set Up WireGuard on Your GL.iNet Router

Use this section when your GL.iNet router will act as the WireGuard server and VPN Tracker will connect as the client.

1. Open a browser and sign in to the GL.iNet web Admin Panel. The default local address is often 192.168.8.1, but use the address configured for your router.
2. Go to VPN > WireGuard Server.
3. If this is the first WireGuard setup on the router, generate or initialize the server configuration.
4. Review the tunnel address. If it conflicts with an upstream router or another VPN network, change it to a non-conflicting subnet, for example 10.1.0.1/24.
5. Create a new profile for the device that will use VPN Tracker. Use a clear name such as MacBook Pro - Alex or iPhone - Sales.
6. Export the WireGuard configuration as a .conf file or display the QR code.
7. If your router uses Dynamic DNS, make sure the exported endpoint uses the DDNS hostname instead of a temporary public IP address.
8. If remote devices should access the GL.iNet LAN, enable the router option that allows remote access to the LAN subnet.

Each WireGuard profile should normally be used by one client device. If you need to connect multiple devices, create separate profiles so each device has its own keys and address.

Set Up OpenVPN on Your GL.iNet Router

Use this section when your GL.iNet router will act as the OpenVPN server and VPN Tracker will import the exported OpenVPN profile.

1. Open the GL.iNet web Admin Panel and sign in with your router admin password.
2. Go to VPN > OpenVPN Server.
3. Generate the OpenVPN server configuration if it has not already been created.
4. Keep the default settings unless your network requires a specific subnet, protocol, or port.
5. If you configured Dynamic DNS, enable the option to use the DDNS domain when exporting the client configuration.
6. Export or download the OpenVPN client configuration file. This is typically an .ovpn file.
7. Start the OpenVPN server on the GL.iNet router.
8. If remote devices should reach devices on the GL.iNet LAN, enable the setting for remote LAN access. On newer firmware this may appear as an option in the OpenVPN Server page; on older firmware it may be located in the VPN Dashboard.

Store the exported .ovpn file securely. It contains connection details that should only be shared with the person or device that needs VPN access.

Create the Connection in VPN Tracker

Once the GL.iNet side is ready, create the matching connection in VPN Tracker 365.

1. Open the GL.iNet connection creator: Create GL.iNet VPN connection.
2. Choose your GL.iNet router or the matching protocol option.
3. For WireGuard, import the .conf file or scan the WireGuard QR code exported by the GL.iNet router.
4. For OpenVPN, import the .ovpn file exported by the GL.iNet router.
5. Name the connection clearly, for example GL.iNet Home WireGuard or GL.iNet Office OpenVPN.
6. Review the remote network settings. If the imported profile does not include the LAN route you need, add the remote network manually, for example 192.168.8.0/24 or your actual GL.iNet LAN subnet.
7. Save the connection securely in VPN Tracker.

If you manage connections for a team, create and test the connection first before sharing it with users through TeamCloud. This gives you a chance to verify routing, DNS, and remote network access before rollout.

Test Your GL.iNet VPN Connection

Test from outside the GL.iNet router’s local network. For example, use a mobile hotspot or another internet connection, then connect in VPN Tracker.

1. Connect the VPN in VPN Tracker.
2. Confirm the connection status changes to connected.
3. Open an internal resource, such as the GL.iNet router address, a file server, a web app, or a remote desktop host.
4. Check whether DNS names resolve as expected. If DNS does not work, test with the internal IP address to separate DNS issues from routing issues.
5. If your setup should route all traffic through the VPN, confirm your public IP address changes while connected.

For a split-tunnel setup, only the configured remote networks should use the VPN. Other internet traffic should continue to use the local connection.

Common Issues

The VPN does not connect from outside the network

Check whether the GL.iNet router has a public IP address. If it is behind another router, confirm that port forwarding is configured on the upstream router for the WireGuard or OpenVPN server port. If you use Dynamic DNS, confirm that the hostname points to the current public IP address.

The connection succeeds, but local devices are not reachable

Confirm that remote LAN access is enabled on the GL.iNet VPN server settings. Then check the remote network in VPN Tracker. The route must match your GL.iNet LAN subnet, for example 192.168.8.0/24 if your router uses the default GL.iNet network.

WireGuard connects, but only one device works

Create a separate WireGuard profile for each device. Reusing the same WireGuard profile on multiple devices can lead to confusing connection behavior because each profile is expected to identify a specific peer.

OpenVPN imports, but authentication fails

Export a fresh OpenVPN client configuration from the GL.iNet router and make sure it is the complete .ovpn file. If your GL.iNet OpenVPN server requires additional credentials, enter the correct username and password provided by the router or your VPN admin.