aly badawy/homelab
all systems operational
// networking · hardware

Physical hardware

Every physical device in the homelab. One router, two managed switches, one NAS, one k3s server, one Proxmox lab machine, one AREDN mesh node. Servers and storage all on VLAN 20 (172.20.20.0/24).

VLAN 20 · Servers UniFi stack Beelink · Proxmox

01 Network gear

DeviceRoleIPVLAN
UniFi Dream Router 7 (UDR7) Router, firewall, DHCP, VLAN trunk. Gateway for all VLANs. 172.20.1.1 Management (1)
UniFi Flex 2.5G Managed switch (8-port + 2 SFP+ trunk). Connected directly to UDR7. Trunks all VLANs to servers. 172.20.1.x Management (1)
UniFi Flex Mini 2.5G Managed switch (5-port). Connected directly to UDR7. Additional VLAN trunk for overflow devices. 172.20.1.x Management (1)
Wireless access point — Personal, IoT, Guest SSIDs on separate VLANs. Management (1)

02 Servers

DeviceRoleIPNotes
UniFi UNAS 4 (NAS) NFS storage for k3s mounts and Longhorn backups. UniFi NAS appliance. 172.20.20.2 Static reserved. NFS exports at /var/nfs/shared.
GMKtec NucBox M8 k3s cluster node (Ubuntu 26.04 bare-metal). Runs all Kubernetes workloads. 172.20.20.3 AMD Ryzen 5 PRO 6650H · 16 GB LPDDR5 · 512 GB SSD · Dual 2.5GbE (Wi-Fi + BT disabled in BIOS). See rebuild guide.
Beelink (Proxmox) Lab hypervisor. Runs private test and development VMs. Not part of the k3s cluster. 172.20.20.10 VMs reserved in the 172.20.20.11–.19 range on VLAN 20.

The Beelink runs Proxmox and is used for private lab and test work independent of the k3s cluster. It sits on VLAN 20 and VMs are bridged onto the same network. VM IPs are reserved in the 172.20.20.11–172.20.20.19 range.

The specific services running on this machine are private and not documented here.

PropertyValue
Hypervisor IP172.20.20.10
VM IP range172.20.20.11 – 172.20.20.19 (reserved)
VLANServers (20) — all VMs on the same Linux bridge

04 AREDN mesh node

An amateur radio emergency data network node connects to the homelab on its own isolated VLANs.

InterfaceVLANIPRole
AREDN-WAN (40) 172.20.40.2 Node's WAN interface — uplink from UDR7.
AREDN node LAN AREDN-LAN-1 (41) 10.6.229.9 Node-managed LAN (AREDN assigns addresses in 10.6.229.8/29).
UDR7 on AREDN LAN AREDN-LAN-1 (41) 10.6.229.10 UDR7 acts as gateway on the AREDN LAN network.
AREDN port wiring. The AREDN node's WAN and LAN interfaces connect on separate switch ports, each tagged to a different VLAN. This keeps mesh traffic isolated from the node's own LAN clients. The local.mesh domain and address ranges are managed by the AREDN firmware — see arednmesh.org for details on the mesh IP schema.
last updated 2026-06-08