// Infrastructure Lab
A Proxmox-based lab environment I run for hands-on infrastructure engineering. Production-like in design - monitored with PRTG, documented, and intentionally broken.
Network Topology IPs randomised per session · 10.1.x.x RFC-1918
| Service | Host | Status |
|---|---|---|
| PRTG Network Monitor Core server - 218 sensors |
monitor-lxc | Running |
| PRTG Remote Probe Distributed probe - lab segment |
docker-host | Running |
| Traefik v3 Reverse proxy / TLS termination |
docker-host | Running |
| Portainer Container management UI |
docker-host | Running |
| AdGuard Home DNS filtering - all VLANs |
lxc-dns | Running |
| Ollama + Inference API Local LLM serving (RTX GPU) |
gpu-vm | Idle |
| ID | Name | Subnet |
|---|---|---|
| 10 | Servers | 10.1.x.0/24 |
| 20 | Lab | 10.1.x.0/24 |
| 30 | IoT | 10.1.x.0/24 |
| 99 | Mgmt | 10.1.x.0/24 |
Stack at a Glance
// Hardware
// Lab Design Principles
The homelab is deliberately designed to mirror production infrastructure patterns - not as a toy environment, but as a real platform I operate and learn from. OPNsense handles firewall and routing with proper VLAN segmentation on the Cisco switch, matching the layered security model of enterprise environments. Everything is monitored via PRTG with meaningful alert thresholds, changes are tracked in Git, and I intentionally create failure conditions to understand how things break.
Current focus areas: declarative service management with Docker Compose, cloud-init-based VM templating in Proxmox for zero-touch provisioning, and building PowerShell-based PRTG custom sensors for application-layer health checks that SNMP/WMI can't surface.