# Homelab networking for Windows: 2.5GbE, switches and VLANs

> What actually bottlenecks a Windows lab network, when 2.5GbE is worth it, and the switch/VLAN basics that make remote management safe.

**Tested on**

- Build: 26300.9457 / 26100.33650
- Edition: Pro (26H2) / Server
- Architecture: x64
- Evidence: E1
- Verified: 2026-10-29

## The short answer

In a Windows homelab, the bottleneck is almost never the switch:

1. **Disk IOPS** on the host — VM boot storms are storage-bound.
2. **RAM** on the host — swapping makes everything look slow.
3. **The client link** — a laptop on Wi-Fi is the slowest thing in the path.
4. **The switch** — 1GbE is usually fine; 2.5GbE helps VM-to-NAS transfers.

Buy a switch for **port count and VLAN support**, not for headline speed.

## When 2.5GbE is worth it

| Use case | Benefit |
|---|---|
| VM to NAS backups | large sequential copies finish faster |
| Moving ISOs/images between hosts | noticeable above a few GB |
| Multiple VMs on one host | aggregate, not per-VM |
| Internet browsing | none |

1GbE moves ~110MB/s; 2.5GbE moves ~280MB/s. If your NAS or SSD cannot sustain that, the upgrade buys nothing.

Windows side: a 2.5GbE adapter needs working drivers — Intel i225/i226 are the safer choice; some Realtek 8125 revisions have known issues with offloads and power saving.

```powershell
Get-NetAdapter | Select-Object Name,Status,LinkSpeed,DriverVersion
Get-NetAdapterAdvancedProperty -Name 'Ethernet' | Select-Object DisplayName,DisplayValue
```

If `LinkSpeed` shows 1Gbps on a 2.5G port, check the cable (Cat5e is usually fine for short runs), the switch port, and the adapter's "speed & duplex" setting.

## VLANs: the part that makes remote management safe

A homelab needs at least two logical networks:

- **LAN** — your normal devices;
- **MGMT** — Proxmox UI, iDRAC/iLO, switch management, NAS admin.

Why it matters: a compromised VM should not be able to reach the BMC. VLANs (or a separate physical switch) are the cheap way to enforce that.

On Windows, a VM's VLAN is usually set on the **virtual NIC** in the hypervisor, not inside Windows. Inside the guest you just see a normal adapter.

## Common mistakes

| Mistake | Consequence |
|---|---|
| Management interface on the LAN with default password | the classic homelab compromise |
| Wi-Fi for the hypervisor host | VM traffic shares a fragile link |
| Jumbo frames on one side only | mysterious slow transfers and failed pings |
| Two DHCP servers on one L2 segment | random IP changes, broken DNS |
| USB Ethernet on the host | driver resets under load |

> **Caution: Do not put the BMC on your main VLAN**
>
> iDRAC/iLO/IPMI are unpatched more often than anything else in a homelab. Put them on a management VLAN with no route to the internet, and change the default credentials before first boot.

## A sane topology for a small lab

```text
ISP router
  └─ switch (managed, 8–16 ports)
       ├─ port 1  : hypervisor host (2.5GbE)
       ├─ port 2  : NAS (2.5GbE)
       ├─ port 3  : desktop (2.5GbE)
       ├─ port 4  : BMC / management (VLAN 99)
       └─ port 5+ : other devices, Wi-Fi AP

VLAN 10  LAN     192.168.10.0/24
VLAN 99  MGMT    192.168.99.0/24  (no gateway to internet)
```

Keep the management VLAN without a default gateway if you can — it makes accidental exposure much harder.

## Verify from Windows

```powershell
Get-NetAdapter | Select-Object Name,Status,LinkSpeed
Get-NetIPConfiguration | Select-Object InterfaceAlias,IPv4Address,IPv4DefaultGateway
Test-NetConnection 192.168.99.10 -Port 443   # BMC reachable from the right place only
```

If a VM can reach the BMC, your segmentation is not working — check the virtual switch and the port VLAN, not the guest firewall.

## Related

- [Mini PC as a PVE host](https://windows.homes/en/hardware/homelab/mini-pc-host/)
- [Server hardware and Windows Server](https://windows.homes/en/hardware/homelab/server-hardware/)
- [USB4 and docks](https://windows.homes/en/hardware/display/usb4-dock/)

## Lab boundary

E1. Link speeds and VLAN behaviour are network/vendor facts; Microsoft documents the Windows-side adapter and server requirements. The lab runs on a flat 1GbE segment, so no 2.5GbE or VLAN throughput was measured.

## Sources

- [Microsoft Learn — Windows Server hardware requirements](https://learn.microsoft.com/en-us/windows-server/get-started/hardware-requirements)
- [Proxmox VE — Windows 11 guest best practices](https://pve.proxmox.com/wiki/Windows_11_guest_best_practices)

---

Source: https://windows.homes/en/hardware/homelab/network-hardware/