3 ms·

I run IPv6 only servers on Scaleway because IPv4 addresses are €1/month extra and my node costs €2/month. That's a 50% cost increase. The biggest stumbling blo

by sspiff 9y ago

I run IPv6 only servers on Scaleway because IPv4 addresses are €1/month extra and my node costs €2/month. That's a 50% cost increase. The biggest stumbling blocks for IPv6 are the fact that many prominent cloud services don't fully support IPv6. The biggest problems for me are Amazon S3 and Github. I end up having to pass traffic for those services through an SSH tunnel to a nearby node with both IPv4 and IPv6. On an unrelated note, I'm happy to see that apparently my home country Belgium has one of the highest adoption levels worldwide, if not the highest.

mgbmtl 9y ago
Same here! Google-Cloud still doesn't really support IPv6 on public-facing nodes (?), and Github ... However, this encouraged me to self-host with Gitlab and to use other hosting providers (ex: OVH). Sometimes I will NAT the outgoing IPv4 connections on VMs (if I control the host, and the host has one IPv4 address). A lot of internal services, such as logs, build systems, etc, don't need public IPv4 addresses, but giving them 10.x.x.x addresses quickly becomes a burden when dealing with multiple networks.
rsync 9y ago
"The biggest stumbling blocks for IPv6 are the fact that many prominent cloud services don't fully support IPv6." rsync.net has been ipv6 accessible (the storage, not the website) for 7-8 years ...
ianburrell 9y ago
NAT64/DNS64 is supposed to work well for allowing IPv6-only networks outgoing access to IPv4. Servers are less likely to use software like Skype that only works with IPv4. It would be nice if providers that support IPv6-only networking would provide NAT64 gateways and DNS64 DNS servers.
btgeekboy 9y ago
S3 is available over IPv6, but you need to use a different endpoint. https://aws.amazon.com/blogs/aws/now-available-ipv6-support-for-amazon-s3/ https://aws.amazon.com/blogs/aws/now-available-ipv6-support-...
sigjuice 9y ago
The biggest stumbling blocks for IPv6 are the fact that many prominent cloud services don't fully support IPv6. Or have outright broken IPv6, e.g. Digital Ocean's /124

by sspiff 9y ago

mgbmtl 9y ago

Same here! Google-Cloud still doesn't really support IPv6 on public-facing nodes (?), and Github ... However, this encouraged me to self-host with Gitlab and to use other hosting providers (ex: OVH). Sometimes I will NAT the outgoing IPv4 connections on VMs (if I control the host, and the host has one IPv4 address). A lot of internal services, such as logs, build systems, etc, don't need public IPv4 addresses, but giving them 10.x.x.x addresses quickly becomes a burden when dealing with multiple networks.

rsync 9y ago

"The biggest stumbling blocks for IPv6 are the fact that many prominent cloud services don't fully support IPv6." rsync.net has been ipv6 accessible (the storage, not the website) for 7-8 years ...

ianburrell 9y ago

NAT64/DNS64 is supposed to work well for allowing IPv6-only networks outgoing access to IPv4. Servers are less likely to use software like Skype that only works with IPv4. It would be nice if providers that support IPv6-only networking would provide NAT64 gateways and DNS64 DNS servers.

btgeekboy 9y ago

S3 is available over IPv6, but you need to use a different endpoint. https://aws.amazon.com/blogs/aws/now-available-ipv6-support-for-amazon-s3/ https://aws.amazon.com/blogs/aws/now-available-ipv6-support-...

sigjuice 9y ago

The biggest stumbling blocks for IPv6 are the fact that many prominent cloud services don't fully support IPv6. Or have outright broken IPv6, e.g. Digital Ocean's /124