• kieron115@startrek.website
      link
      fedilink
      English
      arrow-up
      0
      ·
      3 hours ago

      I think you’re missing the point - that’s neither simple nor easy for most people. I’m a network engineer and I don’t wanna deal with setting up and (being responsible for troubleshooting) a bunch of VPNs! Nevermind the additional power/CPU usage from the tunnels. My parents just got fiber and they don’t even have a public address (ipv4 or v6) which just adds another layer of headache. thanks west virginia…

      • Shnog@lemmy.world
        link
        fedilink
        English
        arrow-up
        0
        ·
        3 hours ago

        I’d much rather deal with setting up a few VPN gateways which is trivial at most…than securing a public web service. I deal with that crap enough at work.

        There are a lot less variables to contend with with a single VPN endpoint which undergoes considerably more security auditing than N public web services. Many of which I don’t have the time to review myself and mitigate if they decide to suck at coding.

        Edit: I share my services with less than 5 households though.

        Edit2: I’m not sure what public ipv4 or ipv6 has to do with this. My remote sites use starlink ipv4. I haven’t setup ipv6 on those internally at all. They all tunnel via wireguard to my homesite.

        • kieron115@startrek.website
          link
          fedilink
          English
          arrow-up
          0
          ·
          2 hours ago

          also fyi starlink has public ipv6 available if you DO wan’t to set it up. been hosting a minecraft server off a starlink connection lol.

        • kieron115@startrek.website
          link
          fedilink
          English
          arrow-up
          0
          ·
          3 hours ago

          When I set up wireguard it was just more complicated when one side didn’t have a public IP. Whyyyy can’t we adopt ipv6 already.