• 2 Posts
  • 7 Comments
Joined 2 years ago
cake
Cake day: June 19th, 2023

help-circle
  • Yeah I think were on the same track, what I can think of is to do this;

    • Set up firewall rules on my LAN router (which hosts the Wireguard server), restricting access to the Wireguard client coming in from the VPS.
    • Set up firewall rules on the cloud provider to restrict access to anything but my public IP where the Wireguard server is hosted.
    • Do the same in the VPS host internal firewall.
    • Configure the Wireguard server and client config to only allow access to the IPs relevant for the clustering.
    • Set up CrowdSec as part of Pangolin, it’s an integrated feature
    • Move the Newt + service containers exposed via Pangolin to their own isolated VLAN in order to further harden the environment around them
    • Configure Nomad and Consul tokens to only allow the VPS to register the Pangolin services and nothing else

  • But I think that’s kind of where the problem lies; if we’re talking about external firewalls applied on the cloud provider, then I need an external IP for my homelab network to use in the rules, which defeats the point of Pangolin to begin with. And if we’re talking about the firewall inside the VPS, like ufw or whatever, then that would be forfeit if a bad actor would gain root access on that host, they would just disable the rules. This is kind of where my thinking is at currently.