Support
kelix kelix Aug 2, 2025
Posted Sat, Aug 2, 2025 9:23 AM
Edited Sat, Aug 2, 2025 9:54 AM

What version of Amnezia are we on?

Hi all, what version of AmneziaWG are we running on? 1.5?

if so I assume we are benefitting from the multi-level obfuscation at the transport layer?

👍️ 3 Like Loading...
35 ⁨35⁩ ⁨comments⁩
Answered by 0xVirtualCake 0xVirtualCake

We have reviewed version 2.0, and we will not be adding support for it for the foreseeable future. We understand that many users here were expecting that we will add support for it, so before you feel disappointed, let us explain why.

  • Supporting AmneziaWG 2.0 means that we need to drop support for native WireGuard which is powered by a kernel module which is a lot faster than the Go implementation of AmneziaWG 2.0 to support it on all existing VPN servers.

  • Alternatively we could deploy brand new and separate infrastructure only for AmneziaWG 2.0 and separate it from WireGuard, but that is costly (not only in terms of money, but mainly developing and keeping it safe and up to date) and we already have Stealth Proxies for this.

  • AmneziaWG 2.0 is very close to Hysteria 2.0 that we already support.

  • Supporting only AmneziaWG 1.0 is not that bad and DPI vendors still need to keep the block rules for it. More block rules = more computing power. At some point some DPI vendors might even drop block rules for it, because everyone will focus on 2.0 version. Of course more modern DPI system might keep all the possible protocols in the block list, but it does not apply to every country/city.

  • Adding support for AmneziaWG 2.0 won't solve the issue with blocked VPN infrastructure that we are using for WireGuard/OpenVPN and I have explained this in my previous message here.

We will keep checking the status and development of AmneziaWG, but for now we will not support AmneziaWG 2.0 or any further versions of it. We think it's fair game based on how many protocols we already provide today.

View Answer

⁨35⁩ ⁨Comments⁩

In reply to kelix kelix

The official Amnezia VPN client experience is bad. It uses dynamic code loading for no reason and crashed on me a couple of times even with the generic malloc. It's better to wait for them to update the AmneziaWG client.

In reply to 2 2D4F2F

There were wg servers I wasn't able to connect to, but after updating amneziawg client which now supports 1.5 version and adding new parameters to the config file I was able to successfully connect to those servers and so far so good. So, would you maybe think about adding these options to the configurator?

What parameters have you added and tested, so we can run some additional tests and see if it actually works properly or not.

In reply to 0xVirtualCake 0xVirtualCake

I added the Special Junk l1 parameter, and it was enough to successfully resolve the connection issues I had with some wg servers. There are other parameters I didn't try because the issue was resolved, but you can find the howto on amneziawg 1.5 on the amnezia website.

In reply to kelix kelix

If you used the special junk l1 from the howto, it didn't work for me either and I found a working one elsewhere. You can find your own l1 parameter using Wireshark, as mentioned in the howto. Additionally, there are converters for proton vpn wg configs to make them compatible with awg 1.5. You can search for those online. Then you can just copy l1 parameter from there.