Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

> This is exactly how NAT64 works, and still doesn't solve the problem of IPv4 clients trying to connect to servers with only IPv6 addresses.

You also have to deploy new DNS code to handle a new record type to handle longer "IPv4+" addresses.

You also have to deploy new OS and library code with new socket, etc, APIs because all in_addr_t definitions and data structures are 32-bit-only.



AFAIK, IPv6 adoption is held back by hardware. My ISP doesn't provide IPv6, but its DNS provides IPv6 addresses just fine.


> AFAIK, IPv6 adoption is held back by hardware.

What hardware, especially ASICs, do not support wire speed IPv6 and have not for a decade or two?

T-Mobile was gave a presentation on going IPv6-only in 2017:

> For the past 10 years T-Mobile has worked towards creating an IPv6 environment and we are now getting very close to our goal. Stephan presents learning on how to successfully enable IPv6-only using DNS64 with or without 464XLAT. He will do a live demo of the different IP interfaces on an Android handset. Finally, he will discuss and give some best practices on how to handle DNS, applications, and websites that are having issues with DNS64.

* https://www.youtube.com/watch?v=nNMNglk_CvE

So they started in 2007.

Whatever ISP you're with has probably had at least 2-3 tech refreshes in which IPv6 hardware has been available.

For the CPE, Free in France had IPv6 in 2007:

* https://en.wikipedia.org/wiki/IPv6_rapid_deployment


Maybe my ISP bought T-Mobile's ip4 hardware. Since DNS supports ip6, it suggests software is fine, the only thing left is hardware.


Any hardware router introduced in the last two decades has IPv6 support; in my somewhat outdated experience the barrier to implementation is implementing dual-stack logic in software built for single stack.


ISPs in Belgium implemented IPv6 a decade ago (some even two decades). ISPs elsewhere could have done it too by now (nobody is still using 10+yo hardware, I hope...).




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: