• ryannathans
    link
    fedilink
    English
    arrow-up
    1
    ·
    11 months ago

    Nothing stops you doing that with ipv6. NAT is complicated and unnecessary.

    • Plopp@lemmy.world
      link
      fedilink
      English
      arrow-up
      1
      ·
      11 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
        link
        fedilink
        English
        arrow-up
        1
        ·
        11 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.

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

          Most of the time I do use hostnames, but it doesn’t matter what I use as a user if I have a list of addresses I have to look through in log files, or enter addresses for configuration or whatever. My brain works on IPv4. I’m sorry for ruining your day, but I assume, or at least hope, that you get paid for the work. I do not and I have more important and pressing things to do than learn IPv6 and reconfigure my whole network.