I know that IPv6 was created in 1998 as a future-proofing, to make sure that there will be enough IP addresses in the works for large networks. IPv4 uses 32 bits and is represented with denary (0-9) while IPv6 uses 128 bits, so there are far more possible addresses, and it is represented using hexadecimal (0-9 then A-F).

What I’m wondering is why IPv4 is still so common, even though the number of devices connected to the internet have skyrocketed with more computers, laptops, smartphones, game consoles, embedded systems, etc. all connected! If it was thought that there would be too few available addresses in 1998, surely that has to be a bigger problem in the modern day?

Additionally, why didn’t IPv6 replace v4, even after nearly three decades of existing? Is it a technological limitation, cost, or something else?

And online I see many sysadmins online (!) complaining about IPv6 being more difficult to work with. Is this because the addresses are harder to remember, are adaptations of the protocol by manufacturers all different (similar to USB-C), or is there some other problem with IPv6? Or is this a case of a loud angry minority, especially in chat forums where people tend to have more polarised views?

Many devices do support IPv6, but it’s not universal like IPv4, despite the standard existing since 1998 and having many advantages. Why is this?

  • slazer2au@lemmy.worldEnglish
    75·
    8 hours ago

    Because people are slow to fix something unless it is an impending problem.

    Take the Y2K bug. Did you know the original person who made the bug was telling people in the 70s that is needs fixing? And it wasn’t actually fixed till the second half of the 90s.

    2038 is going to be a fun year with all the 32bit clocks overflowing to 1970

    • NeatNit@discuss.tchncs.de
      43·
      7 hours ago

      2038 is going to be a fun year with all the 32bit clocks overflowing to 1970

      Actually 13 December 1901, since it overflows to negative, not zero.

      Other than that, good answer, full marks

    • iknewitwhenisawit@fedinsfw.appEnglish
      11·
      6 hours ago

      I learned to program in the 1980s. I promise you that for most programs written then the coder was like, “Two digit year, of course. Why waste so many bytes with a four digit year? Nobody will be using this software in 15 years!” And probably 95% of the time they were right…

    • palordrolap@fedia.io
      19·
      8 hours ago

      2038 problems have already started happening in niche cases. I expect things will pick up in pace in a couple of years because 10 years is that sort of period of time that people like to post-date future events by.

      That might be enough to scare a few of the hold-outs. Then 2033 will be the next scare and reminder, because five years, etc.

      Then probably every year after that until the deadline hits. By that point, the remaining few will be using faketime or something like it to eke out a few more years from whatever ancient hardware they’re still running that is too expensive to replace.

      Fun fact, and possible hint: Setting the date back 28 years on such hardware could work in a pinch, since the calendar from 2010 to 2037 is identical to that from 2038 to 2065. All weekdays and leap days fall on the same dates. (Easter and other moveable feasts don’t, however.)