Network Configuration
Subnet Design
Primary cluster network:
✔ 10.0.0.0/24
Removed to avoid conflicts:
❌ 192.168.1.0/24 (home network — no DHCP from MAAS)
❌ IPv6 subnet (2a02:...) (disabled entirely)
Rule: MAAS DHCP runs only on the isolated 10.0.0.0/24 network.
MAAS Controller Network Interfaces
ip a
enx00e04c6802b8 → 10.0.0.1/24 (cluster network — USB Ethernet adapter → switch)
enp0s31f6 → dedicated internet uplink (keeps cluster traffic isolated from home network)
wlp0s20f3 → 192.168.1.x (home WiFi — kept separate, not used for cluster)
The controller uses a dedicated Ethernet uplink (enp0s31f6) for internet access rather than the home WiFi, keeping the cluster network fully isolated. MAAS DHCP runs only on enx00e04c6802b8.
DHCP Configuration
✔ DHCP enabled ONLY on 10.0.0.0/24 (managed by MAAS)
✔ DHCP disabled on 192.168.1.0/24 (home router handles it)
✔ IPv6 DHCP disabled
IP Assignment Table
| Host | IP | Assignment |
|---|---|---|
| MAAS Controller | 10.0.0.1 | Static |
| set-hog | 10.0.0.2 | MAAS DHCP |
| fast-skunk | 10.0.0.4 | MAAS DHCP |
| fast-heron | 10.0.0.7 | MAAS DHCP |
| star-kitten | 10.0.0.8 | MAAS DHCP |
Why Disable IPv6?
MAAS has issues selecting the correct subnet when IPv6 is present alongside IPv4. Disabling IPv6 entirely eliminates subnet selection ambiguity and simplifies the provisioning pipeline.
IPv6 is disabled via cloud-init sysctl settings on each node:
net.ipv6.conf.all.disable_ipv6=1
net.ipv6.conf.default.disable_ipv6=1
net.ipv6.conf.lo.disable_ipv6=1