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

• frezik@midwest.social ⁨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.

  source

  • barsoap@lemm.ee ⁨9⁩ ⁨months⁩ ago

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

    No. It’s 23 or 42.

    source
• SteveTech@programming.dev ⁨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.

  source

  • Khanzarate@lemmy.world ⁨9⁩ ⁨months⁩ ago

    I have never thought of writing things with static ipv6.

    I have been missing out.

    source

    • exception4289@lemmy.world ⁨9⁩ ⁨months⁩ ago

      You’re missing out your ::cafe’s

      source
  • phoneymouse@lemmy.world ⁨9⁩ ⁨months⁩ ago

    fe80::dead:beef

    source
• p1mrx@sh.itjust.works ⁨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.

  source