Gonna echo some of the other replies on what I’ve used at home that’s helped me out.

1. Media - Used Windows Media Center on Windows XP/7 to start with > XBMC/Kodi > Plex - on several different machines

2. Networking - First wireless router was a Netgear N750, and it was great until the wife spilled some water on it > Netgear Nighthawk R7000 > Ubiquiti Edgerouter ER-X and UAP-AC-LR Access Point > still using the ER-X router but got a U6-Lite AP and then an Engenius controller and ECS-357 AP > ER-X and Aruba AP315/325 converted to be IAP models.

Got a Meraki MS120-8LP switch for POE for my APs. Ended up getting a bunch of Cisco switches and routers of different models to use at home from my current job. Still haven’t setup a working lab with those yet.

3. Compute - This has been the most recent developments due to getting disposal mini desktops from work. Currently have a 3 node Proxmox cluster with 2 Windows server 2022 eval vms. One is a domain controller and the other is going to be setup for MECM(new acronym for SCCM).

I reckon that’s it for now.

Hypervisor cluster, K8s Cluster, routed Vlans. Learn a lot of IT things building clusters and lot of networking things building out a routed vlan network. Before that just hosting websites, network shares, email, setting up postfix/sendmail running DNS servers. The first stepping stone for me was running a hypervisor so I could build the rest of the things in there.

vlan
k8 cluster.
hpc cluster simulation
GPU cluster simulation
proxmox-/vmware install and management.
building general networking and solving mid level networking issues.

Trying to setup Nextcloud calling on docker 🥹

I have multiple things I tested and learned.

Firstly an opnSense firewall.

An Active Directory (aka setting up a Domain Controller with DNS etc) with a test client, DHCP failover (active passive)

When you have an AD (=Active Directory) you should try to set up an Exchange server, making mail flow rules etc. maybe a cluster

Docker

Reverse Proxy

And last but not least setting up Vlans -> I have a basic understanding and know how it works (and should be set up) but sadly haven’t actually configured it here at home

And virtualizing things and get some hands-on experience with VMware/Hyper-V/Proxmox/QEMU etc.

That are the things I have learned and improved my skills with at home -> At work we have no opnSense firewalls, but for learning setting up pfSense, opnSense or using an old firewall (regardless of the manufacturer) helps understanding access rules, NAT PAT etc.

Absolutely nothing has been as helpful in understanding how the internet works, as setting up and actually using BGP. An asn and a /40 for ipv6 can be had for almost nothing as a one time fee if you go through a LIR. Ipv4 is very expensive to buy but renting a /24 can be had for around $100 a month. And then you’re ready to start peering over tunnels or you can get VPSes that support it or ask your ISP (usually only on higher end business connections).

Truenas/Linux Proxmox/Virtualization Docker/Containerization/Portainer Traefik/Reverse Proxy/SSL Certificates PiHole/DNS

I’m going into my 2nd year self-hosting and home-labbing. i learned all of these skills from watching TechnoTim, DBTech, Network Chuck, Raid Owl, Christian Lempa, Level1Techs, Learn Linux TV, Awesome Open Source, Craft Computing, and Jeff Gerling. These guys are awesome i highly recommend them.

Setting up a small website hosted locally helped me understand the whole stack so much better. Roles / permissions / firewall rules / ports/ webservers / appservers / devops / daemons / docker / DNS and a bunch more

Oh…wow. That’s quite the loaded question. How much time do we have? ::checks watch::

The short answer is that almost every technical skill I’ve learned or improved (and some non-technical ones like public speaking as well) has been a result of my home lab. I just needed the right push/motivation/use case to dive into it.

The first iteration of my home lab started 20 years ago while I was in college. I started my lab because I wanted more hands on experience, and my curiosity pushed me forward from there.

So…it really depends on what skills you want to develop and where you want to start your career. IT is a very large area.

The best thing you can do is find problems you have and use your lab to design and implement a solution.

In general, I would say the following:

1. Troubleshooting- Build things in your lab just to break them. Learn how to figure out what you broke and how to solve the problem.
2. Networking - Build a network. Understand how applications and services talk to each other. Learn a little about TCP/IP and basic routing. It doesn’t need to be complex (unless you want to go for your CCIE)
3. Virtualization - Build out a small virtual environment. Use it to run a few applications or services for personal use. This is also good because you can put multiple services on the same piece of hardware.
4. Share what you’re doing - A big part of IT is communications skills. Once you start doing something interesting, share it. Blog. Find user groups for the technology you’re interested in and talk about how you use your lab to learn it. Good communication skills will get you further than good technical skills.

Setting up a full k8s cluster (vanilla k8s, not k3s etc.) and running most of my self-hosted apps in that cluster caused me a lot of headaches but also got me an immense amount of knowledge and experience.

A robust PKI implementation.

my video game bot farm gave me desire and the need to learn… 1.programming. 2.database administration, 100s of bots need a database. 3.advanced home server deployments and virtualization, 100s of bots need hardware. 4. logging, you cant observe 100s of bots you need to log their activity and establish and observe metrics. etc… I could keep going but after this I started my career as a mainframe programmer, because I had like 70ish percent of the skills I needed.

Setting up exchange server cluster with backups, OWA webmail behind reverse proxy doing IPS+SSO+ MFA, setting up DKIM, DMARC and SPF for this server / testdomain.

Windows PKI using offline and issuing CA. Using these certificates for 802.1x auth.

Hardening Windows Active Directory, setting up LAPS, enforcing TLS where possible, restricting service accounts etc.

Using Azure AD for SAML SSO to where possible. Using JIT or SCIM prorvisioning for accounts. Access roles from groups etc.

Setting up Intune managed workstations with device complience policies and using these policies in conditional access policies.

So yeah mostly Windows stuff.

setting up a pfSense router is cool.

you can use docker to run some local services and give them their own domain names with pfsense

if you want to progress further, you can use traefik to give docker/kubernetes services hostnames and get a cloudflare certificate to enable https on everything

Running my own vmware server

Configuring guest network

Multiple vlans

Configuring tagging on switches for said vlans

Installing Linux on a VM and taking the plunge to learn it.