Hacker News Reader

Comment by sandstrom | Hacker News Reader

Until AWS, Azure and GC support native IPv6 there won't be many apps that can use this.

These apps can use it anyway.

It is for carriers to be able to deploy IPv6 only networks. If your service is hosted on IPv4-only host, from the perspective of the device, you will be behind NAT64.

If your service is on IPv6-reachable host, you will get the bonus in the form of a direct connection.

Good point, thanks for adding this!

Still, I think it's sad that none of the three large cloud providers have IPv6 support.

Digital Ocean, OVH and a few other has it though. Still, most are with one of the big three.

It's coming, I noticed that my Linodes and Rackspace boxes started sending mail to Google and 365 via straight IP6 recently. I didn't have to do anything, I only noticed because my IP6 PTR's were wrong. It's the future!

And until there are apps that can use IPv6, there won't be a need. I think it's fine that Apple attempts to push IPv6, because no one else seems to be doing anything, well no big companies at least.

Almost 12% of internet users are accessing Google over IPv6, and that figure is growing exponentially[0]. The users are already there, and our apps need to start using IPv6 more.

[0] https://www.google.com/intl/en/ipv6/statistics.html

AWS ELBs are reachable over IPv6 http://docs.aws.amazon.com/ElasticLoadBalancing/latest/Devel...

Only if you're still using classic.

Not when using VPC, which almost any modern AWS deployment is.

True, though ClassicLink is an option. Launch ELB in EC2 classic and add instances in VPC over classlink.

New accounts (as of 2013-12-04) don't even support classic.

http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-vpc...

Only in EC2-Classic, which is only supported by legacy AWS accounts that signed up before December 2013. Anyone who signed up for AWS in the past 2 years can not use IPv6.

The HE tunnel broker can be used there.

OVH’s cloud supports native IPv6.

Reply on news.ycombinator.com