This applies to all Windscribe Servers / Clients, I'm just opening the issue here since IPv6 only is being rolled out especially quickly on mobile networks. Issue can be moved to another bug tracker, if applicable.
First of all, I greatly appreciate support for IPv6 egress on supported locations, this makes Windscribe better than a lot of VPNs out there (who are still stuck in the last century).
With IPv4 becoming less and less common on end user devices, the next step would be IPv6 ingress. Especially on mobile networks, providers are increasing implementing IPv6 only setups. To connect to Windscribe on such a network, the path currently looks like this:
- Phone tries to reach IPv4 Windscribe server (no public IPv4 routes exist)
- IPv4 packets get sent to 464XLAT daemon on device, get translated to IPv6
- IPv6 packets go to the network providers NAT64 service, get translated back to IPv4 and NAT'ed
- IPv4 packets leave NAT64 server and go to Windscribes servers
With IPv6, the transmission is greatly simplified, possibly decreasing latency, throughput and increasing battery life on end user devices:
- IPv6 packets leave phone and get routed as-is
- IPv6 packets arrive at Windscribe servers, no translations necessary.
First of all, I greatly appreciate support for IPv6 egress on supported locations, this makes Windscribe better than a lot of VPNs out there (who are still stuck in the last century).
With IPv4 becoming less and less common on end user devices, the next step would be IPv6 ingress. Especially on mobile networks, providers are increasing implementing IPv6 only setups. To connect to Windscribe on such a network, the path currently looks like this:
With IPv6, the transmission is greatly simplified, possibly decreasing latency, throughput and increasing battery life on end user devices: