• FrederikNJS@lemm.ee
          link
          fedilink
          English
          arrow-up
          6
          ·
          11 months ago

          Because there’s no such thing as private address spaces in IPv6.

          If your ISP is IPv6 only, then you need to enable IPv6 for your local network too, which means that every device on your network gets an IPv6 address.

          You can still have a private IPv4 as well, but if your remove the IPv6 support, then you lose access too the Internet.

        • Supermariofan67@programming.dev
          link
          fedilink
          English
          arrow-up
          3
          ·
          edit-2
          11 months ago

          When you want the private network to connect to a public IPv6 network. Most people connect their LANs to the public Internet

        • ryannathans@aussie.zone
          link
          fedilink
          English
          arrow-up
          12
          ·
          11 months ago

          Not only that, but ipv6 makes networking easier and less complicated. No longer, needing port forwarding or NAT, amongst other improvements

          • Blackmist@lemmy.world
            link
            fedilink
            English
            arrow-up
            4
            arrow-down
            3
            ·
            11 months ago

            It’s that necessarily a good thing?

            I remember suddenly needing a firewall on my PC back in the days of the Blaster worm.

            Do we really want all those crappy IoT devices open on all ports to the general internet?

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

            I’d be fucked if I had to deal with IPv6 at home. Give me NAT, port forwarding and a dynamic public address that changes.

            • ryannathans@aussie.zone
              link
              fedilink
              English
              arrow-up
              4
              ·
              11 months ago

              Slaac does everything for you. You get dynamic public addresses that change (you can disable if you please). Nothing to deal with, just open a firewall port if you want to receive traffic

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

      • BearOfaTime@lemm.ee
        link
        fedilink
        English
        arrow-up
        4
        arrow-down
        15
        ·
        edit-2
        11 months ago

        No shit.

        But a private Lan will never need it.

        There are 4 billion+ possible IP v4 addresses, nearly 600 million in the current private range.

        Show me a private network with 600 million devices.

        There’s no reason a device that doesn’t have a direct internet connection needs IP6.

        • Nighed@sffa.community
          link
          fedilink
          English
          arrow-up
          8
          ·
          edit-2
          11 months ago

          Ideally, using just IP6 would be simpler, as every device gets a global address. Then you don’t need to mess with NAT, port forwarding and all that bullshit. Every device having multiple addresses just complicates things.

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

          A device on your private IPv4 network can send packets directly to 104.21.36.127 via NAT. How will it send packets to 2606:4700:3033::6815:247f? There’s not enough space in the IPv4 header.

    • Supermariofan67@programming.dev
      link
      fedilink
      English
      arrow-up
      21
      ·
      11 months ago

      A lot of the world, especially Africa and south America, was somewhat later in adopting the Internet and has a much smaller supply of IPv4 addresses. People with ISPs there need IPv6 to be directly connectable without CGNAT

    • thanevim@kbin.social
      link
      fedilink
      arrow-up
      13
      ·
      11 months ago

      PXE, or network boot. It is basically never used (and rarely enabled, if ever, by default) by the individual, but can be helpful in, for example, a large scale OS deployment. Say IT has to get their corporate image version of Windows 10/11 installed on 30 new laptops. They could write a ton of flash drives, but it’d be easier to just host a PXE boot server and every laptop just listen to them.

      V6 specifically in that instance would just be for the reason of “we need to move away from v4 anyways”