Research guide

VPNs that run on a GL.iNet router

By J.K. Ward (pen name) · Updated 2026-11-17· Method v1.0 · Test pending

Which VPN apps and WireGuard profiles vendors say work on GL.iNet firmware. Research guide; test pending.

A GL.iNet travel router can run a VPN client in firmware so every device on the LAN uses one tunnel. This page is a research pass over what vendors themselves document. It is not a compatibility log, and it does not rank providers. For the mechanical steps, see the setup guide.

Two ways a VPN gets onto the router

  1. A generic WireGuard or OpenVPN profile. You download a configuration from the VPN provider and add it in the GL.iNet client screens. This path is documented by GL.iNet and by many providers. It is the most portable.
  2. A vendor-specific app or plugin that the provider or GL.iNet publishes for that firmware. When it exists, follow the matching official page. Do not assume an app from a different platform (Windows, Android, iOS) can be installed on the router.

If a marketing page says “works on routers” without saying how, treat that as incomplete.

What official materials say, in brief

NordVPN. NordVPN publishes router and WireGuard (often under a NordLynx name in their apps) documentation, and it has published materials aimed at manual configuration. Whether a dedicated GL.iNet flow exists, and for which firmware, is a question for Nord’s current help pages. We have not logged a handshake on a Beryl, Slate, or other model.

Surfshark. Surfshark publishes WireGuard and router-setup documentation. Same rule: use the official router page, not a guess, and do not treat a screenshot on a third-party blog as our result.

Proton VPN. Proton documents WireGuard configuration downloads for paying plans (availability of a router-friendly profile is a plan and documentation question). A generic WireGuard client on GL.iNet is the expected path when a profile is available.

Mullvad. Mullvad documents WireGuard configuration generation in the account panel and has public router notes. Mullvad has no affiliate program; the link is unpaid and stays that way. That does not make the product automatically “the one that works” on a given firmware. It does mean we include it on merit.

Other brands, including ones on the ownership map, may also document generic profiles. When we add them, they will get the same kind of entry: a claim from official docs, plus a future log if we run one.

What “it runs” has to mean later

Our VPN protocol and travel-router protocol will treat a successful run as:

  • A named firmware version and a named VPN app or profile version.
  • A documented protocol (WireGuard or OpenVPN).
  • A handshake that stays up long enough to check the public IP from a LAN client, using something like the leak-test tool.
  • A note on what happens to LAN traffic if the tunnel is stopped.

Until that file exists, this page is only a map of documentation.

Practical cautions

  • Hotel networks sometimes block UDP ports used by WireGuard. A documented OpenVPN-over-TCP profile is the usual fallback, if the provider offers one.
  • Split tunneling and “apps excluded from the VPN” on a phone app do not apply the same way when the tunnel lives on the router. The whole LAN is typically in or out.
  • Putting a provider’s account keys on a travel router means the router is now part of your account security. Use a strong admin password and keep firmware current.

Sources

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.