Building a Home Server: The Budget Networking Gear Guide

Some links in this post are affiliate links. I only recommend products I personally use or have thoroughly researched.

When I first set up my homelab, I spent hundreds of hours researching server hardware, comparing TrueNAS vs Proxmox, and planning storage arrays. Then I connected everything with a $3 Ethernet cable I found in a drawer and plugged it into the ISP-provided router. The server was great. The network was the bottleneck holding everything back.

Networking gear isn’t exciting. Nobody posts their Ethernet cables on Reddit. But after rebuilding my home network from scratch, I can tell you that reliable, well-organized networking is the foundation that makes everything else in your homelab actually work. Here’s the budget gear that got me there.

Start With the Cables: Cat 6 Is the Sweet Spot

Cat 5e technically supports gigabit, but Cat 6 gives you better shielding, less crosstalk, and headroom for 10GbE over short runs if you ever upgrade your switch. Cat 8 is overkill for a homelab unless you’re running cables through an electrically noisy environment (next to power lines, fluorescent ballasts, etc.).

I picked up the Amazon Basics Cat 6 Ethernet Cable 5-Pack when I was wiring up my rack. Getting a multi-pack in different lengths saved me from having 10 feet of slack coiled behind my NAS when I only needed 3 feet.

After plugging everything in, the first thing I do is verify the link speed. You’d be surprised how often a bad crimp or a kinked cable silently drops you to 100Mbps:

# Check link speed on Linux
ethtool eth0 | grep Speed
# Expected: Speed: 1000Mb/s

# On TrueNAS, check via the shell
ifconfig igb0 | grep media
# Or use the Web UI: Network > Interfaces

# Quick bandwidth test between two machines
# On the server:
iperf3 -s
# On the client:
iperf3 -c 192.168.1.100
# You should see ~940 Mbps for gigabit

If iperf3 shows anything significantly below 900 Mbps on a gigabit link, swap the cable before troubleshooting anything else. I wasted two hours debugging “slow NFS transfers” that turned out to be a cable that had been pinched under a desk leg.

RJ45 Couplers: The Joint You Didn’t Know You Needed

My server rack is in the basement. My office is on the second floor. The single longest Ethernet run in my house is about 80 feet. I didn’t have an 80-foot cable, but I had two 50-foot cables. The Amazon Basics RJ45 Coupler joins them together with no measurable signal loss at gigabit speeds.

I also use couplers as a way to create modular cable runs. Instead of running one long permanent cable through the wall, I run a cable from the patch panel to a coupler at the wall plate, then a short patch cable from the coupler to the device. When I need to swap a device or move things around, I only replace the short patch cable.

One caveat: don’t chain multiple couplers. Each junction is a potential point of failure, and while one coupler is fine, daisy-chaining three of them is asking for intermittent connectivity issues that will drive you crazy during a late-night Docker deployment.

The 8-Port Gigabit Switch: Your Homelab’s Traffic Cop

If you’re running more than two devices on your homelab network, you need a dedicated switch. Your ISP router’s built-in switch ports are fine for casual use, but they’re typically limited to 4 ports and share bandwidth with the router’s other functions (NAT, DHCP, firewall, Wi-Fi).

The Amazon Basics 8-Port Gigabit Switch is unmanaged, which means zero configuration — plug it in and it works. For most homelabs, unmanaged is the right call. You get dedicated gigabit bandwidth between devices without worrying about VLAN configs or spanning tree.

My current setup has seven devices on this switch:

# My homelab network map
# Port 1: TrueNAS server (192.168.0.62) - NAS + Docker host
# Port 2: Proxmox node (192.168.0.70) - VMs
# Port 3: Raspberry Pi (192.168.0.80) - Pi-hole DNS
# Port 4: Desktop workstation
# Port 5: Uplink to router
# Port 6: IP camera NVR
# Port 7: Spare (for testing)
# Port 8: Spare

# Quick network scan to see what's alive
nmap -sn 192.168.0.0/24

