Support obfuscation with AmneziaWG protocol extension

[RTechSn]

Hello.
There is more censorship each day around the world, and classic Wireguard gets easily detected by ISPs if there is such desire.
AmneziaWG is backwards-compatible fork of Wireguard which makes it harder to detect by Deep Packet Inspection systems.
https://github.com/amnezia-vpn/

[encodeous]

Hey,

I am aware of Amnezia, but I don't know if there is a clean way to integrate it into nylon.

Currently, if you wish to use Amnezia, or any other obfuscated tunnel, you can simply nylon's wireguard over the obfuscated tunnel of your choice.

Perhaps in the future, nylon can be protocol-agnostic, or at least support different protocols with minimal changes. We can also send packets over raw IP, thereby allowing any tunneling protocol. However, I'll have to look into the implications of that, and the user experience.

Currently however, this is out of scope, and nested tunnels would function (with slightly degraded performance)

[RTechSn]

Hi.
I'm aware that it's possible to run one tunnel through another, but the underlying tunnel would still need to have routing configured and this pretty much "defeats the purpose" of dynamic routing.
I hope this still may be considered in the future as there is much potential demand for it.

[encodeous]

I see, I will look into it!

[Brekit]

I agree, a more suitable repository for study is https://github.com/amnezia-vpn/amneziawg-go
In short, additional keys and extra payload bytes need to be added to the handshake to confuse the DPI.