bunny-lab/docs
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
Files
947abc47ecd28dfe40c54803a627b90ecf1c23d4
docs/reference/Lab Map/Homelab Server Inventory.md
T
nicole 947abc47ec
Automatic Documentation Deployment / Sync Docs to https://kb.bunny-lab.io (push) Successful in 8s
Details
Update reference/Lab Map/Homelab Server Inventory.md
2026-09-05 14:21:43 -06:00

192 lines
32 KiB
Markdown
Raw Blame History

---
tags:
- iptables
- Networking
---
---
title: Homelab IP Allocation
description: Canonical host, IP address, DNS, and workload allocation map for the Bunny Lab environment.
icon: material/ip-network
-------------------------
# Homelab IP Allocation
This page is the canonical allocation map for statically assigned infrastructure, servers, virtual machines, appliances, and reserved services.
<div class="grid cards" markdown>
* :material-check-circle:{ .lg .middle } **49 Active**
---
Addresses currently represented by active host entries.
* :material-bookmark-outline:{ .lg .middle } **22 Reserved**
---
Addresses assigned to a workload or planned service, but not currently represented by an active host entry.
* :material-checkbox-blank-circle-outline:{ .lg .middle } **8 Available**
---
Explicitly unallocated addresses available for reuse.
* :material-server-network:{ .lg .middle } **1 Deep Node**
---
Additional host allocation outside of the primary `192.168.3.0/24` server network.
</div>
!!! info "Allocation state"
```
| State | Meaning |
|---|---|
| :material-check-circle: **Active** | Host was present as an uncommented entry in the previous AWX / Ansible inventory. |
| :material-bookmark-outline: **Reserved** | An IP has an assigned workload or intended use, but the corresponding AWX entry was commented or absent. |
| :material-checkbox-blank-circle-outline: **Available** | Address was explicitly identified as not currently in use. |
```
!!! warning "Source data requiring reconciliation"
```
`deeplab-win11` was associated with allocation marker `#30`, but its descriptive entry listed `192.168.3.35`. This table treats it as `192.168.3.30`.
`deeplab-win10` was associated with allocation marker `#36`, but its descriptive entry also listed `192.168.3.35`. This table treats it as `192.168.3.36`.
`cluster-laptop-node-01` is assigned to both `192.168.3.69` and `192.168.3.72`. The `.72` hostname should be reviewed.
```
!!! note "Documentation links"
```
Placeholder `example.com` documentation links from the previous inventory have been omitted. Existing external documentation and internal relative runbook links have been retained.
```
---
## Deep Nodes
| IP address | Host | State |
| ----------- | ----------- | ---------------------------------- |
| `10.0.0.20` | `deep-node` | :material-check-circle: **Active** |
---
## Primary Server Allocation
### `192.168.3.1` — `192.168.3.75`
| IP address | Host / DNS | Workload / purpose | State | Documentation |
| -------------- | ------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------- | ------------------------------------------------------------------------------------------------------------- |
| `192.168.3.1` | `lab-pfsense-01` | pfSense Firewall | :material-check-circle: **Active** | [Docs](https://www.pfsense.org/getting-started/) |
| `192.168.3.2` | `lab-mini-pc` | 3.7 GHz High-Performance Mini-PC | :material-check-circle: **Active** | — |
| `192.168.3.3` | `lab-storage-01` | TrueNAS CORE Server | :material-check-circle: **Active** | [Docs](https://www.truenas.com/truenas-core/) |
| `192.168.3.4` | `cluster-node-01` | Proxmox VE Virtualization Node | :material-check-circle: **Active** | — |
| `192.168.3.5` | `cluster-node-02` | Proxmox VE Virtualization Node | :material-check-circle: **Active** | — |
| `192.168.3.6` | `lab-games-04`<br>`lab-games-04.bunny-lab.io` | Satisfactory Dedicated Server | :material-check-circle: **Active** | [Docs](https://satisfactory.wiki.gg/wiki/Dedicated_servers) |
| `192.168.3.7` | `lab-photos-01`<br>`lab-photos-01.bunny-lab.io` | Immich Server | :material-check-circle: **Active** | [Docs](https://immich.app/docs/install/docker-compose/) |
| `192.168.3.8` | `kb-bunny-lab-io`<br>`kb.bunny-lab.io` | Zensical Documentation Server | :material-check-circle: **Active** | [Docs](https://hub.docker.com/r/zensical/zensical) |
| `192.168.3.9` | `lab-fog-01` | FOG Project | :material-check-circle: **Active** | [Docs](https://fogproject.org/) |
| `192.168.3.10` | `lab-ansible-01`<br>`lab-ansible-01.bunny-lab.io` | Ansible AWX *(legacy inventory / automation)* | :material-check-circle: **Active** | [Docs](../../deployments/automation/AWX/AWX Operator.md) |
| `192.168.3.11` | `lab-games-02`<br>`lab-games-02.bunny-lab.io` | Minecraft — All The Mods 9 | :material-check-circle: **Active** | [Docs](https://www.curseforge.com/minecraft/modpacks/all-the-mods-9) |
| `192.168.3.12` | `lab-dhcp-01`<br>`lab-dhcp-01.bunny-lab.io` | Windows DHCP Server | :material-check-circle: **Active** | — |
| `192.168.3.13` | `lab-dhcp-02`<br>`lab-dhcp-02.bunny-lab.io` | Windows DHCP Server | :material-check-circle: **Active** | — |
| `192.168.3.14` | `lab-games-03`<br>`lab-games-03.bunny-lab.io` | Minecraft — All The Mods 10 | :material-check-circle: **Active** | [Docs](https://www.curseforge.com/minecraft/modpacks/all-the-mods-10) |
| `192.168.3.15` | `lab-mail-gw-01` | Proxmox Mail Gateway | :material-check-circle: **Active** | — |
| `192.168.3.16` | — | *Unallocated* | :material-checkbox-blank-circle-outline: Available | — |
| `192.168.3.17` | `lab-traefik-01`<br>`traefik.bunny-lab.io` | Traefik Reverse Proxy | :material-check-circle: **Active** | — |
| `192.168.3.18` | — | Keycloak Server | :material-bookmark-outline: **Reserved** | [Docs](../../deployments/Identity and Certificates/Keycloak/Deploy Keycloak.md) |
| `192.168.3.19` | `container-node-01`<br>`container-node-01.bunny-lab.io` | Docker Container Environment (Portainer) | :material-bookmark-outline: **Reserved** | [Docs](../../deployments/Containers/Docker/Deploy Portainer.md) |
| `192.168.3.20` | — | PrivacyIDEA<br><small>Separate allocation from `deep-node` at `10.0.0.20`.</small> | :material-bookmark-outline: **Reserved** | [Docs](../../deployments/Identity and Certificates/Privacyidea.md) |
| `192.168.3.21` | `lab-puppet-01`<br>`lab-puppet-01.bunny-lab.io` | Puppet Server | :material-check-circle: **Active** | [Docs](../../deployments/automation/Puppet/Puppet.md) |
| `192.168.3.22` | — | *Unallocated* | :material-checkbox-blank-circle-outline: Available | — |
| `192.168.3.23` | `usagi-cluster`<br>`usagi-cluster.bunny-lab.io` | Hyper-V Failover Cluster | :material-check-circle: **Active** | [Docs](../../deployments/Virtualization and Storage/Hyper-V/Failover Cluster/Deploy Failover Cluster Node.md) |
| `192.168.3.24` | `lab-pool-01`<br>`lab-pool-01.bunny-lab.io` | TrueNAS SCALE | :material-check-circle: **Active** | [Docs](https://www.truenas.com/truenas-scale/) |
| `192.168.3.25` | `lab-dc-01`<br>`lab-dc-01.bunny-lab.io` | Primary Domain Controller | :material-check-circle: **Active** | — |
| `192.168.3.26` | `lab-dc-03`<br>`lab-dc-03.bunny-lab.io` | Secondary Domain Controller | :material-check-circle: **Active** | — |
| `192.168.3.27` | `lab-camera-01`<br>`lab-camera-01.bunny-lab.io` | Blue Iris Surveillance | :material-check-circle: **Active** | [Docs](https://blueirissoftware.com/) |
| `192.168.3.28` | `lab-games-01`<br>`lab-games-01.bunny-lab.io` | ARK: Survival Ascended Server | :material-check-circle: **Active** | [Docs](../../deployments/Applications/Gaming and Media/Ark Survival Ascended.md) |
| `192.168.3.29` | `lab-cloud-01`<br>`lab-cloud-01.bunny-lab.io` | Nextcloud AIO | :material-check-circle: **Active** | [Docs](../../deployments/Applications/Files and Collaboration/Nextcloud AIO.md) |
| `192.168.3.30` | `deeplab-win11`<br>`deeplab-win11.dev-testing.lab` | Dev-Testing Windows 11 Lab Environment<br>:material-alert-circle-outline: Source narrative says `.35`; allocation marker says `#30`. | :material-check-circle: **Active** | — |
| `192.168.3.31` | `lab-dt-02`<br>`lab-dt-02.bunny-lab.io` | Windows 11 Work VM | :material-check-circle: **Active** | — |
| `192.168.3.32` | — | Matrix Synapse Homeserver | :material-bookmark-outline: **Reserved** | [Docs](https://github.com/matrix-org/synapse) |
| `192.168.3.33` | `cluster-node-03` | Proxmox VE Virtualization Node | :material-check-circle: **Active** | — |
| `192.168.3.34` | `lab-draas-01-ilo` | LAB-DRAAS-01 iLO / IPMI Interface | :material-check-circle: **Active** | — |
| `192.168.3.35` | `deeplab-dc`<br>`deeplab-dc-01.dev-testing.lab` | Dev-Testing Domain Controller | :material-check-circle: **Active** | — |
| `192.168.3.36` | `deeplab-win10`<br>`deeplab-win10.dev-testing.lab` | Dev-Testing Windows 10 Lab Environment<br>:material-alert-circle-outline: Source narrative says `.35`; allocation marker says `#36`. | :material-check-circle: **Active** | — |
| `192.168.3.37` | — | Security Onion | :material-bookmark-outline: **Reserved** | [Docs](https://docs.securityonion.net/en/2.4/installation.html) |
| `192.168.3.38` | — | Wazuh SIEM Security VM | :material-bookmark-outline: **Reserved** | [Docs](https://documentation.wazuh.com/current/quickstart.html) |
| `192.168.3.39` | — | Rancher Harvester Hyper-Converged Infrastructure | :material-bookmark-outline: **Reserved** | — |
| `192.168.3.40` | — | Rancher Harvester HCI — VIP Management Interface | :material-bookmark-outline: **Reserved** | — |
| `192.168.3.41` | — | Pterodactyl Dedicated Game Server Hosting Dashboard | :material-bookmark-outline: **Reserved** | — |
| `192.168.3.42` | — | NGINX Package Caching Server | :material-bookmark-outline: **Reserved** | — |
| `192.168.3.43` | — | *Unallocated* | :material-checkbox-blank-circle-outline: Available | — |
| `192.168.3.44` | — | *Unallocated* | :material-checkbox-blank-circle-outline: Available | — |
| `192.168.3.45` | — | *Unallocated* | :material-checkbox-blank-circle-outline: Available | — |
| `192.168.3.46` | — | *Unallocated* | :material-checkbox-blank-circle-outline: Available | — |
| `192.168.3.47` | — | *Unallocated* | :material-checkbox-blank-circle-outline: Available | — |
| `192.168.3.48` | `lab-docker-02` | Portainer Docker Node | :material-check-circle: **Active** | — |
| `192.168.3.49` | `lab-fps-01` | Windows File Server | :material-check-circle: **Active** | — |
| `192.168.3.50` | — | Flyff VM 01 | :material-bookmark-outline: **Reserved** | — |
| `192.168.3.51` | — | Semaphore UI Automation Server | :material-bookmark-outline: **Reserved** | — |
| `192.168.3.52` | — | Headless Laptop Server 01 | :material-bookmark-outline: **Reserved** | — |
| `192.168.3.53` | — | Headless Laptop Server 02 | :material-bookmark-outline: **Reserved** | — |
| `192.168.3.54` | `veeam-draas-01` | Veeam Backup & Replication Server | :material-check-circle: **Active** | — |
| `192.168.3.55` | — | Veeam Backup Worker | :material-bookmark-outline: **Reserved** | — |
| `192.168.3.56` | — | Veeam Backup Worker | :material-bookmark-outline: **Reserved** | — |
| `192.168.3.57` | — | Veeam Backup Worker | :material-bookmark-outline: **Reserved** | — |
| `192.168.3.58` | `lab-photos-02` | Immich Server | :material-check-circle: **Active** | [Docs](https://immich.app/docs/install/docker-compose/) |
| `192.168.3.59` | `lab-ca-01` | Active Directory Root Certificate Services VM | :material-check-circle: **Active** | — |
| `192.168.3.60` | `lab-ca-02` | Active Directory Intermediate Certificate Services VM | :material-check-circle: **Active** | — |
| `192.168.3.61` | `lab-mail-02` | Mailcow Email Server | :material-check-circle: **Active** | — |
| `192.168.3.62` | — | *Unallocated* | :material-checkbox-blank-circle-outline: Available | — |
| `192.168.3.63` | — | Proxmox Datacenter Manager | :material-bookmark-outline: **Reserved** | — |
| `192.168.3.64` | `lab-iso-01` | h5ai File Sharing Server | :material-check-circle: **Active** | — |
| `192.168.3.65` | — | NetBird VPN Server | :material-bookmark-outline: **Reserved** | — |
| `192.168.3.66` | — | Kasm Workspaces VM | :material-bookmark-outline: **Reserved** | — |
| `192.168.3.67` | `lab-fps-02` | Windows File Server | :material-check-circle: **Active** | — |
| `192.168.3.68` | `lab-pbs-01` | Proxmox Backup Server | :material-check-circle: **Active** | — |
| `192.168.3.69` | `cluster-laptop-node-01` | Proxmox VE Headless Laptop Virtualization Node | :material-check-circle: **Active** | — |
| `192.168.3.70` | `cluster-laptop-node-02` | Proxmox VE Headless Laptop Virtualization Node | :material-check-circle: **Active** | — |
| `192.168.3.71` | `cluster-laptop-node-03` | Proxmox VE Headless Laptop Virtualization Node | :material-check-circle: **Active** | — |
| `192.168.3.72` | `cluster-laptop-node-01` | Proxmox VE Headless Laptop Virtualization Node<br>:material-alert-circle-outline: Hostname duplicates `.69`. | :material-check-circle: **Active** | — |
| `192.168.3.73` | `cluster-laptop-node-05` | Proxmox VE Headless Laptop Virtualization Node | :material-check-circle: **Active** | — |
| `192.168.3.74` | — | Rancher Harvester Node | :material-bookmark-outline: **Reserved** | — |
| `192.168.3.75` | — | Rancher Harvester Cluster VIP | :material-bookmark-outline: **Reserved** | — |
---
## High Infrastructure Addresses
These addresses are intentionally allocated near the top of the `/24` rather than in the primary server range.
| IP address | Host | Workload / purpose | State |
| --------------- | -------------------- | ----------------------------------------------- | ---------------------------------- |
| `192.168.3.251` | `borealis-engine-02` | Borealis Engine Node 02 | :material-check-circle: **Active** |
| `192.168.3.252` | `borealis-engine-01` | Borealis Engine Node 01 | :material-check-circle: **Active** |
| `192.168.3.253` | `deeplab-node-02` | Fedora Workstation 42 VM | :material-check-circle: **Active** |
| `192.168.3.254` | `core-switch-01` | Core Infrastructure Switch 01 — Zyxel GS1920-48 | :material-check-circle: **Active** |
---
## Addressing Conventions
!!! tip "Maintaining this page"
```
Treat **IP address** and **intended workload** as the authoritative allocation.
A host does not need to be online to retain an allocation. Use **Reserved** when an address remains assigned to a planned, powered-off, or temporarily decommissioned workload.
Only mark an address **Available** when the previous allocation has intentionally been released.
Prefer recording the canonical hostname and FQDN independently of whether Ansible, AWX, DNS, DHCP, or another management system currently consumes the record.
```
Reference in New Issue View Git Blame Copy Permalink