6 ms·
The need for IPv6 support is real! This site: https://whynoipv6.com/country/us https://whynoipv6.com/country/us -- provides a "wall of shame" summary of sites
by mhale 5y ago
The need for IPv6 support is real!
This site: https://whynoipv6.com/country/us https://whynoipv6.com/country/us -- provides a "wall of shame" summary of sites that do not yet fully support IPv6, in order of Alexa rank. It is definitely surprising, even shameful, that so many top sites make this list.
That Twitter and Amazon don't have full IPv6 support yet blows my mind.
It's also worth noting that IPv6 networks definitely DO exist in the real world.
My tiny startup provides software to run sports teams (mostly swim teams) and we've run into several cases where new wifi gets installed at a neighborhood pool, and the network is IPv6 only. So far, the pattern seems to be cases where AT&T is the ISP in the Houston area. To troubleshoot these issues via phone support, we ask if the customer can reach amazon.com or twitter.com. If not, it's a pretty good sign they are on a IPv6 only network.
Apple also requires IPv6 support for backend services for approval of iOS apps in the App Store (although, in practice, this requirement is not consistently checked).
See: https://developer.apple.com/support/ipv6/ https://developer.apple.com/support/ipv6/
Fortunately, adding IPv6 support to a site is relatively simple using Cloudflare.
See: https://www.cloudflare.com/ipv6/ https://www.cloudflare.com/ipv6/
[Edit] To clarify, I'm not affiliated with the Why No IPv6? site. I just found it to be a useful resource. The site credits https://crawler.ninja/ https://crawler.ninja/ as the source of its data.
[Edit 2] Added link to Apple's IPv6-only support policy.
- deleted 5y ago[deleted]
- yaomtc 5y ago> https://whynoipv6.com/country/us https://whynoipv6.com/country/us What a strange layout - the sidebar, which cannot be manually collapsed, covers up page content at moderate widths, until the page is quite wide. When the window gets narrow enough, some of what's in the sidebar can't be accessed at all.
- zamadatix 5y agoThat site says reddit.com is IPv6 but I'm not able to resolve any AAAA records for it.
- kd913 5y agoReddit ipv6 was enabled before Christmas but got disabled because of issues with the Android app and square’s okhttp lib I think. Namely that it didn’t support happy eyeballs.
- rekoil 5y agoI'm sorry but "happy eyeballs"?
- zinekeller 5y agoYeah, the name is straight from marketing (implying happy people seeing a fast website). It simply means that clients detect which is the better connection (whether IPv4 or IPv6) rather than naive IPv6-first or IPv4-first. RFC Standards about this: https://datatracker.ietf.org/doc/html/rfc6555 https://datatracker.ietf.org/doc/html/rfc6555 and https://datatracker.ietf.org/doc/html/rfc8305 https://datatracker.ietf.org/doc/html/rfc8305 Unfortunately OkHttp is naively priotising IPv6 regardless if the IPv6 connection is good or not.
- tadfisher 5y agoThe latest release now has a Happy Eyeballs implementation.
- mhale 5y agoI've also found this Geekflare tool to be useful to test the IPv6 compatibility of any domain/URL. https://gf.dev/ipv6-test https://gf.dev/ipv6-test Geekflare (https://gf.dev/ https://gf.dev/) has several other useful tools, worth checking out. This page is useful to test the IPv6 compatibility of your current network/browser: https://test-ipv6.com/ https://test-ipv6.com/
- toast0 5y ago> Apple also requires IPv6 support for backend services for approval of iOS apps in the App Store It really doesn't. It requires that the iOS apps work on IPv6 networks with DNS64/NAT64/whatever it's called. It meerly suggests that you might want to have server side IPv6, since your iOS apps need to support it anyway.
- cmeacham98 5y ago> DNS64/NAT64/whatever it's called I run an ipv6-only local network for fun, so I can tell you the name you're looking for is 464XLAT. In this style of setup, IPv4 packets are translated into IPv6, routed over the IPv6-only network, and translated back to IPv4.
- doublepg23 5y agoThat does sound like a fun project. Any reasoning behind it or benefits?
- tcoff91 5y agoNAT64 and DNS64 are not the same thing as 464XLAT. It's been a number of years since I had to work on this at a previous company, but my recollection is that Android relies 464XLAT to make sure that all android apps will work properly on ipv6-only mobile networks that use carrier grade NAT. Apple on the other hand demands that your app actually natively works with ipv6. I didn't have access to an ipv6 network when I was working on solving this issue in our networking libraries, so I used this https://www.jool.mx/en/ https://www.jool.mx/en/ to set up NAT64 and I used bind9 to do DNS64 in order to create an ipv6 network for testing ipv6 functionality.
- cmeacham98 5y ago> NAT64 and DNS64 are not the same thing as 464XLAT. Correct, that's my point. What my parent poster is describing is 464XLAT, not DNS64 and/or NAT64.
- 5y ago
- divbzero 5y agoI was surprised to see github.com in the list. I would generally expect them to be earlier adopters of new technology.
- baaym 5y agoYou got the wrong conclusion from your argument. IPv6 is older than some of HN's audience.
- rekoil 5y agoIndeed, IPv6 has existed for 26 years yet here we are in 2022 still having issues using it. Sites/apps are still deployed IPv4 only, consumer equipment is not ready for IPv6, and very few ISPs are even providing customers with native IPv6 addresses. Mine is, luckily, so I've been able to set my network up, but I'm struggling to see how the world is gonna make this transition in the near future tbh. My guess is we'll be stuck with carrier grade NAT for a long time.
- 41b696ef1113 5y ago>...consumer equipment is not ready for IPv6 Is that true? I had assumed that all network equipment could do IPv6, but the functionality was not exposed by default.
- toast0 5y agoJust because the equipment can do it, doesn't mean it's ready. I was trying to get my home network setup for IPv6, but the DSL modem would reboot if a fragmented packet was sent, so that's not really ready. The replacement modem didn't reboot, but had severe induced latency, so I went in a different direction and still don't have IPv6.
- sgent 5y agoMy ISP is dual stack (cox), as is AT&T fiber -- but that is only for residential. Almost all consumer gear is IPv6 compatible, much of Cisco Meraki's still isn't or is limited. It is not all consumer.
- rob_c 5y agoFrankly, given the peering issues and lack of support from major peers it's not going to happen soon... And the mess that is v6 when things go wrong... I'm going to say it again. Private v6 and a powerful v6<->v4 NAT if you insist on using v6 only on devices, we're nowhere near the point where people can't afford a single v4 address and if the phone companies can do it at huge scale so can others... Edit: "Adding support via cloudflare" ??? doesn't that mitigate pretty much 90% of all of the advantages of v6 in the first place? that's just implementing it for tech-point scoring...
- mhale 5y agoIt's not about tech point scoring, it's about quickly solving a problem. Specifically how can my customers on IPv6-only networks reach my service hosted on Heroku (which does not support IPv6)? Cloudflare is a practical and relatively easy solution to that problem.
- rob_c 5y agoand again... WHO IS ISSUING IPv6 ONLY WITHOUT A 6<->4 NAT AT THE EDGE???