Phase 1: Overcoming Wi-Fi Limitations & The Linux Mint Era

The Challenge of Wireless Virtualization

Originally, the home server infrastructure was heavily constrained by environment variables: running two active servers entirely over a Wi-Fi connection. This created a massive roadblock for deploying Proxmox early on, as Proxmox relies heavily on network bridges, and standard wireless cards do not support bridging cleanly.

Initial Workarounds & Evolution

To cope with these network limitations, several virtualization solutions were tested:

1. VirtualBox & Vagrant: Used initially to automate deployments. While functional, it was a clunky setup where software updates frequently broke configurations.
2. Linux Mint with KVM/QEMU: Migrated to a more stable foundational layer using Linux Mint on both host machines. Virtual machines were managed using a combination of virt-manager and the Cockpit Machines UI. This provided a reliable environment that handled wireless interfaces smoothly.

Network Workarounds

Because VMs were restricted to their internal virtual networks and could not directly sit on the local network, creative routing was required:

• Tailscale: Deployed so that external nodes could establish direct communication with the isolated VMs.
• Nginx Proxy Manager (NPM): Installed directly on the host machine to bind and forward ports 80 and 443. Combined with Tailscale, this made services inside the virtual networks securely usable.
• Host-Bound Services: Applications requiring native local network discovery (such as Home Assistant) had to be deployed directly on the host OS. Similarly, network-wide tools like AdGuard Home required plugging in a secondary wireless card dedicated via PCI Passthrough.

Despite these setbacks, a surprising amount of self-hosted services were successfully deployed and maintained.