F5F Stay Refreshed Hardware Desktop Getting Started with My First Home Server Project Need some guidance? Here’s what you should consider.

Getting Started with My First Home Server Project Need some guidance? Here’s what you should consider.

Getting Started with My First Home Server Project Need some guidance? Here’s what you should consider.

G
GASA30
Junior Member
Find
36
12-05-2023, 12:47 AM
#1
Hello everyone, in the past 18 months I've been focusing on building an IT career. I earned my Net+ and A+, completed CCNA studies, and finished a bachelor's degree in MIS. My current setup is limited to a single laptop that only supports one virtual machine at a time. My aim is to upgrade to something like a PowerEdge 730, set up a network model, and practice using different components alongside my Cisco Packet Tracer work. This includes Windows Server with Active Directory, group policies, automation, etc. I'm also running Red Hat Linux for various tasks such as an SSH server, a Linux client for SIEM (like graylog), and other tools. I've attached a network diagram outlining my planned configuration. Everything beyond the server will be VMs, possibly with containers later. My private network is set to 10.0.0.0/24 and completely separate from my home network. Would this arrangement be correct? Or should I adjust anything? From what I've learned, I prefer avoiding PCI passthrough. Instead, I'll use Promox for NIC1, create VMBR1 connected to the server's NIC2 for the WAN side of PF-Sense, and set VMRR2 as a VNIC for the LAN side of PF-Sense and the other VMs. Could this configuration work without causing connectivity problems between the virtual machines and clients? Thanks!
Reply
Reply
G
GASA30
12-05-2023, 12:47 AM #1

Hello everyone, in the past 18 months I've been focusing on building an IT career. I earned my Net+ and A+, completed CCNA studies, and finished a bachelor's degree in MIS. My current setup is limited to a single laptop that only supports one virtual machine at a time. My aim is to upgrade to something like a PowerEdge 730, set up a network model, and practice using different components alongside my Cisco Packet Tracer work. This includes Windows Server with Active Directory, group policies, automation, etc. I'm also running Red Hat Linux for various tasks such as an SSH server, a Linux client for SIEM (like graylog), and other tools. I've attached a network diagram outlining my planned configuration. Everything beyond the server will be VMs, possibly with containers later. My private network is set to 10.0.0.0/24 and completely separate from my home network. Would this arrangement be correct? Or should I adjust anything? From what I've learned, I prefer avoiding PCI passthrough. Instead, I'll use Promox for NIC1, create VMBR1 connected to the server's NIC2 for the WAN side of PF-Sense, and set VMRR2 as a VNIC for the LAN side of PF-Sense and the other VMs. Could this configuration work without causing connectivity problems between the virtual machines and clients? Thanks!

Reply
Reply
R
RepoSnipez
Member
Find
128
12-06-2023, 05:20 AM
#2
I've been running this role for a while now. Your configuration seems quite limited in scope and heavily reliant on software. The main adjustment I'd suggest is removing the switch and connecting the cable directly to the router—unless you're managing more than eight devices, which isn't common in 2025 outside specialized environments. If your goal is just to explore and test software, avoid brands like HP or DELL, and steer clear of rackmount solutions. Opt for a standard dual-socket pedestal from Supermicro or IBM, and add a few Lenovo M92 and HP-8300 AIO terminals for variety.

When I started working with servers, I focused on consolidating resources and prioritizing long-term reliability after years of dealing with outdated components and formats. The true value of a well-run server lies not in the software you install, but in mastering workload aggregation and NUMA optimization.
Reply
Reply
R
RepoSnipez
12-06-2023, 05:20 AM #2

I've been running this role for a while now. Your configuration seems quite limited in scope and heavily reliant on software. The main adjustment I'd suggest is removing the switch and connecting the cable directly to the router—unless you're managing more than eight devices, which isn't common in 2025 outside specialized environments. If your goal is just to explore and test software, avoid brands like HP or DELL, and steer clear of rackmount solutions. Opt for a standard dual-socket pedestal from Supermicro or IBM, and add a few Lenovo M92 and HP-8300 AIO terminals for variety.

When I started working with servers, I focused on consolidating resources and prioritizing long-term reliability after years of dealing with outdated components and formats. The true value of a well-run server lies not in the software you install, but in mastering workload aggregation and NUMA optimization.

Reply
Reply