There’s only so much you can learn from a textbook. At some point, you have to break things to understand how they work – and that’s exactly why I built my homelab.

It Started With Curiosity

I was going through college courses for networking when I realized something: the labs were sanitized. Everything worked the way it was supposed to. Configs were handed to you. Topologies were pre-built. But real networks don’t work like that. Real networks fight back.

Networking started as a degree requirement and quickly became a hobby. I wanted to understand what happened when things went wrong, not just when they went right. And the only way to do that was to build something of my own, break it, and figure out how to fix it.

Along with the networking side came the server and infrastructure piece. Once you start running your own services, you start thinking about data ownership, security, and privacy in a completely different way. My homelab isn’t just a study tool, it’s my own private cloud, and I control every packet that moves through it.

Starting From Nothing

The first iteration was embarrassingly simple: a router and a switch. A buddy of mine came over and we stayed up way too late just trying to get the router to connect to the internet. When it finally worked, we were ecstatic. It sounds ridiculous now, but that moment hooked me.

He gave me a Dell OptiPlex, and I threw Proxmox on it. That was the turning point. Suddenly I wasn’t just routing packets, I was spinning up virtual machines, running services, and learning Linux out of necessity. The OptiPlex was never meant to be a server, though. I ran out of RAM and storage fast. That’s when I invested in a Dell PowerEdge R730, and the lab started to look like something real.

Where It Is Today

The lab has grown into a multi-node environment that mirrors the kind of infrastructure I work on professionally:

Network: A Palo Alto PA-850 handles firewalling with zone-based segmentation. A Cisco Nexus 9372TX runs as the core switch, with a Catalyst 3650 at distribution. Cisco 9130AXI access points provide enterprise wireless. EIGRP handles routing across all VLANs with a routed access design.

Compute: Three Proxmox nodes form a cluster, hosting everything from Active Directory and TACACS+ to a 9800 WLC and a Docker host running Grafana, Prometheus, and a handful of other services.

Lab Environment: Cisco CML runs as a VM for CCNP study – OSPF, EIGRP, BGP multi-AS topologies, STP tuning, vPC, and VXLAN EVPN fundamentals. It’s where I can test configurations before touching anything in the production side of the lab.

Monitoring: Prometheus collects metrics, Grafana visualizes them, and Uptime Kuma watches service health. If an interface flaps at 2 AM, I know about it.

The Gear Hunt

Almost everything was bought on eBay. Enterprise networking gear depreciates hard, which is great if you’re building a lab on a budget. A switch that cost thousands new shows up for a fraction of that once it’s a few generations old.

Some of the best gear I have came from connections I’ve made through the buying process. The homelab community is generous — people pass along equipment, share configs, and help each other troubleshoot. I’ve built real friendships through this hobby, and a few of those connections have opened professional doors too.

What the Homelab Actually Taught Me

The biggest thing isn’t any specific protocol or platform. It’s troubleshooting.

When something breaks in a college lab, you raise your hand. When something breaks in your homelab at midnight, you open a browser and start reading documentation. You learn to parse vendor docs, dig through forum threads, cross-reference RFCs, and test hypotheses methodically.

That skill, knowing how to find answers when nobody’s handing them to you, is the single most valuable thing I’ve taken from this experience. Every interview I’ve walked into, every production issue I’ve resolved at work, traces back to the habits I built troubleshooting my own gear at home.

What’s Next

There’s a lot on the roadmap, but I’m keeping the details for future posts. Let’s just say the lab isn’t done growing.

If you’re thinking about building your own homelab, start small. A router, a switch, and a willingness to stay up too late is all it takes. The gear will come. The skills will follow.

This post is part of an ongoing series about my homelab. Follow along for deep dives into specific builds, configurations, and the occasional troubleshooting war story.