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
33 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.