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?

  • thenextguy@lemmy.world
    0·
    11 days ago

    FYI, there’s a new proposal for IPv8 to address the issues with ipv6.

    The main benefit seems to be that it is a superset of IPv4, so all existing addresses remain valid.

    It also has some questionable ‘enhancements’ like requiring DNS records in order to allow routing.

  • Robert7301201@slrpnk.net
    0·
    11 days ago

    The first and biggest reason is network effects. If nobody else is using IPv6, then there’s little benefit to switching. Corporations and governments are always resource constrained and there’s not really a business case for switching just because it might be necessary someday. Being that corporations and governments are the ones providing the vast majority of services on the internet, that means there’s not as much reason for switching for end users as well.

    Part of the reason that switching didn’t end up being necessary was that NAT did a really good job of solving the address problem. NAT let you have an internal network behind a single IP address which vastly reduced the amount of public IPs necessary. Even most people in tech probably wouldn’t realize that the concept of public vs internal network didn’t exist back in the day. Everything connected to the Internet had a publically reachable IP. When even that wasn’t enough, they just did it again and had CGNAT, carrier grade NAT. Now you could have multiple households and businesses behind a single IP.

    The final reason is that IPv6 is just different from IPv4. Things like router advertisements and SLAAC require you to learn new things and rethink how you do things. What doesn’t help matters is that until you get everyone switched over to IPv6, you still have to support IPv4 in some way. Dual stack, where you run both IPv4 and IPv6 in parallel, is the most compatible way, but it’s also the most complicated to administrate. There are ways for an IPv6-only network to communicate with IPv4 clients, such as NAT64, but they each have their own caveats. These differences can result in small annoyances to administrators that add up, such as like you mentioned that IPv6 addresses are just not as memorable as IPv4. The natural fix for this is DNS. But like I said, that requires you to rethink your network. DNS goes from being a nice to have to being essential even for small networks.

    Despite all these issues, IPv6 adoption is still marching along. France, India, and Germany have some of the highest rates of IPv6 capable devices, at 83.97%, 78.81%, and 74.30%. (IPv6 Adoption) Globally, we’re sitting around just under 50%. (Google IPv6 Tracker) Some sectors also have higher adoption rates. Mobile carriers are mostly IPv6-only these days. A lot of residential routers also ship with IPv6 enabled.

    • kent_eh@lemmy.caEnglish
      0·
      11 days ago

      Mobile carriers are mostly IPv6-only these days.

      I was going to point that out as well.

      Your phone is probably on an IP6 network right now.

      And it will be NATted to an IP4 address when it leaves the carrier’s network to interact with the public internet.

      • grue@lemmy.world
        0·
        11 days ago

        Does that mean you can use IP6 to connect despite CGNAT, or do the ISPs that use it tend to firewall off the IP6 connections anyway?

        • Robert7301201@slrpnk.net
          0·
          11 days ago

          If your ISP supports IPv6, then yes, you can use IPv6 to get a publicly reachable address when you would otherwise be unable to due to being behind a CGNAT. If your ISP does not support IPv6, you are out of luck. There are methods to translate between IPv4 and IPv6, but they require a public IPv4 address.

          My friend switched to Starlink recently and was disappointed to find out he can’t host Minecraft servers and such due to CGNAT. Luckily, Starlink does support IPv6, so he was able to host his servers that way. The caveat is that we have to be IPv6 capable to join his server.

    • joel_feila@lemmy.world
      0·
      10 days ago

      I remember my first class on NAT. The teacher said “this was not meant to be a security feature but that one use for it”.

  • Pipea@lemmy.world
    0·
    10 days ago

    Inertia. IPv4 still works, every service on the internet still available over it. You can just be lazy and things will be ok.

    Complexity. IPv6 is complex in the areas where v4 sucks. Ran out of address space? Here’s a lot more address space. Multiple routers offering multiple routes? Just grab them all, have as many addresses as you want. No method to find peers on the same subnet? Here’s like three methods to find peers on the subnet. All this is stuff you gotta learn!

    Workarounds. Initially, ISPs thought that people turned their PC off at night and they’d get the IP address back. Then, they were leaving multiple devices on all day! So they came up with a hack that pretends everyone is behind one IP address, now all your devices are just one IP. But that IP still stays up and occupied all the time, they’re not getting it back, so they put all their customers under another (CG)NAT. It’s just NAT all the way down whenever they run out, and this way they never run out.

    • filcuk@lemmy.zip
      0·
      10 days ago

      I still don’t understand IPv4 fully after all these years, I’m not sure I’ll ever bother with v6 for my hone network.

      • bss03@infosec.pubEnglish
        0·
        10 days ago

        I’m just too used to setting up DHCP and including the single gateway address in that.

        Setting up a routing advertisement daemon and just letting devices use their (MAC-derived) automatic IPv6 address is significantly different, so I haven’t learned it yet.

        It also doesn’t help that I’ve never been under an ISP that provided IPv6 connectivity, so I’d only be able to connect to IPv4 external endpoints anyway, unless I separate got a 6-in-4 tunnel service of smth.

    • floquant@lemmy.dbzer0.com
      0·
      10 days ago

      On the LAN side sure, but I don’t think many people would make a public website/webapp “true single stack”. If there’s a network appliance “terminating” the IPv6 connection and “NATting” it over IPv4 that’s a terrible hack that is even worse than not having it at all imho

      Unless you’re talking about the link-local fe80 addresses, but those are basically sparkly MAC addresses

      • quick_snail@feddit.nl
        0·
        9 days ago

        On WAN. Often hosting providers charge extra for ipv4 addresses, so many servers just don’t get them anymore

  • joel_feila@lemmy.world
    0·
    10 days ago

    we did a few tricks to get more use out of ipv4 address. take 192.168.100.1 that is a private ipv4 address it can not connect directly to the internet. Most home routers will have a single public ipv4 address and assign some private address to each device connected to it. So now each home can have 1 device with 192.168.100.1. This means we kept using ipv4 for a long time after ipv6 came out.

    Second updating all the old routers and switches. At this point in time it is unlikely you will find a router in the wild that can’t use ipv6. Someone let me know the last time you found a device on some job site. But it took a while to get there because its expensive to replace them and no one was going to cough the massive amount of money to get it done in just a year or two.

    Here is a full ipv6 address 2001:0db8:85a3:0000:0000:8a2e:0370:7334, yes it can be shortened to 2001:db8:85a3::8a2e:370:7334. That’s still a pain to type out and yes it did make a mistake just typing that one address. It is just more error prone to write and type out ipv6 addresses.

    • maturelemontree@lemmy.zip
      0·
      10 days ago

      Yeah I did networking on Navy ships which used technology from the 60s. We checked a certain devices software and it was originally booted in 1962. Still, everything was IPv6 capable.

  • KiwiTB@lemmy.world
    0·
    11 days ago

    Ipv6 is widely used, but it can be used along side ipv4 so until ipv4 because unused it’ll be there

  • 𝘋𝘪𝘳𝘬@lemmy.ml
    0·
    11 days ago

    Why is this?

    Most corporations have the inertia of a rock when it comes to changes. There is no real reason behind it. Implementing IPv6 is a no-brainer. Same with NATing legacy systems so they can continue using IPv4.

    Instead of manually juggling IP addresses, properly set up environments use hostnames and handle DNS automatically.

    It’s basically “we/I don’t see any short-term benefit from it, it causes some setup work, and it is not important because everything still works”.

  • slazer2au@lemmy.worldEnglish
    0·
    11 days 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

    • palordrolap@fedia.io
      0·
      11 days 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.)

    • NeatNit@discuss.tchncs.de
      0·
      11 days 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
      0·
      11 days 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…

  • Greg@discuss.tchncs.deEnglish
    0·
    11 days ago

    IIRC security is nonexistent when you deep dive into ipv6, thus no one can guarantee anything which in return gets 0 investment for implementation.

    • 4am@lemmy.zip
      0·
      11 days ago

      IPv6 has the same level of security as IPv4.

      If you mean to say that IPv4 NAT provides security, well please never work on any networks that I need to use.

  • inkblade@lemmy.world
    0·
    11 days ago

    Maybe because a 128-bit hexadecimal address is impossible to memorise. I know all (6) my IPV4 addresses.

  • Zwuzelmaus@feddit.org
    0·
    11 days ago

    Additionally, why didn’t IPv6 replace v4

    Same reasons why electric vehicles have not replaced gas powered vehicles (yet).

    The engine is not easily exchangeable, and there are still enough people who build, and people who buy the older models.

  • pryre@lemmy.world
    0·
    11 days ago

    I think you might be underestimating uptake. Google suggests upwards of 50% usage. Also I’m fairly certain that a lot of residential infrastructure has been slowly moving to IPv6 in Australia at least. Not an overnight process, but it’s happening. Over here we have a lot of newer mobile plans offering IPv6 as well.

    I think a big holdback is that a lot of larger corporations will still use IPv4/NAT setups at the top level, even if all of the hardware in the network supports it. “If it’s not broke don’t fix it.” The result is huge amounts of daily traffic coming from these institutions being IPv4 by default, with all devices in WiFi, etc, being lumped into the same group.

    • zzffyfajzkzhnsweqm@sh.itjust.worksEnglish
      0·
      11 days ago

      I love australia for it. We had to support IPv6 because some of your clients were IPv6 only. And I think this is a good thing. Some push is neccessary.

  • dhork@lemmy.worldEnglish
    0·
    11 days ago

    I think people are missing a main point here. There is nothing wrong with IPv4, it works. It just can’t scale globally anymore, it doesn’t have enough space.

    If you are running a worldwide network with millions of nodes, IPv6 is essential. But for things that are smaller than that, it becomes less essential. But what’s the best metric for adoption, how many small offices or home labs adopt it? Or how many large, worldwide networks?

    • dbtng@moist.catsweat.com
      0·
      11 days ago

      When IPv6 was created, NAT technologies had not yet really developed yet. That development stretched out the utility of IPv4 and allowed it to be perfectly sufficient even today. Back then, you bought a public IP for every node on your network. Seems crazy now, because you can put an entire enterprise behind one IP.

      IPv6 was created to allow that same provisioning concept of every node having a public IP. Well, we don’t really need that anymore. So we relegate IPv6 usage to machines like cell phones, but if a human has to utilize the address, we give em an IPv4.

      • SmoothLiquidation@lemmy.worldEnglish
        0·
        11 days ago

        IPv6 was created to allow that same provisioning concept of every node having a public IP. Well, we don’t really need that anymore.

        I’m my home lab I don’t want every node to have an external IP. I like that NAT forces me to provision holes for specific purposes and between reverse proxy and limited port forwarding I get all of the functionality that I need.

        I know I can get similar security using firewall rules and DNS but it is hard to want to replace something that just works.

  • Treczoks@lemmy.world
    0·
    11 days ago

    There are a number of points:

    If you build a networking devices, you have to have IPV4. You may or better should have IPV6, too, but without IPV4, you’ll have a bad start.

    If you build an embedded system, like an “internet of things” sensor or actor, memory is at premium, so having to take care of a small and a large IP stack might be challenging.

    Some systems are old that their software libraries don’t even offer an IPV6 option.

    My current project uses IPV4 only, because I don’t need anything fancy. I just span a 10/8 network with 10.0.0.1 being the server. No routing, not even DNS. Using IPV6 for that application would be wasted.

  • Björn@swg-empire.de
    0·
    11 days ago

    For me personally it’s unfamiliarity. Technically all my devices and networks use IPv6. But I just enabled it in my router and used my hosting company’s configuration.

    But one of my servers at home should be reachable from the internet but that is only through IPv4. Configuring port forwarding through my router was intuitive and straight forward. But for IPv6 I have to allow the port to be open, but I don’t want it to be the standard port so I have to configure the corresponding service on the machine itself to listen with a specific port on a specific address. But I have no idea what each of the addresses it has mean.

    I think some of them are purely internal, some temporary, some less so. And if I ever found out what to use I would then have to configure my DynDNS, which is currently just pointing to the public IPv6 address of my router but not to the server I would want to reach.

    I could learn all these things. But I just can’t be bothered because the IPv4 stuff still works.

    • orgrinrt@lemmy.world
      0·
      11 days ago

      At least you have ipv6 as an option…

      I will switch the second it becomes available here. Won’t hold my breath though…