homelab

proxmox and truenas, plus somewhere to break things where it doesn't matter.

one proxmox host and one truenas box, with most services running in lxc containers. media and a few household services live there, which is the part that gets used most often.

tthere's a separate dataset set aside for security work, kept off the rest of the network. it's not built out much yet.

• host: proxmox, lxc for anything that doesn't need a full vm
• storage: truenas, zfs, nfsv4 to the containers
• services: media and household services, containerised
• access: tailscale, nothing forwarded at the router
• lab: separate dataset, isolated from the rest of the network

containers could read from truenas but not write to it. two causes: root squash meant fixes had to be made on truenas rather than the client, and the dataset was using posix acls, which were blocking writes even with the right ownership.

fixed by stripping the acls, setting ownership on truenas, and moving container configs off the mount to local storage.

truenas is moving off proxmox to bare metal. virtualising the system that holds the data means the hypervisor can take the data with it which is a bit risky. general compute moves to a dedicated mini pc, and the whole setup goes into a rack.

after that, building out the security lab: persistent target machines and properly tested segmentation.