homelab

Current homelab configuration, bugs and other stuff related to it.

Hardware

Device	Function	Drivers
Beelink GTi13 Ultra Intel® Core™ i9-13900HK	Hyper-V host	Driver download
Raspberry Pi 4 Model B	N/A	N/A
Raspberry Pi 3 Model B	N/A	N/A
Raspberry Pi 2	Pihole	N/A
ASUS ZenWifi Pro ET12 Router	Wi-fi and IoS-network	N/A
ASUS RT-AX92U Router	Lab-network	N/A

Virtual machines

Name	Info	Function
LAB - DC01	Windows Server 2025	Domain controller for lab
LAB - WS01	Windows 11 Enterprise	Workstation in lab domain
LAB - Proxy	Ubuntu 24.04 Server	Running Squid proxy and Wireguard for remote access
D4IoTSensor	Virtual appliance for Hyper-V	Runs a trial version of Defender for IoT

Lab design

The general idea of the lab is to test on-premise and hybrid scenarios.

Generic overview

  flowchart LR
    A(Internet)
    C(ASUS ZenWifi Pro ET12)
    D(ASUS RT-AX92U)
    AA[Beelink GTi13]
    A --> C
    C --> D
    D --> AA
    W1((IoT WiFi))
    W2((Lab WiFi))
    C --- W1
    subgraph "Lab"
    D --- W2
    H{Hyper-V}
    AA --- H
    H --- DC01[[DC01]]
    H --- WS01[[WS01]]
    H --- D4IOT[[D4IOT]]
    H --- PROXY[[Squid-proxy]]
    H --- W2
    D4IOT --> W1
    DC01 -.-> PROXY
    PROXY -.-> W2
    WS01 -.-> PROXY
    end

Network

Name	Type	Description	Physical Adapter Link	IP space
Core	Internal	Management network for my Defender for IoT lab	N/A	192.168.0.0/24
VSwitch-Internal-Lab	Internal	Lab network for my Active Directory lab	N/A	10.0.0.0/24
VSwitch-SPAN-Azkaban	External	External network for connecting my Defender for IoT sensor to my IoT network	Wi-Fi	172.16.0.0/24
VSwitch-INET-Cronos	External	Management interface for RDP and proxy server	Ethernet	10.13.*.0/24

I’ll cover a bit more about the VMs and the networking later, but this basically illustrates the way it’s currently set up to work:

  flowchart LR
    NET1[Core]
    NET2["VSwitch-Internal-Lab"]
    NET3["VSwitch-SPAN-Azkaban"]
    NET4["VSwitch-INET-Cronos"]
    MGMT[MGMT Computer]
    LABR[Lab router] --> LABR1["Cronos network"]
    H{Hyper-V}
    H --- DC01[[DC01]]
    H --- WS01[[WS01]]
    H --- D4IOT[[D4IOT]]
    H --- PROXY[[Squid-proxy]]
    LABR1 --> |Ethernet| NET4 
    MGMT --> LABR1
    DC01 --> NET2
    WS01 --> NET2
    NR[Router] --> NR1["Azkaban network"]
    NR1 --> IOT[IoT Devices]
    NR1 --> NET3
    IOT -.-> NET3
    NET2 -.-> |Proxy| PROXY 
    PROXY --> NET4
    D4IOT --> |Management network| NET1
    D4IOT --> |Sensor network| NET3
    NET4 --> |Remote MGMT| H

Configuration and setup

Some details about configuration and setup. Some places I followed guides 1:1 and I will just link directly to those. If I had any issues I might write a separate post on it and link it in just to make sure this page stays a bit lean.

Hyper-V host

Windows Server 2025 installed on the Beelink server.

Downloaded Rufus and Windows Server 2025
Created a bootable USB
Followed installation guidelines

After boot I had a ton of issues getting drivers to install correctly. One major issue was that of the network cards. The Beelink uses the I226 intel cards and this was the major source of most of the issues.

D4IoT Sensor

TBA

Active Directory Lab Domain

Some details about the domain and hosts. These servers are not connected directly to the internet via bridge, they are connected to an internal v-switch that allows them to reach the internet* via the Squid-proxy.

*Microsoft endpoints required fby Defender (endpoint/identity) to send telemetry.

DC01

TBA

WS01

TBA

Squid proxy

Ubuntu 24.04, runs Squid-proxy. This server is connected via a bridged ethernet-adapter to the internet and via an internal v-switch to the servers in the domain.

security automation blog