Migrating a Proxmox server from zfs-auto-snapshot to sanoid for ZFS snapshot management. The server has been running zfs-auto-snapshot with systemd timers for over a decade, but the AUR package description notes that as of 2021, sanoid and zrepl are better maintained alternatives. Since I’m setting up a new backup pipeline anyway, seemed like a good time to make the switch. The main difference between the two is configuration model. Where zfs-auto-snapshot uses ZFS properties (com.

This guide outlines the steps to set up a Linux bridge device connected to a physical Ethernet interface with a specific VLAN tag. In this article the VLAN tag will be assumed as 170 but it can be any valid VLAN tag/id. In the world of networking, a Linux bridge device is a powerful tool that acts as a virtual switch, connecting different network segments seamlessly. It operates at the data link layer (Layer 2) of the OSI model, forwarding traffic between connected interfaces based on their MAC addresses.

The rtl_433 that comes bundled with Homebrew on macOS does not support SSL. Which means that we need to compile it from source. It is rather straight forward to do so. Uninstall rtl_433 If you already have rtl_433 installed via Homebrew it should be removed first. brew uninstall rtl_433 Dependencies brew install cmake pkg-config openssl@3 Compile from Source git clone https://github.com/merbanan/rtl_433.git cd rtl_433 mkdir build cd build cmake -DOPENSSL_ROOT_DIR=$(brew –prefix openssl@3) .

After installing Cockpit you will likely end up with certificates that are self-signed and therefore untrusted by default. There is a better way; Let’s Encrypt. NOTE: Through out the article the fully-qualified domain name of the Cockpit server is treated as a variable (e.g., $FQDN). Make sure to either define a similar variable with an appropriate value or replace it when copying the commands. Install certbot First thing is first, install certbot1.

Installing Podman on Proxmox is rather straight forward. The initial idea for how to do this came from a post on the Serve the Home (STH) blog: Create the Ultimate Virtualization and Container Setup (KVM, LXC, Docker) with Management GUIs. In that article STH uses Docker and provides a Portainer GUI. In this example the Portainer GUI is going to be omitted and use Podman instead of Docker. The daemonless part of Podman is the real selling point.