# Or the faster way with just arp
arp -a | grep -v incomplete

One thing I appreciate about this switch: it’s fanless and silent. My rack sits in the same room where I sometimes work, and I can’t hear the switch at all. The power draw is around 5 watts, which is negligible on your electric bill even running 24/7.

Cable Management: Because Spaghetti Networking Causes Real Problems

This one took me too long to learn. A messy cable situation isn’t just ugly — it makes troubleshooting harder, restricts airflow around your equipment, and increases the chance of accidentally unplugging something when you’re reaching behind the rack.

The Amazon Basics Cable Management Sleeve bundles multiple cables into a single, clean run. I use them for the power cables and Ethernet runs going from my rack to the wall. The split-tube design means you can add or remove cables without disconnecting everything — a small detail that matters a lot when your NAS is serving files 24/7 and you don’t want downtime just to route a new cable.

My cable management philosophy is simple: if you can’t trace a cable from end to end in under 10 seconds, it needs to be reorganized. Label both ends of every cable (a label maker is worth its weight in gold), and group cables by function — power in one sleeve, data in another.

# Generate labels for your cables with a simple script
#!/bin/bash
# cable_labels.sh - Print labels for your homelab cables
devices=("TrueNAS" "Proxmox" "Pi-hole" "Desktop" "Router-Uplink" "NVR")
for i in "${!devices[@]}"; do
  port=$((i + 1))
  echo "Port $port -> ${devices[$i]} | $(date +%Y-%m-%d)"
done
# Pipe to your label printer or just print and tape them on

Surge Protection: Insurance for Your Entire Lab

I live in an area with frequent thunderstorms. After a power surge killed a Raspberry Pi and corrupted an SSD (on the same day, naturally), I stopped messing around with cheap power strips.

The Amazon Basics Surge Protector Power Strip has enough outlets for my rack equipment and provides actual surge protection — not just a glorified extension cord. It also has a flat plug, which matters more than you’d think when your outlet is behind a rack that sits close to the wall.

For a proper homelab power setup, I recommend this hierarchy:

• Tier 1 (critical): UPS → Surge Protector → TrueNAS, switch, router
• Tier 2 (important): Surge Protector → Proxmox nodes, secondary storage
• Tier 3 (nice to have): Regular power strip → monitors, desk accessories

The surge protector sits between the UPS and the devices on Tier 1, giving me two layers of protection. On the TrueNAS side, I also monitor power events:

# If you have a UPS connected via USB to TrueNAS
# Check UPS status
upsc ups@localhost

# Set up email alerts for power events in TrueNAS
# Web UI: System > Alert Services
# Configure SMTP and enable "UPS" alert category

# On Linux with NUT installed
upsmon -D  # debug mode to verify communication

The Complete Budget Network Build

Here’s the full shopping list:

• Cat 6 Ethernet 5-Pack — ~$14
• RJ45 Couplers — ~$7
• 8-Port Gigabit Switch — ~$18
• Cable Management Sleeves — ~$10
• Surge Protector Power Strip — ~$15

Total: Under $65 for a properly wired, organized, and protected homelab network. The switch alone was probably the single best upgrade I made — going from a 4-port ISP router to a dedicated 8-port switch eliminated the random latency spikes I was seeing during large NFS transfers.

What Comes Next

This setup handles gigabit networking reliably. When you’re ready to level up, the typical homelab upgrade path is:

1. Managed switch — VLANs to isolate IoT devices, guest traffic, and lab experiments
2. pfSense/OPNsense router — proper firewall rules, VPN, traffic shaping
3. 10GbE — for high-throughput workloads between NAS and workstation

But start with the fundamentals. Good cables, a solid switch, and proper cable management will solve 90% of the networking frustrations in a typical homelab. Get those right first, then invest in the advanced stuff.

---

Affiliate Disclosure: Some links in this post are affiliate links, which means I may earn a small commission if you make a purchase through them — at no extra cost to you. I only recommend products I personally use or have thoroughly researched. These commissions help support the blog and keep the content free.