Skip to content
Get Real IP Docs

GL.iNet Setup

GL.iNet routers have WireGuard built in with a straightforward UI. This guide uses the GL.iNet admin panel to set up your Get Real IP tunnel.

Step 1 — Download your config

Section titled “Step 1 — Download your config”

From the Get Real IP dashboard, open your tunnel and click Download Config. Save the .conf file — you’ll upload it directly to your router.

Step 2 — Open the WireGuard VPN page

Section titled “Step 2 — Open the WireGuard VPN page”
  1. Log in to your GL.iNet admin panel (typically at 192.168.8.1)
  2. Go to VPN → WireGuard Client
  3. Click Add a New VPN Configuration

Step 3 — Import the config file

Section titled “Step 3 — Import the config file”

In the configuration dialog:

  1. Select Import from File
  2. Upload the .conf file you downloaded from the dashboard
  3. Give it a name like Get Real IP
  4. Click Import

GL.iNet will parse the config and fill in all the fields automatically.

Step 4 — Connect

Section titled “Step 4 — Connect”

Back on the WireGuard Client page:

  1. Find the Get Real IP profile
  2. Toggle it on

The status indicator should turn green and show Connected within a few seconds.

Step 5 — Verify

Section titled “Step 5 — Verify”

From any device on your GL.iNet network, check your public IP:

  1. Open a browser and go to https://api.ipify.org
  2. You should see your Get Real IP static address

Or from the GL.iNet admin panel, go to VPN → WireGuard Client and check that the connection shows a Handshake time.

Routing options

Section titled “Routing options”

By default, the imported config routes all traffic through the tunnel (AllowedIPs = 0.0.0.0/0). This means both inbound and outbound traffic use your static IP.

GL.iNet firmware does not support policy-based routing (incoming-only mode). If you need split routing — where only inbound traffic uses the tunnel and outbound goes through your ISP — you’ll need a router that supports it (pfSense, OPNsense, or a Linux box). See the Policy-Based Routing guide for details.

Auto-connect on startup

Section titled “Auto-connect on startup”

GL.iNet routers reconnect VPN tunnels automatically after reboot by default. To confirm:

  1. Go to VPN → WireGuard Client
  2. Make sure Auto-Connect is enabled for your profile

Troubleshooting

Section titled “Troubleshooting”

Status stays “Connecting” or shows no handshake:

  • Check that your GL.iNet has an active internet connection (WAN status)
  • Verify the endpoint resolves: from Network → DNS or try a ping test if your firmware supports it
  • Confirm UDP 51834 is not blocked by your upstream network or ISP

Connected but public IP doesn’t change:

  • Check the AllowedIPs value in your config — it should be 0.0.0.0/0 to route all traffic
  • Try disconnecting and reconnecting the tunnel
  • Check for conflicting VPN profiles that might be active at the same time

Services on my LAN aren’t reachable from the internet: The WireGuard tunnel terminates at the GL.iNet router. Traffic arriving at your static IP will reach the router — you’ll need to set up port forwarding to reach devices behind it.

Go to Network → Firewall → Port Forwards (location may vary by firmware version) and add rules for each service you want to expose.