You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: