Case Study

Proxmox Home Lab.

A preserved infrastructure case study for virtualization, lab topology, Windows/Linux administration practice, and documentation-first operations.

Back to ProjectsOpen Proof Library
Home lab network topology diagram

Executive Summary

A lab foundation for practical systems administration review.

This case study ties the preserved home lab PDF and topology diagram to infrastructure learning outcomes: virtualization, service placement, network boundaries, documentation quality, and operational troubleshooting context.

Business Objective

Show a realistic practice environment for support and infrastructure skills.

Give recruiters and technical reviewers a concise route from project summary to preserved lab evidence without overstating production experience.

Skills Demonstrated
  • Proxmox and virtualization concepts
  • Windows and Linux lab workload awareness
  • Network topology documentation
  • Infrastructure boundary mapping
  • Evidence preservation and reviewer handoff

Technical Environment

Preserved home lab infrastructure context.

The evidence references a Dell R710 and lab workloads, Proxmox concepts, network switching, Active Directory-style services, DNS/DHCP context, Microsoft administration concepts, and PowerShell-supported operations.

Interactive Topology

Click a node or isolate a flow to review the lab service model.

This interactive diagram keeps the home lab evidence understandable for recruiters while still showing the technical relationships between virtualization, firewalling, identity, network services, VPN access, segmentation, and monitoring.

case study topologyFocused on Proxmox virtualization
Interactive Proxmox home lab topology Clickable topology showing pfSense, Proxmox, Active Directory, DNS, DHCP, WireGuard, OpenVPN, VLANs, Windows Server, Linux, and IDS/IPS relationships. Edge Access Core Services Servers Internet and WAN ingress pathWANInternet pfSense firewall, NAT, VLAN gateway, WireGuard, and OpenVPN edgepfSenseFirewall Proxmox virtualization host for Windows Server, Linux, and service workloadsProxmoxCompute Active Directory domain services, Group Policy planning, and identity boundary reviewActiveDirectory DNS and DHCP service placement, lease review, and name-resolution troubleshootingDNSDHCP VLAN segmentation for management, server, client, and lab trafficVLANsZones Windows Server workload for identity, management, and support validationWindowsServer Linux workload for service hosting, package administration, logging, and network checksLinuxServices WireGuard and OpenVPN remote access path into controlled lab segmentsVPNWG / OVPN IDS/IPS monitoring concept for traffic visibility and alert reviewIDSIPS
Virtualization

Proxmox

I use Proxmox as the virtualization layer for lab workloads, service isolation, snapshot-aware practice, and infrastructure documentation.

Firewall

pfSense

pfSense represents routing, firewall, NAT, VLAN gateway, WireGuard, OpenVPN, and segmentation-control boundaries.

Identity

Active Directory

Active Directory supports domain-service planning, OU structure, Group Policy scope, authentication context, and Windows administration practice.

Core Network Services

DNS and DHCP

DNS and DHCP provide name resolution, lease assignment, reservation review, gateway checks, and common service desk troubleshooting paths.

Remote Access

WireGuard and OpenVPN

WireGuard and OpenVPN model controlled remote access, tunnel validation, firewall rules, and client connectivity troubleshooting.

Segmentation

VLANs

VLANs separate management, server, client, lab, and monitoring traffic so routing and firewall policy remain reviewable.

Server Administration

Windows Server

Windows Server anchors identity, management, service validation, and endpoint support workflows.

Linux

Linux Workloads

Linux workloads support service hosting, package administration, network checks, logging practice, and cross-platform troubleshooting.

Security Monitoring

IDS/IPS

IDS/IPS concepts provide traffic visibility, alert-review context, and segmentation validation without claiming live production monitoring.

Edge

WAN Ingress

The WAN edge shows where outside connectivity reaches the firewall before controlled routing into lab segments.

Architecture Overview

Topology evidence supports project orientation.

The home lab topology diagram provides a quick visual path for reviewers. The preserved PDF remains supporting evidence for the broader lab portfolio and should be treated as historical proof rather than a current production environment claim.

Implementation Approach

Use lab evidence as context for operational workflows.

The lab supports the surrounding case studies by giving a practical environment for identity, networking, DNS/DHCP, automation, and troubleshooting documentation. Claims stay scoped to preserved lab evidence and documented methodology.

Validation Process

Review topology, proof-library index entries, PDF accessibility from public pages, and related evidence links. Avoid implying current uptime, production traffic, or enterprise service ownership.

Lessons Learned

A home lab is most valuable to employers when it is translated into clear diagrams, support workflows, validation notes, and reusable documentation.

Related Evidence

Open the source artifacts.

Home lab topology

Preserved topology diagram for lab network roles and boundaries.

Open Diagram

Home lab PDF

Preserved home lab portfolio PDF retained as supporting evidence.

Open PDF

VLAN walkthrough

Adjacent networking evidence for lab segmentation and Proxmox bridge planning.

Open Walkthrough

DNS/DHCP runbook

Operational runbook for core network service troubleshooting context.

Open Runbook