4 ms·

> just upgrade. I wish it was that easy.

josephcsible 3y ago
Doesn't basically all modern hardware and software already support IPv6 just fine? Aren't we just waiting for more ISPs to start rolling it out and sysadmins to remove their stupid "disable IPv6" policies?
- Dagger2 3y ago
  A lot of programmers are still writing v4-only code somehow. They'll write things like "socket(AF_INET, ...)" or "struct sockaddr_in address;" or "gethostbyname(...)" completely seriously and not seem to realize that any one of those things is an immediate red flag that your code is wrong and broken. OSs are fine, but the software and systems that we build on top of them are often v4-only.
  - feldrim 3y ago
    TBH, if it is not a requirement of the software, why would devs spend time on developing and testing IPv6? YAGNI kicks in way that point. If it's FOSS, it depends on the community. But if it is commercial, it's up to the specs.
    - Dagger2 3y ago
      I'm not even asking for that, I'm just asking for people to use the "new" APIs (they're older than some of the programmers making these mistakes), which are agnostic to address family. Use them even vaguely correctly and your code won't care about what address family the addresses are. Having bugs in untested functionality is understandable, but using long-deprecated known-broken APIs, or using the current ones in ways that are clearly and obviously wrong, isn't. (Also you should be using, and therefore testing, v6 at this point. But that's a separate discussion.)
- feldrim 3y ago
  It's not just the ISPs. It's the organizations themselves. All the on-premises infrastructure whether it's an SMB or international corporates. It's not just out of laziness. It's a huge change that requires an enormous amount of time, money and efforts with little added value to their business. No one in the world would pay more to a company who invested in IPv6 migration while the service is exactly the same. No customer will prefer one vendor over another just because they recently migrated to IPv6. The value proposition of IPv6 was about scarcity of resources. The problem is there and mitigation cost is higher than workarounds. And as people mentioned, an IPv4 address is as cheap as a a dinner for two.

Doesn't basically all modern hardware and software already support IPv6 just fine? Aren't we just waiting for more ISPs to start rolling it out and sysadmins to remove their stupid "disable IPv6" policies?

Dagger2 3y ago
A lot of programmers are still writing v4-only code somehow. They'll write things like "socket(AF_INET, ...)" or "struct sockaddr_in address;" or "gethostbyname(...)" completely seriously and not seem to realize that any one of those things is an immediate red flag that your code is wrong and broken. OSs are fine, but the software and systems that we build on top of them are often v4-only.
- feldrim 3y ago
  TBH, if it is not a requirement of the software, why would devs spend time on developing and testing IPv6? YAGNI kicks in way that point. If it's FOSS, it depends on the community. But if it is commercial, it's up to the specs.
  - Dagger2 3y ago
    I'm not even asking for that, I'm just asking for people to use the "new" APIs (they're older than some of the programmers making these mistakes), which are agnostic to address family. Use them even vaguely correctly and your code won't care about what address family the addresses are. Having bugs in untested functionality is understandable, but using long-deprecated known-broken APIs, or using the current ones in ways that are clearly and obviously wrong, isn't. (Also you should be using, and therefore testing, v6 at this point. But that's a separate discussion.)
feldrim 3y ago
It's not just the ISPs. It's the organizations themselves. All the on-premises infrastructure whether it's an SMB or international corporates. It's not just out of laziness. It's a huge change that requires an enormous amount of time, money and efforts with little added value to their business. No one in the world would pay more to a company who invested in IPv6 migration while the service is exactly the same. No customer will prefer one vendor over another just because they recently migrated to IPv6. The value proposition of IPv6 was about scarcity of resources. The problem is there and mitigation cost is higher than workarounds. And as people mentioned, an IPv4 address is as cheap as a a dinner for two.