Amazon finds $1B jackpot in its 100 million+ IPv4 address stockpile
www.techspot.com
Amazon Web Services (AWS) flipped the switch on its new IPv4 address pricing scheme on February 1 as it had announced months prior. The new policy means...

Amazon finds $1B jackpot in its 100 million+ IPv4 address stockpile | The tech giant has cited ballooning costs associated with IPv4 addresses::undefined

  • abhibeckert@lemmy.worldEnglish
    22·
    9 months ago

    IPv6 is here, and has been for a long time. But if, for example, your web or email server can only be reached over IPv6 some people will not be able to load the site or send emails to you.

    The entire internet is configured to work with IPv4. Some of the internet (less than a quarter) is also configured to also work with IPv6.

    Imagine if your home had two driveways on different streets. Do you tell everyone both addresses, or do you pick one of them? Probably just one right? Now imagine if the second address can only be reached if someone has an off road capable vehicle. And you don’t know what vehicle someone has - which address would you give them? Is it even worth having two driveways?

    That’s the situation we’re in. IPv4 support is required and works perfectly. IPv6 is optional and doesn’t always work.

    • elrik@lemmy.worldEnglish
      4·
      9 months ago

      IPv4 support is required and works perfectly.

      Except it doesn’t work perfectly, because it has a relatively small address space. That’s why ipv6 exists.

      • otp@sh.itjust.worksEnglish
        4·
        9 months ago

        The driveway works perfectly, but it doesn’t have space for all the guests if they all want to use their own vehicles.

        Thankfully, we have carpooling and rideshares.

    • KairuByte@lemmy.dbzer0.comEnglish
      0·
      9 months ago

      “Luckily” we are reaching the point where IPv4 just isn’t going to be fiscally sustainable for the majority of companies, meaning the push to IPv6 will be hastened.

      Though I don’t pretend it isn’t going to be a hell of a ride.

      • ___@lemm.eeEnglish
        51·
        9 months ago

        192.169.x.x will always be easier than fe80:x:x::x:x

        • frezik@midwest.socialEnglish
          6·
          9 months ago

          I had a roommate once who need an IP for something, and because it was a device I had been working with recently, I just rattled off “192.168.0.7” or something.

          He was in awe of the fact that I could remember it. However, it’s not that difficult when you know the private prefix you use is always “192.168.” and that gets burned into your brain. The next octet is often zero (maybe 1 if your home network gets crazy), and you really only need to remember the final octet for the device.

          Point is, fe80::x will go the same way. You’ll remember fe80, and the rest is however you handled your own network scheme.

          (I can never remember the class B private address space, though. Only classes A and C. Never needed to bother with the class B space when you can subnet 10.x.x.x so much.)

          • barsoap@lemm.eeEnglish
            1·
            9 months ago

            The next octet is often zero (maybe 1 if your home network gets crazy)

            No. It’s 23 or 42.

        • SteveTech@programming.devEnglish
          2·
          9 months ago

          I definitely agree with automatically configured stuff, but I enjoy setting link-local static IP address with IPv6, like my home server is fe80::bad:c0de or 192.168.0.2, and my NAS is fe80::coo1:da1a or 192.168.0.3. I’ve definitely mistyped the IPv4 a few times (see your 169 typo), but the IPv6 always delivers hackerman vibes.

          I have also set <prefix>::bad:c0de and have my IPv6 prefix on a keybind, but I understand that’s a bit of a stretch.

        • p1mrx@sh.itjust.worksEnglish
          1·
          9 months ago

          fd00::x is shorter than 192.168.x.x

          Technically you’re supposed to use fdxx:xxxx:xxxx::x, but on your home network nobody cares.