6 ms·

This finally puts real pressure on software and services to work on IPv6 only. I wouldn't be surprised if within 1-2 release cycles lots of distributions sudden

This finally puts real pressure on software and services to work on IPv6 only. I wouldn't be surprised if within 1-2 release cycles lots of distributions suddenly update just fine with just IPv6, package mangers can download packages over IPv6, lots of APIs gain solid and well-tested IPv6 support, etc.

kccqzy 3y ago
Apple has been demanding apps support IPv6 only for years now. They reject your app if it fails under NAT64. The end user side is mostly a solved problem.
- ketralnis 3y ago
  For iOS maybe. Most of those applications are also using Apple's networking libraries and are effectively required to be on Apple's infinite software update treadmill to continue to be listed, keeping them young and hip in perpetuity. This is the upside to that treadmill, things are up to date or just stop working. But I don't think that's representative. "Or just stop working" isn't a valid alternative to the rest of the world. Outside of mobile ecosystems and maybe web development most things aren't on these 6 to 12 month update cycles. It would be absolutely unreasonable to tell a hospital that every piece of hardware and software and MRI machine in their building has to be upgraded every 2 years or it's positively geriatric and do you even `pacman -Syyu` bro? Theres a whole world of things that haven't been, and may never be, transitioned. Useful things like utility control computers and even peoples' 10 year old, still perfectly functional and supported desktops. Heck, my "end user" newly-installed fibre ISP doesn't support IPv6! And their previous DSL installation to the same address did! So much for "solved problem" :(
  - kccqzy 3y ago
    A hospital's MRI machine doesn't need an internet connection. IPv4 only intranets are fine and we are never going to get rid of them. But anything that connects to the internet needs to be updated regularly, if only for security and vulnerability reasons. If you have a 10-year-old functional and supported desktop, it most likely supports being IPv6 only just fine. The typical 10-year-old desktop came from the factory with Windows 8 and could be upgraded to Windows 10 (since it's supported). It even gets relatively new features such as IPv6 RDNSS allowing DHCP-less deployments.
    - p_l 3y ago
      Windows networking became v6-first in Vista, over a decade ago.
    - bandrami 3y ago
      > A hospital's MRI machine doesn't need an internet connection That's one of the more disheartening searches on censys, unfortunately
candiddevmike 3y ago
Businesses and organizations are holding IPv6 back, not consumers. No one I talk to is prioritizing IPv6 migrations or spending money to upgrade gear that will support it. Maybe some net new stuff might get it, but for most businesses IPv4 is and will be the default, simply because they can't be bothered to do something different.
- 0cf8612b2e1e 3y ago
  Serious question, is there any enterprise gear made today which does not support IPv6? I have assumed that the natural hardware upgrade cycles made it so 99% of all active equipment could support the technology, even if it was not configured to do so.
  - candiddevmike 3y ago
    That door alarm thing that has a Windows XP workstation VM the facilities team touches once a month probably doesn't support IPv6. Repeat that scenario across multiple BUs and multiple locations and no leader wants to commit to doing that kind of due diligence. What's wrong with our current IP?
    - GoblinSlayer 3y ago
      Windows XP supports IPv6.
  - jandrese 3y ago
    Man in the middle certificate re-signing deep packet inspection firewalls are notorious for not supporting IPv6. Most everything else has switched, but many network admins fear IPv6 and don't want to have to learn something new.
  - squeaky-clean 3y ago
    "Made today"? Probably not. "Still in operation today"? Definitely. My company makes what is essentially an enterprise IoT device. I'd guesstimate 10% of networks with our hardware in them have no ipv6 support at all. And these are businesses that are on the more tech savvy side (I would assume, since they're ordering our stuff).
NoZebra120vClip 3y ago
TIL that my Chromebook connects to the Internet with a 6to4 address rather than the real /64 that my ISP assigns.
- deleted 3y ago
  [deleted]
- p1mrx 3y ago
  This seems unlikely, as 6to4 was deprecated in 2015: https://datatracker.ietf.org/doc/html/rfc7526 https://datatracker.ietf.org/doc/html/rfc7526
  - NoZebra120vClip 3y ago
    I couldn't believe it either, but using Chome on ChromeOS 114, updated yesterday, all the public sites report that I am connecting from 2002::/16
    - p1mrx 3y ago
      Interesting. It's only possible to terminate 2002::/16 using a public IPv4 address, so if you're behind a NAT router, then the router itself must be running 6to4.
      - NoZebra120vClip 3y ago
        Aha! Thanks for the hint: I recently had to reconfigure my router from factory settings. The IPv6 configuration, sure enough, was kicked into 6to4 mode. I set it to "Auto Config" and now I've got end-to-end IPv6 connectivity with, look Ma, no NAT! Thank you, p1mrx!
Macha 3y ago
As a business... $40/year/server is nothing. As a individual/hobbyist, it's a much bigger disincentive. For students and the like, it might actually be prohibitive. The problem is it's really the first group that needs to drive the remaining IPv6 adoption by replacing their middleware boxes etc. and they're the group who are unlikely to care at this price.
wiredfool 3y ago
For a while, google was blocking linode's ipv6 block in Frankfurt. NBD, except that elastic hosts their client deb repos on google infra, so apt-get update was failing from it. The solution was to single stack the server, or manually install the clients having downloaded from elsewhere.
sph 3y ago
Yearly reminder that HN is still IPv4-only

kccqzy 3y ago

Apple has been demanding apps support IPv6 only for years now. They reject your app if it fails under NAT64. The end user side is mostly a solved problem.

ketralnis 3y ago
For iOS maybe. Most of those applications are also using Apple's networking libraries and are effectively required to be on Apple's infinite software update treadmill to continue to be listed, keeping them young and hip in perpetuity. This is the upside to that treadmill, things are up to date or just stop working. But I don't think that's representative. "Or just stop working" isn't a valid alternative to the rest of the world. Outside of mobile ecosystems and maybe web development most things aren't on these 6 to 12 month update cycles. It would be absolutely unreasonable to tell a hospital that every piece of hardware and software and MRI machine in their building has to be upgraded every 2 years or it's positively geriatric and do you even `pacman -Syyu` bro? Theres a whole world of things that haven't been, and may never be, transitioned. Useful things like utility control computers and even peoples' 10 year old, still perfectly functional and supported desktops. Heck, my "end user" newly-installed fibre ISP doesn't support IPv6! And their previous DSL installation to the same address did! So much for "solved problem" :(
- kccqzy 3y ago
  A hospital's MRI machine doesn't need an internet connection. IPv4 only intranets are fine and we are never going to get rid of them. But anything that connects to the internet needs to be updated regularly, if only for security and vulnerability reasons. If you have a 10-year-old functional and supported desktop, it most likely supports being IPv6 only just fine. The typical 10-year-old desktop came from the factory with Windows 8 and could be upgraded to Windows 10 (since it's supported). It even gets relatively new features such as IPv6 RDNSS allowing DHCP-less deployments.
  - p_l 3y ago
    Windows networking became v6-first in Vista, over a decade ago.
  - bandrami 3y ago
    > A hospital's MRI machine doesn't need an internet connection That's one of the more disheartening searches on censys, unfortunately

candiddevmike 3y ago

Businesses and organizations are holding IPv6 back, not consumers. No one I talk to is prioritizing IPv6 migrations or spending money to upgrade gear that will support it. Maybe some net new stuff might get it, but for most businesses IPv4 is and will be the default, simply because they can't be bothered to do something different.

0cf8612b2e1e 3y ago
Serious question, is there any enterprise gear made today which does not support IPv6? I have assumed that the natural hardware upgrade cycles made it so 99% of all active equipment could support the technology, even if it was not configured to do so.
- candiddevmike 3y ago
  That door alarm thing that has a Windows XP workstation VM the facilities team touches once a month probably doesn't support IPv6. Repeat that scenario across multiple BUs and multiple locations and no leader wants to commit to doing that kind of due diligence. What's wrong with our current IP?
  - GoblinSlayer 3y ago
    Windows XP supports IPv6.
- jandrese 3y ago
  Man in the middle certificate re-signing deep packet inspection firewalls are notorious for not supporting IPv6. Most everything else has switched, but many network admins fear IPv6 and don't want to have to learn something new.
- squeaky-clean 3y ago
  "Made today"? Probably not. "Still in operation today"? Definitely. My company makes what is essentially an enterprise IoT device. I'd guesstimate 10% of networks with our hardware in them have no ipv6 support at all. And these are businesses that are on the more tech savvy side (I would assume, since they're ordering our stuff).

NoZebra120vClip 3y ago

TIL that my Chromebook connects to the Internet with a 6to4 address rather than the real /64 that my ISP assigns.

deleted 3y ago
[deleted]
p1mrx 3y ago
This seems unlikely, as 6to4 was deprecated in 2015: https://datatracker.ietf.org/doc/html/rfc7526 https://datatracker.ietf.org/doc/html/rfc7526
- NoZebra120vClip 3y ago
  I couldn't believe it either, but using Chome on ChromeOS 114, updated yesterday, all the public sites report that I am connecting from 2002::/16
  - p1mrx 3y ago
    Interesting. It's only possible to terminate 2002::/16 using a public IPv4 address, so if you're behind a NAT router, then the router itself must be running 6to4.
    - NoZebra120vClip 3y ago
      Aha! Thanks for the hint: I recently had to reconfigure my router from factory settings. The IPv6 configuration, sure enough, was kicked into 6to4 mode. I set it to "Auto Config" and now I've got end-to-end IPv6 connectivity with, look Ma, no NAT! Thank you, p1mrx!

Macha 3y ago

As a business... $40/year/server is nothing. As a individual/hobbyist, it's a much bigger disincentive. For students and the like, it might actually be prohibitive. The problem is it's really the first group that needs to drive the remaining IPv6 adoption by replacing their middleware boxes etc. and they're the group who are unlikely to care at this price.

wiredfool 3y ago

For a while, google was blocking linode's ipv6 block in Frankfurt. NBD, except that elastic hosts their client deb repos on google infra, so apt-get update was failing from it. The solution was to single stack the server, or manually install the clients having downloaded from elsewhere.

sph 3y ago

Yearly reminder that HN is still IPv4-only