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?
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?
Something Went Wrong
24 Comments
Hi,
Official AmneziaWG apps are not yet updated and are still running 1.0 version. Once they are updated we will look into updating configuration files and testing it out.
Is it safe to update amnezia-go, amnezia-tools to the latest tagged release?
We haven't tested new versions and if they are compatible with our current configs. Do at your own risk.
how's this progressing?
Amnezia team still haven't updated AmneziaWG clients to support 2.0.
I wonder if there is a way using their own app AmnesiaVPN with the support built in.
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.
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?
Is it out for Mac yet?
What is the awg version currently reached by the protocol? 2.0?
Well, seeing as amneziawg client in appstore hasn't been updated yet, I guess it is not. But maybe you can try Amnezia app.
What parameters have you added and tested, so we can run some additional tests and see if it actually works properly or not.
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.
didn't work for me in the amnesia app.
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.