• Semi-Hemi-Lemmygod
    link
    fedilink
    English
    216 months ago

    “IP address are four sets of numbers with dots in between AND THAT’S HOW I LIKES IT!” - Me, an old network guy

    Honestly the fact that I can’t remember or type IPv6 addresses is a big reason I haven’t bothered figuring it out.

    • @[email protected]
      link
      fedilink
      11
      edit-2
      6 months ago

      I imagine you sitting there like Scotty, “Give me an ip address, not no colon, not no hexadecimal, and not no bloody double colon. Just 4 numbers between 0 and 255 with a dot in between.”

    • @[email protected]
      link
      fedilink
      English
      26 months ago

      So, my argument here is… Why the hell are you memorizing IP addresses?

      Is your DNS so misconfigured that you’re still punching in IPs by hand?

      DNS is the solution. Going to “router.domain.local” or whatever your internal domain is, is easier to remember than… Which subnet am I on again? Is this one 192.168.22.254? Or 192.168.21.1?

      Stop punching in numbers like a cave man. Use DNS. You won’t even notice if it’s IPv6 after that

      • Semi-Hemi-Lemmygod
        link
        fedilink
        English
        4
        edit-2
        6 months ago

        And what happens when DNS inevitably falls over and I need to fix it?

        And when I’m watching IP addresses scroll by, IPv6 ones are a lot harder to read than v4

        • @[email protected]
          link
          fedilink
          English
          15 months ago

          DNS, by its very nature is redundant. So DNS shouldn’t just fall over. If it does, you’re doing something wrong.

          If you absolutely need to go to IP addresses, they should be documented.

          Unless DNS is outright wrong, there should not be an issue.

          For scrolling: are you staring at active log files? Who isn’t using a syslog aggregator? You can easily look up the IP of whatever device that is interesting and filter the log by that IP.