Cyber Neural Network: Architectural Overview
“In the seven-layer network model, the hardest layer to troubleshoot is always the eighth: my own clumsy configuration that I haven’t noticed yet.”
This page documents the overall network wiring and logical planning of this “Cyber-Unfinished Building.” To defend against advanced hackers who don’t actually exist on the internet, I used OPNsense, VLANs, and complex static routing rules to build myself a literal labyrinth.
Judging by the results, my network security construction has been extremely successful: Hackers definitely can’t get in, because even I often can’t access my own intranet.
Current Network Health Assessment: Status: Schrödinger's Connectivity Architecture: Hybrid Cloud Frankenstein Protection: Self-Defense (Against Myself)
🕸️ Physical & Logical Topology
Section titled “🕸️ Physical & Logical Topology”Displayed here is the crystallization of countless late-night hair-loss sessions (v4.2). Please note that due to over-engineering, the connections in the diagram may currently be in a state of “superposition collapse” in reality.
🌐 Static IP Asset Table
Section titled “🌐 Static IP Asset Table”“Behind every string of IP addresses hides a tearful history of network unreachability.” > This is the current addressing manifest for all core laboratory equipment. The router is the gatekeeper, PVE is the foundation, and the rest are the “Cyber Slaves” under my command.
| Node | Address | Layer (VLAN/Port) | Status | Role |
|---|---|---|---|---|
| 🖲️ Main Router R6S | 192.168.100.1 | WAN/LAN | 🟡 Sporadic Outages | Traffic egress, home-wide proxy. Schrödinger’s connectivity. |
| 🍎 Mac Mini | 192.168.100.4 | 2.5G Eth | 🟢 Peaceful & Quiet | Productivity office, service development. The most expensive SSH launcher in the house. |
| 🖥️ PVE Host | 192.168.100.50 | 2.5G Eth | 🔴 Howling at Full Load | N100 Virtualization Management. Unplugging results in total family collapse. |
| 🎛️ Core Switch | 192.168.100.220 | MGMT | 💤 Gathering Dust | Layer 2 Cloud Management. Configured once and never opened again. |
| 🛡️ Virtual Gateway OPNsense | 192.168.100.247 | vBridge | 🟢 Interception Freak | Lab entrance. Successfully defended against the whole world, including myself. |
| 💾 TrueNAS Storage | 10.20.10.x | VLAN 10 | 🟢 Data Black Hole | NFS / iSCSI storage sharing. The sound of my wallet crying in the dead of night. |
| ☸️ K3s Master | 10.20.10.10 | VLAN 10 | 🟡 Crazy Swapping | Kubernetes Control Plane. Cannon Swatting Mosquitoes HQ. |
| ☸️ K3s Node 01 | 10.20.10.11 | VLAN 10 | 🚷 Node Offline | Core workload container node. Often deserts the post due to poor “rations.” |
| 🐳 Docker Core Engine | 10.20.30.10 | VLAN 30 | 🟢 Independent & Sane | Pure Docker environment. The ultimate practice ground for “Everything can be Dockerized.” Specifically used to run all sorts of weird containerized apps, ready to be spun up or deleted at will. |
| 🪟 Cyber Desktop Pool (VDI) | 10.20.50.x | VLAN 50 | 💥 Lag-induced Hallucinations | (New) Runs Linux/Win11 desktops. Specifically designed to torture the N100 to death. |
💡 Node Status & Architectural Notes
Section titled “💡 Node Status & Architectural Notes”- 🟢 Peaceful & Quiet / Independent & Sane: Excess performance, zero pressure, or simply the only reliable node actually doing work in the server room.
- 🟡 Sporadic Outages / Crazy Swapping: Barely usable, but hovering on the edge of a health-related collapse.
- 💥 Lag-induced Hallucinations: Mouse lag trails of up to two seconds. A computational disaster caused by extreme misuse of the N100.
- 🔴 Howling at Full Load: CPU fan spinning faster than my heart rate.
- 🚷 Node Offline: Don’t know why, but it just won’t Ping anymore.
- 💤 Gathering Dust: Lights are on, but nobody’s home.
Design Note (Regarding the Independent Docker Engine): Since “Everything can be Dockerized”, I had to set up an exclusive VIP playground for it. While K3s is cool, it’s just too heavy for running lightweight personal services. I specifically established this independent Docker Core Engine in VLAN 30. It breaks away from the complex orchestration of K3s and returns to the most raw and reliable docker-compose. This is the Foreman’s express lane for “day shift building, night shift demolishing”—fast to deploy, fast to destroy, fully embracing the freedom to tinker!