--- title: AmneziaWG description: Configure embedded or optional Linux kernel AmneziaWG inbounds in 3x-ui. icon: Lock --- **AmneziaWG** is a WireGuard fork that adds traffic obfuscation (junk packets, randomized padding, and rewritten protocol magic values) so the tunnel doesn't look like WireGuard to deep-packet inspection. It's a popular choice where plain WireGuard is blocked but a WireGuard-shaped tunnel with a different fingerprint gets through. AmneziaWG runs **embedded in the panel process** — `amneziawg-go` over a userspace (gVisor) network stack, not a kernel module. There is no DKMS build, no Secure Boot conflict, and no host network/kernel access requirement, so it works the same way inside a container as on bare metal. Each peer's decapsulated traffic relays into its own loopback Xray SOCKS5 inbound, so a peer's routing, sniffing, and per-client stats all come from Xray's own machinery — the same as any other protocol's inbound, not a separate code path. ## Key settings ### Server / interface | Field | What it is | | ------------------------ | ------------------------------------------------------------------------ | | **Subnet** | The tunnel's IPv4 subnet (e.g. `10.8.1.0/24`); each client gets an address from it. | | **MTU** | Interface MTU. Leave at the default unless you have a reason to change it. | | **DNS (primary/secondary)** | Seeded into downloadable client configs; the server's own interface doesn't need one. | | **External interface** | The host NIC a peer's IPv6 address gets aliased onto when IPv6 is enabled (see below). Leave blank to auto-detect. | ### Obfuscation (AmneziaWG 3.1) The same values must match on both ends of the tunnel, so the server stores them once and every client config inherits them. The panel generates a randomized set for you (with a **regenerate** button) — a static, reused value defeats the point, since DPI can fingerprint it over time. | Field | What it is | | ------------ | ---------------------------------------------------------------------------- | | **Jc** | Number of junk packets sent before the handshake. | | **Jmin/Jmax** | Size range (bytes) for those junk packets. `Jmin` must not exceed `Jmax`. | | **S1/S2** | Padding added to the handshake init/response packets, `0`-`1552` / `0`-`1608`: the packets are `148 + S1` and `92 + S2` bytes and must fit the 1700-byte receive buffer amneziawg-go uses on iOS. The panel also rejects `S1 + 56 = S2`, which would give both packets the same size on the wire (amneziawg-go itself accepts it). An AmneziaWG outbound takes the remote server's values as they are, up to `65535`. | | **S3** | Cookie-reply padding, `0`-`1636`: the reply is `64 + S3` bytes and must fit the 1700-byte receive buffer amneziawg-go uses on iOS. An outbound, as with S1/S2, takes the remote server's value up to `65535`. | | **S4** | Transport (data) packet padding, `0`-`32`. | | **H1-H4** | Header values that replace WireGuard's message-type field. Each is a single integer or a `low-high` range, and the four must not overlap — amneziawg-go and the kernel module refuse the whole device otherwise. `1`-`4` are WireGuard's own types and the engine default for a blank field: valid, but without a HeaderProtectionKey the type field then reads like plain WireGuard. | | **I1-I5** | Optional signature packets — random bytes prepended before the handshake, e.g. ``. Generated sets fill `I1` only, matching Amnezia's own generator. | | **HeaderProtectionKey** | A base64 32-byte key for the 3.0 header-protection mechanism. Must match on every client config; blank disables it. | | **ContentPaddingAddition** | A single integer or `low-high` byte range of extra padding on content packets. Kept `<= 64` by the generator so a 1420-MTU tunnel doesn't fragment. | | **RekeyAfterTime / RekeyTimeout / RejectAfterTime / KeepaliveTimeout / MaxHandshakeAttempts** | Handshake-timing randomization: each is a `low-high` range (seconds; attempts for the last one) the peer samples from, so session timing stops being a WireGuard fingerprint. Every `RekeyAfterTime` value must stay below every `RejectAfterTime` value. Blank keeps the WireGuard default. | | **RandomTrailers** | Appends a random number of bytes to the end of every packet. | | **DisableCookies** | Never send cookie replies — removes a DPI-visible WireGuard message type, at the cost of WireGuard's handshake-flood mitigation. | If you enter obfuscation values by hand instead of using the generated defaults, keep `H1`-`H4` **non-overlapping** and above `4`, and double-check `S1 + 56 != S2` — a bad value here keeps the embedded interface from coming up at all. The 3.1 parameters need a **3.1-capable client**. Clients must run a 3.1-capable Amnezia app; blanking the 3.1 fields renders a config older clients still understand. There is no host-side version requirement — the panel ships its own pinned `amneziawg-go`, not whatever happens to be installed on the system. ## Set it up in the panel ### Add an inbound Add a new inbound, choose protocol **AmneziaWG**, and set the port and tunnel subnet. ### Leave obfuscation on defaults (or regenerate) The panel fills in a randomized, kernel-valid obfuscation set automatically. Use **Regenerate** if you want a fresh one; there's no need to hand-edit these unless you have a specific reason to. ### Add a client Each client gets its own keypair and tunnel address. Download the client's `.conf` or copy its share link (`vpn://…`, importable by the official AmneziaWG/AmneziaVPN apps) from the client list. ### Optional: enable IPv6 Turning on IPv6 allocates an IPv6 address alongside each client's IPv4 one from the configured IPv6 subnet. The panel aliases that address onto the external interface's host NIC so outbound connections carry the peer's own distinct public IPv6 identity — no NAT66 needed. ### Optional: forward ports to a client Set a client's forwarded ports (e.g. `80, 443, 8000-8100`) to open a real listener on the host that relays that traffic straight to the client's tunnel address — useful for a client that needs to expose a service through the server. In the **embedded** backend, each peer relays into its own loopback SOCKS5 inbound, tagged with the AmneziaWG inbound's tag. Its traffic therefore uses Xray routing and appears on the [Routing](/docs/operations/outbounds-routing) page, like other Xray inbounds. ## Optional Linux kernel backend The embedded backend remains the default. On a supported Linux host, an administrator can opt an individual inbound into the kernel backend with **Kernel mode**. The panel then creates an `xui-awg` interface on the AmneziaWG kernel module, configures it with `awg setconf`, and masquerades peer traffic out of the host NIC with an nftables table of its own (`xui_awg`). Peer traffic bypasses Xray. Nothing runs through a shell: every step is a direct `ip`, `awg` or `nft` command, and the interface's config lives in a panel-private directory (`/etc/x-ui/amneziawg` on a standard install), never next to your own `awg-quick` configs. Kernel mode requires a Linux host running the panel as root, with the `amneziawg` module installed and `awg`, `ip` and `nft` available. The readiness panel reports missing host requirements and provides the install command. On a standard install, run `sudo /usr/local/x-ui/x-ui install-awg-kernel`. The bundled command builds a pinned, commit-verified release of the module and tools on Debian and Ubuntu; kernel headers and, when Secure Boot is enabled, module signing must be available. Review the script and host changes before running it. The panel enables IPv4 forwarding and, when `iptables` is installed, adds two `FORWARD` accept rules per interface (commented `3x-ui:xui-awg`), so a host whose `FORWARD` policy is `DROP` — as Docker and ufw set it — still forwards the tunnel. A firewall that drops forwarded traffic in its own nftables table, such as firewalld, still needs a rule from you. Kernel mode is not supported in Docker. Embedded mode continues to work in containers. The kernel backend does not support Xray routing or sniffing, per-client IPv6, client port forwarding, or a pinned listen address; the panel rejects saves that request those features. On a multi-node setup the master checks that the target node supports kernel mode before pushing such an inbound, and the node checks its own host when it applies it. Stopping the panel records the interfaces' final traffic and then tears them down, exactly as the embedded backend stops: a stopped panel enforces no quota or expiry, so nothing keeps forwarding. A panel-only restart (`SIGHUP`) leaves them running. If the panel process dies instead, the next start adopts the surviving interfaces; traffic between the crash and the first counter read after it is not charged. Interfaces and configs the panel cannot prove are its own — a same-named link with a different key, or an unmarked, non-regular or symlinked config file — are never changed or removed. ## Keepalive ranges AmneziaWG clients accept `keepAlive` as a number or an ordered range from 0 to 65535, such as `15-25`. Omitted values keep the existing setting; explicit `0` disables keepalive. Native `.conf` files preserve ranges, while Clash/Mihomo scalar-only output uses the lower bound (`0-25` therefore disables keepalive). Plain WireGuard clients support only a scalar value. Upgrade sub-nodes before sending them range values because older nodes parse keepalive as an integer. Parser support is present in the native tools and the panel embedded engine: [the native `awg-tools` v3.1.20260812 config parser](https://github.com/amnezia-vpn/amneziawg-tools/blob/v3.1.20260812/src/config.c#L596-L599) sends `PersistentKeepalive` to its [ordered-range parser](https://github.com/amnezia-vpn/amneziawg-tools/blob/v3.1.20260812/src/type.c#L40-L59), and this panel pins [amneziawg-go v3.1.20260828](https://github.com/amnezia-vpn/amneziawg-go/tree/v3.1.20260828) in `go.mod`; its [UAPI parser](https://github.com/amnezia-vpn/amneziawg-go/blob/v3.1.20260828/device/uapi.go#L663-L674) reads the interval as a `UintRange`. This confirms parser support for these code paths, not interoperability with every third-party client. The panel enforces the documented 0-65535 limit on new values; the native parser's syntax support is not a substitute for that validation. ![AmneziaWG client editor with an ordered keepalive range](/images/amneziawg-keepalive-range.png) ## What the configuration looks like A client's downloadable `.conf` (also what the `vpn://` share link encodes, base64url'd) looks like this: ```ini title="client .conf" [Interface] PrivateKey = Address = 10.8.1.2/32 DNS = 8.8.8.8, 8.8.4.4 Jc = 4 Jmin = 65 Jmax = 220 S1 = 87 S2 = 44 S3 = 21 S4 = 9 H1 = 463065432 H2 = 912345678 H3 = 1345678901 H4 = 1987654321 I1 = HeaderProtectionKey = 8Iu83eHDA3fMKKSGaEsVW9Ycd2lYYzc0MYlk1jJTvE4= ContentPaddingAddition = 17-49 RekeyAfterTime = 111-139 RekeyTimeout = 4-7 RejectAfterTime = 187-251 KeepaliveTimeout = 9-14 MaxHandshakeAttempts = 19-36 RandomTrailers = on DisableCookies = on # my-client [Peer] PublicKey = AllowedIPs = 0.0.0.0/0, ::/0 Endpoint = your-server:443 PersistentKeepalive = 25 ``` ## Multi-node (sub-nodes) An AmneziaWG inbound can be created on, or cloned to, a sub-node. The node's own panel runs the interface, so the node must run panel **v3.7.0** or newer; the master refuses an older node, or one that has not reported its version yet. A client's `forwardedPorts` are checked against the ports in use on that node. ## Not yet covered - **Telegram bot** — AmneziaWG inbounds haven't been exercised through the bot yet. Treat it as unverified until someone reports back.