Skip to content
← Back to projects

INFRA-01 / Live

Homelab

My personal infrastructure, segmented and monitored like real production.

Role
Design, deployment, operations
Period
Since 2024
Stack
OPNsenseProxmox VEVLANsWireGuardActive DirectoryWazuhPrometheusGrafanaLokiAnsible
  • 2Proxmox nodes
  • 3isolated VLANs
  • 1exposed port

● Topology

Select a device to see its role. Addressing is fictional.

WAN Internet WAN VPN Admin distant 10.99.0.0/24 FW OPNsense CWWK N150 SW Switch managé TP-Link · 802.1Q PVE pve-01 EliteDesk G4 PVE pve-02 EliteDesk G4 CT Jellyfin LXC CT Elastic SIEM WAN Internet WAN VPN Admin distant 10.99.0.0/24 FW OPNsense CWWK N150 SW Switch managé TP-Link · 802.1Q PVE pve-01 EliteDesk G4 PVE pve-02 EliteDesk G4 CT Jellyfin LXC CT Elastic SIEM

CWWK N150

OPNsense

Router and firewall. Filtered inter-VLAN routing, internal DNS with Unbound, WireGuard server, Suricata as IDS.

  • 802.1Q trunk
  • WireGuard
  • Proxmox cluster

Why

Reading documentation isn’t enough to learn network security: you need infrastructure of your own that you can break without consequences. This homelab is built like a small production environment: segmented, monitored, and safely administrable from anywhere. Every other project runs on it.

Architecture

  • Router / firewall: OPNsense on a CWWK N150 mini-PC. It routes between VLANs with explicit rules (default deny) and serves internal DNS through Unbound.
  • Virtualization: a two-node Proxmox VE cluster on HP EliteDesk 800 G4 machines. One node hosts services, the other hosts the offensive lab.
  • Switching: a managed TP-Link switch, with an 802.1Q trunk to the firewall and tagged ports per VLAN.
  • Remote access: WireGuard only. No admin interface is exposed to the Internet.
  • Internal services: Active Directory, DNS, PKI, reverse proxy, GitLab, and Jellyfin in an unprivileged LXC container, across both Linux and Windows environments.
  • Monitoring and detection: metrics with Prometheus and Grafana, logs with Loki, security events with Wazuh.
  • Automation: system configuration with Ansible.

Security choices

  • Default deny between VLANs. Every allowed flow is justified and documented.
  • Offensive lab isolation: the attack VLAN cannot reach the management VLAN.
  • Minimal attack surface: a single UDP port open on the WAN.
  • Internal PKI with step-ca, for TLS everywhere, even internally.

Takeaways

Design the addressing plan and the filtering rules before plugging anything in. And above all: infrastructure you don’t monitor is infrastructure you don’t know.

I'm looking for a 36-month apprenticeship (work-study) in cybersecurity, systems or network administration during my engineering degree at ECE.

sacha@soc — bash