Skip to content
Litora

AmneziaWG config for a GL.iNet router (Mudi 7, Slate 7, Beryl AX)

A GL.iNet router needs no app: its firmware has a WireGuard client built in, and from firmware 4.9 that client also understands the extra lines an AmneziaWG file carries. You download one file from Litora and upload it in the router's admin panel. Every device behind the router then goes through the tunnel, and the router counts as one device on your plan.

Get the file

  1. Open your setup link, or sign in at litoravpn.com/get.
  2. Choose Router (GL.iNet, OpenWrt) as the platform.
  3. Choose AmneziaWG as the connection type. The country list narrows to the locations where AmneziaWG is live.
  4. Pick a country and download the file. It is called litora-<country>-amneziawg.conf — for the United States, litora-us-amneziawg.conf.

Only the file matters. The Setup guide button beside it opens GL.iNet's own instructions, the same steps as below, and the set-up page has them for every platform.

Put it on the router

From GL.iNet's tutorial, firmware 4.9 or later:

  1. Open the router's admin panel and go to VPN → WireGuard Client.
  2. Add a new group and give it any name.
  3. Upload the .conf file. Once it passes the check, click Apply.
  4. Click the three dots next to the configuration and choose Start.
  5. Wait about a minute. A green status means the tunnel is up, and the VPN dashboard shows the location you chose.

If the panel shows an older firmware, upgrade first under System → Upgrade: 4.7 imports plain WireGuard, and AmneziaWG needs 4.9.

What is in the file

Open it in a text editor and you see a normal WireGuard configuration plus nine extra lines under [Interface]: Jc, Jmin, Jmax, S1, S2, H1, H2, H3, H4. They tell the router how many junk packets to send before the handshake, how long they are, and how to disguise the four packet types. The values come from the gateway you picked, not from you: both ends have to use the same numbers, so do not edit them.

This is the AmneziaWG 1.0 parameter set — in GL.iNet's words a "1.0 config": no S3 or S4, and each H value is a single number rather than a range. The 2.0 protocol keeps these lines and adds optional ones on top, so a 1.0 file is a valid file for a 2.0 client with the extras left out. Litora's gateways do not emit the 2.0 extras today. If a guide asks you for an "AmneziaWG 2.0 config", this is the file to give it.

Three things that bite

Questions

Does a 1.0 config work on an AmneziaWG 2.0 router?

The protocol says yes: 2.0 reads the 1.0 lines and treats the newer ones as absent. We have not watched a Litora file import on a GL.iNet ourselves, so if yours is refused, message the bot with the firmware version and the exact message.

Which GL.iNet models?

Any on firmware 4.9 or later. GL.iNet's tutorial uses the Brume 3 and the Beryl AX; the Mudi 7 and Slate 7 travel routers are on the same firmware line. The number matters, not the model name: look under System → Upgrade.

Does the same file work on plain OpenWrt?

Only with the AmneziaWG kernel module and tools installed; the amneziawg-openwrt project on GitHub builds them for OpenWrt releases. That is their project, not ours, and we have not tested it. The file itself is the same.

AmneziaWG or WireGuard, which is faster?

WireGuard. AmneziaWG spends a little on the junk packets and the disguised headers, mostly at the handshake. Use the standard tunnel where it connects reliably, and keep an AmneziaWG file ready for networks that block WireGuard. Which connection type should I choose? has the longer answer.

Does a router cost extra device slots?

No. A router is one device on your plan, however many phones and laptops sit behind it, and a router with both a WireGuard and an AmneziaWG configuration is still one device.

Everything above about the router's panel comes from GL.iNet's own tutorial and FAQ, the pages the Setup guide button opens; nobody at Litora has walked it through on a GL.iNet router yet. If you do, tell the bot what you saw. It is the fastest way to make this page better.

Updated 2026-10-17.

Still stuck? Message the bot