AmneziaWG
AmneziaWG is WireGuard with exactly one property altered: recognisability. Plain WireGuard opens a connection with a packet of fixed shape — same length, same leading bytes, always in the same order. Even a simple analyser spots that sequence without decrypting anything. AmneziaWG adds parameters that break the constancy: several packets of random length and random content are sent before the handshake, and header service fields take arbitrary values instead of predefined ones. The cryptography is untouched — WireGuard encryption stays as it is, only the outward shape changes.
In short
AmneziaWG is for places where plain WireGuard is identified by packet shape. The cost is compatibility: the obfuscation parameters must match byte for byte on client and server, so a stock WireGuard client will not reach such a server, and the reverse holds too. Traffic overhead is marginally higher because of the added packets, though invisible against normal load.
Frequently asked
Is AmneziaWG less secure than WireGuard?
No. The cryptographic part is shared — same algorithms, same handshake in substance. The changes touch only how packets look: their length, the content of service fields, and the extra packets sent before the exchange begins. Encryption strength is not affected either way.
Will a stock WireGuard app work?
No, a client that supports these parameters is required. Plain WireGuard sees noise in the first packets and cannot make sense of it. For the same reason a configuration cannot be moved between them: the obfuscation values are a mandatory part of the setup, not decoration.