• heartSagan5@lemmy.zip
    link
    fedilink
    English
    arrow-up
    5
    ·
    1 个月前

    I’m okay with IPv6, if I can get a hexadecimal keypad. I know, DNS solves it to a degree, but just pumping in link-local can be a keyboard dance.

    Unfortunately, my ISP doesn’t yet offer IPv6 due to PPPoE to authenticate and authorize subscribers.

    • mholiv@lemmy.world
      link
      fedilink
      English
      arrow-up
      4
      ·
      1 个月前

      Humans shouldn’t really be typing in IPs. Why not just use localhost for localhost and dns / mdns for lan machines? It’s such a nicer experience.

      mdns works with link-local in the case of a private non connected lan.

      • sem@piefed.blahaj.zone
        link
        fedilink
        English
        arrow-up
        5
        ·
        1 个月前

        Dns doesn’t always work, and seeing if you can connect via IP is often a troubleshooting step

        • mholiv@lemmy.world
          link
          fedilink
          English
          arrow-up
          3
          ·
          1 个月前

          True. But pinging IPs directly should only be done as a debug step when dns / mdns does not work. Aka extremely rarely.This all being said mdns is extremely reliable on lan. It’s literally just multicast dns on lan.

          On my personal home network I have never had mdns fail in 5-ish years. FQDNs yah. DNS can break. But mdns has been solid.

          • sem@piefed.blahaj.zone
            link
            fedilink
            English
            arrow-up
            1
            ·
            1 个月前

            I would like to know more about this mdns.

            In my experience, the following are unreliable, and it’s unclear which one is supposed to work under which context:

            • ping hostname
            • ping hostname.local
            • ping hostname.<whatever that local domain thing is called>

            While pinging the ipv4 address is reliable; if the device is reachable on the network, it should respond.