Alternatives for WireGuard Setup due to ISP IPv6 and Potential Block Issues

Questions / Help
1

Hey everyone,

I’ve been working on setting up a WireGuard VPN to use Fly.io’s internal network, but I’ve run into some issues. My ISP doesn’t support IPv6, and I suspect they may also be blocking WireGuard connections entirely (Uzbekistan). As a result, I can’t establish the tunnel needed to access .internal Fly.io addresses.

I’ve tried various workarounds, but the lack of IPv6 support seems to be a major hurdle, especially when trying to ping IPv6 addresses like _api.internal. When attempting to establish the WireGuard tunnel, I receive errors such as:

yaml

[#] ip -6 route add fdaa:a:5815::/48 dev <interface>
RTNETLINK answers: No such device

artgits@artlocal:~/Documents/code/spiral_software/hello-fly$ ping6 google.com
ping6: connect: Network is unreachable

Given these constraints, I’m considering an alternative approach: setting up a VPS in the EU/UK and using it as my development environment. I’d SSH into the VPS and perform all the necessary tasks there, using it as a bridge to access Fly.io’s internal services.

Would this be a viable solution? Has anyone else faced similar issues with IPv6 or WireGuard being blocked by their ISP? If so, how did you resolve it?

Any advice or insights would be greatly appreciated!

Thanks in advance,

2

It seems that the approach with VPS servers works. I’m going to inform the community about my progress here. Hopefully, it will be helpful for someone facing a similar issue.

3

Hi everyone,
Yesterday I set up my workflow for collaboration with Fly’s services. It’s not exactly what I wanted, but I will try again over the weekend. There’s a lot of network administration involved, where I don’t much experience, but it’s interesting.
I’ve moved all my stuff to the VPS and will work there until I find a more comfortable way to work.

4

The Wireguard traffic itself should appear to your ISP as IPv4. It is within the Fly Wireguard tunnel that it is IPv6. That said - the host/client that you’re trying to establish the Wireguard tunnel from must support IPv6.

This may be your problem. However, given you have access to a VPS - try setting up a test/temporary Wireguard server on that. If the Wireguard server on the VPS appears to be ok but you’re unable to connect to it, and see no inbound Wireguard traffic to the VPS - then Wireguard may be blocked.

It is also possible that the problem is on your originating host/client (lack of IPv6 support/etc).

5

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.