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

  • KairuByte@lemmy.dbzer0.com
    link
    fedilink
    English
    arrow-up
    0
    ·
    8 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.ee
      link
      fedilink
      English
      arrow-up
      0
      ·
      8 months ago

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

      • SteveTech@programming.dev
        link
        fedilink
        English
        arrow-up
        1
        ·
        8 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.works
        link
        fedilink
        English
        arrow-up
        1
        ·
        8 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.