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?
What version of Amnezia are we on?
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.
35 Comments
Adding support for 2.0 won't solve this issue. You are not able to use the locations, not because of the protocol, but the fact that IP's/gateways are blocked. We don't rotate IP's on VPN infrastructure that often which is (WireGuard/OpenVPN/AmneziaWG).
That's why Stealth Proxy has different infrastructure and it was designed to bypass the blocks with quick changes to domains/IP's/re-deployments.
Indeed. This will bolster obsfucation of traffic type once flows are established, but initiation etc … wont help.
There are several servers I cannot use without the I1 junk parameter. When connected, the incoming traffic gets stuck at a random byte value. That means I can connect to the server, but the WireGuard protocol is being filtered. After I add the I1 junk parameter, I can use the server as usual. This indicates that IPs/gateways are not blocked; instead, the protocol is being filtered. Of course, some servers' IPs/gateways are blocked entirely, but in instances like this awg 2.0 will help.
Yeah, lately in Russia I've been feeling more and more throttling and blocking on both ShadowSocks and Amnezia. Unfortunately, Hysteria doesn't work for me at all.
It would be really great if your service could deploy the new version of Amnezia, so I could get the best features from the open-source version.
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.