Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

IPv6 support for VPN endpoints #133

Open
ffrediani opened this issue Jun 5, 2024 · 0 comments
Open

IPv6 support for VPN endpoints #133

ffrediani opened this issue Jun 5, 2024 · 0 comments

Comments

@ffrediani
Copy link

Your service is very interesting and the information is very well clear and written on your FAQ. Well done for such level of detail and transparency !

Would you consider to add IPv6 support to all of your VPN endpoints (e.g: xx1.tunnelsats.com) ?
The providers you use (DigitalOcean, Vultr, Hetzner) all have native IPv6 support to their VPS offerings and it should be simply a question of making Wireguard listen on IPv6 socket and add the AAAA FQDN for each endpoint.

This should have not impact on clients with IPv4-only connection that will continue to resolve the A FQDN and enhance connectivity robustness by avoiding local CPE NAT a the home router and possibly at the ISP CGNAT. Even with the Wireguard connecting to a IPv6 endpoint it is still possible to pass IPv4 traffic inside de tunnel normally which fulfil the main propose of the service.

A lot of big Broadband Providers worldwide nowadays have full IPv6 support and therefore many people running Lightning nodes already have IPv6 connectivity to their nodes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant