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 infrastructu...
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.
You don't have permission to do this.
You're going a bit too fast! Take a break and try again in a moment.
Something went wrong! Please reload the page and try again.
Your session has expired. Please reload the page and try again.
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.