My first setup

Why I started my home lab?

In my third semester at MITT, we had to run multiple VMs (Virtual Machines) — things like Microsoft Server, Linux, and different versions of Windows for my Microsoft Server class. At the time, I only had a low-end laptop, and there was no way it could handle VMware and all those VMs.

So, I decided to buy a cheap refurbished desktop with better resources to run my VMs. But then I hit another problem: if the desktop stays at home, how am I supposed to access my VMs from school (or anywhere else)?

That was also the time when we were expected to show off our skills to land good co-op placements. So I figured the best way was to build my own home lab, set up my desktop at home, and make it accessible from school or wherever I am.

Step 1: Building My First LAN (Local Area Network)

I decided to separate my homelab network from my family’s network using a Cisco router, switches, and an access point. The goal was both practical (keep my stuff isolated) and educational (get hands-on experience with VLANs, ACLs, and real networking gear).

Problems I noticed later:

Fan noise from the Cisco gear was annoying.
Too much CLI work just to make small changes.
Redundant setup — why should I run two APs (one on Cisco, one on my ISP modem)?

Step 2: Building My Rack

I kinda loved the idea of having a rack. It kept all my gear organized in one place and gave me that “real data center” feeling.

Problem:

Uneven space between devices.
No cable colour coding → messy look.
Didn’t feel as clean and professional as I wanted.

Step 3: Remote Access & Virtualization

Once the hardware was set up, it was time to go into software. I installed VMware to run my VMs and then looked into remote access.

I decided to use WireGuard on a Raspberry Pi running Linux. That gave me a secure VPN tunnel into my lab from anywhere.

Problem:

Why should I need a separate piece of hardware just to run another OS? (felt like extra overhead).

Step 4: Wake-on-LAN

To avoid walking over and manually powering on my desktop, I configured Wake-on-LAN. Once the rack was powered up, I could send a “magic packet” from the Raspberry Pi to wake my workstation remotely.

Step 5: Mission Accomplished

With all of this in place, I had my first full homelab setup running:

A dedicated LAN separated from my home network.
Organized rack with Cisco gear.
Remote VPN access using WireGuard.
Wake-on-LAN automation for my workstation.

I know for some people these might seem like basic setups, but for me it was the start of really getting hands-on experience in IT. Every challenge gave me something new to learn, and that’s what makes this setup meaningful to me and start up of IT journey in the young aga.

🚧 Problems & Lessons Learned

Even though my first setup worked, I quickly noticed a few limitations:

Fan Noise – The Cisco gear was loud and not practical for running at home 24/7.
Too Much CLI – Simple tasks took too long to configure. Great for learning, but not ideal for daily use.
Redundant Access Points – Running two APs (ISP modem + Cisco AP) felt unnecessary.
Rack Setup Issues – Uneven spacing, no cable colour coding, and not as clean-looking as I wanted.
Extra Hardware Overhead – Using a separate Raspberry Pi just for WireGuard VPN made me rethink efficiency.
VM Host Choice – Windows consumed too many resources as a VM host. I started looking into Proxmox for more flexibility.

👉 These “basic” challenges might not sound like a big deal to some, but they gave me valuable hands-on experience and showed me where I could improve. They also became the foundation for my next goated project, where I take all these lessons and build something even better.

Page updated

Google Sites

Report abuse