Initial software setup of 2023 home router
As discussed in earlier post, the hardware choice was ultimately simple given the requirements. Even top-level software choice (Linux running Debian) did not seem particularly hard, but then started the hard part: coming up with reasonable design for what to run there. The requirements (2023 November) As I had 2,5GB ethernet ports (finally), my main Mac and NAS had to be directly connected to the box I used to have separate 2,5GB point-to-point between the two, but using simply one port in each instead of two made management slightly simpler and less error prone ’Internet-facing’ part would need to be relatively static and not touching Debian directly at all (instead, something bit more hardened would be the first ingress point) Both rootful and rootless containers would be nice to have The more containers the merrier - at this point I foresaw about half dozen useful containers something firewall/router-y facing internet DNS ad blocker (e.g. adguard, or pi-hole) reverse proxy to handle HTTPS (from both inside home, as well as from the internet) using proper certificates (e.g. caddy, traefik) home assistant (for home visibility and automation) jellyfin (for media) Infrastructure as Code (IaC from now on) What I did not choose to use Proxmox ( https://www.proxmox.com/en/ ) seems like the toy of the hour in the enthusiast circles. I am not quite sure why; perhaps it is the GUI. But the combination of GUI driven material (mostly), as well as not particularly good IaC (no first-party Terraform support - at the time there is third-party one in Proxmox Provider - Terraform Registry) did not make it particularly tempting for me. And besides, I was mostly planning to use pyinfra anyway. ...