Hi all, I’m running a small website off of a raspberry pi in my house. I have opened ports 80 and 443 and connected my IP to a domain. I’m pretty confident in my security for my raspberry pi (no password ssh, fail2ban, nginx. Shoutout networkchuck.). However, I am wondering if by exposing my ports to the raspberry pi, I am also exposing those same ports to other devices in my home network, for example, my PC. I’m just a bit unsure if port forwarding to an internal IP would also expose other internal IP’s or if it only goes to the pi. If you are able to answer or have any other comments about my setup, I would appreciate your comment. Thanks!

  • Contravariant@lemmy.world
    link
    fedilink
    English
    arrow-up
    0
    ·
    1 year ago

    I suppose it depends on what you want to do. I’m currently only hosting stuff for my own purposes so it is fine if I can just access it from devices I trust.

    My setup is more like

    Wireguard (on Phone/Laptop/etc) <–> Wireguard (on RaspberryPi) <–> Reverse Proxy (on RaspberryPi) <–> local stuff (mostly in docker on RaspberryPi)

    The advantage is that the only service accessible from outside is Wireguard, so even if some service running behind the reverse proxy is insecure I’m still the only one with access.

    Obviously one of the disadvantages is that I can’t access it (easily) from some random device, but I can access it from my phone and in an emergency I do have keys that I can use to install wireguard somewhere else, but I would require admin rights to some device to do so.

    • ChrislyBear@lemmy.world
      link
      fedilink
      English
      arrow-up
      1
      ·
      1 year ago

      Ah yes. I’ve been there. But since I’ve onboarded my family onto my domain and they use a few of the services I needed a low but still secure barrier of entry. Hence the more “public” approach.