• Shnog@lemmy.world
    link
    fedilink
    English
    arrow-up
    3
    ·
    edit-2
    10 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
      4
      ·
      10 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.

    • kieron115@startrek.website
      link
      fedilink
      English
      arrow-up
      2
      ·
      10 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.

      • Shnog@lemmy.world
        link
        fedilink
        English
        arrow-up
        1
        ·
        9 hours ago

        At my remote site it has little value. At my home I have IPv6 setup on Starlink as my secondary backup internet. I use Fiber as the primary that has a public IPv4 and IPv6.

        Could just use a VPS though I guess if you want.