> ## Documentation Index
> Fetch the complete documentation index at: https://tunnelfleet.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# WireGuard on GL.iNet

> Import a TunnelFleet WireGuard config on a GL.iNet router.

GL.iNet routers can run WireGuard as a client so every device on the LAN shares the tunnel.

<Steps>
  <Step title="Download the WireGuard config">
    In TunnelFleet, download the `.conf` for the VPN user you want the router to use.
  </Step>

  <Step title="Open the GL.iNet admin UI">
    Connect to the router and open its web admin (often `192.168.8.1`). Sign in.
  </Step>

  <Step title="Add a WireGuard client">
    Go to **VPN** → **WireGuard Client** (wording varies slightly by firmware) → **Add New** / **Upload Config**.
  </Step>

  <Step title="Import the TunnelFleet profile">
    Upload the `.conf` file or paste its contents. Save.
  </Step>

  <Step title="Connect">
    Start the WireGuard client connection and confirm status is connected.
  </Step>
</Steps>

## Verify

From a device on the GL.iNet LAN, open [ifconfig.me](https://ifconfig.me) and confirm the public IP is your TunnelFleet VPS.

## Tips

* Dedicate a TunnelFleet VPN user to the router so you can revoke it without affecting phones and laptops
* If you use guest Wi‑Fi, decide whether guest traffic should also traverse the tunnel
* Update GL.iNet firmware before troubleshooting obscure import errors

## Troubleshooting

| Issue                          | Fix                                                                                      |
| ------------------------------ | ---------------------------------------------------------------------------------------- |
| Import rejected                | Re-download the profile; ensure the full `[Interface]` and `[Peer]` sections are present |
| Connected, LAN has no internet | Check the router's kill switch / policy based routing options                            |
| Handshake failure              | Confirm UDP 51820 is allowed from the router's WAN IP to the VPS                         |