• Plopp@lemmy.world
    link
    fedilink
    English
    arrow-up
    1
    arrow-down
    2
    ·
    8 months ago

    I want static addresses on my LAN, and addresses I can remember and easily recognize in a list. And I don’t want my devices to have unique addresses outside my LAN, especially not static ones. NAT is great.

    • p1mrx@sh.itjust.works
      link
      fedilink
      English
      arrow-up
      2
      ·
      8 months ago

      You can statically number a LAN with fd00::/8 and NAT66 to the internet, if you really want to.

        • Plopp@lemmy.world
          link
          fedilink
          English
          arrow-up
          1
          ·
          8 months ago

          See, what both of you wrote is completely alien and confusing to me. The look of IPv6 gives me an aneurysm. Let me keep my IPv4. You can run IPv6 on your own LAN. I’m not stopping you.

          • ryannathans@aussie.zone
            link
            fedilink
            English
            arrow-up
            1
            ·
            edit-2
            8 months ago

            It’s a little bit unfamiliar, not the end of the world. It’s not complicated and not as nuanced as ipv4 networking. No dhcp necessary anymore on your local network, how good is that? No more trying to hardcode MTU, no strict/open/hairpin/fullcone/etc NAT issues because no NAT, no port forwarding, no fear of IP collisions, less overhead, freedom of many public addresses per interface - host each app on its own public IP address if you desire. Ipv4 over ipv6 is part of the spec so you would never lose ipv4 connectivity. I could go on

      • Plopp@lemmy.world
        link
        fedilink
        English
        arrow-up
        1
        ·
        8 months ago

        My brain stops me from remembering and recognizing IPv6 addresses. I can’t deal with long strings of hex. And why are people so against me running IPv4 on my own LAN? Do I make you sad? Do I ruin your day? I love IPv4, and NAT works perfectly fine for me. I’m not doing the translation, my router is.

        • ryannathans@aussie.zone
          link
          fedilink
          English
          arrow-up
          1
          ·
          8 months ago

          You don’t need to have long addresses, you should be using hostnames and domains anyway. Ipv6 addresses are often simpler than ipv4 ones. E.g. prefix::1 for your router. Prefix::2 for the next device, and so on to Prefix::FFFF for the first 65k machines if you wish to set it up that way. Ipv4 exclusively on your lan ruins my day because I have to maintain servers and software to support users that only use ipv4 and flat out refuse ipv6 connectivity - it’s expensive and takes a lot of effort to maintain dual stack support.