From 11e809914a3bfb7a6cc4eac22b738ec7bf111a3d Mon Sep 17 00:00:00 2001 From: Christopher Lorenzo Date: Sun, 4 Oct 2026 13:50:32 -0400 Subject: [PATCH] Update UniFi network status and restore proof links --- .github/workflows/docs-check.yml | 3 + .gitignore | 2 + AGENTS.md | 4 +- CHANGELOG.md | 11 +++ CURRENT-STATUS.md | 19 ++--- LESSONS-LEARNED.md | 4 ++ README.md | 42 +++++------ diagrams/README.md | 6 +- diagrams/current-topology.md | 71 +++++++------------ .../phase-1-managed-network-cutover/README.md | 32 ++++----- .../diagrams.md | 4 +- .../screenshots.md | 63 ++++++++-------- .../validation.md | 50 ++++++------- docs/phase-2-vlan-segmentation/README.md | 2 +- docs/phase-3-firewall-policy/README.md | 2 +- screenshots/README.md | 4 +- scripts/check-relative-links.py | 30 ++++++++ 17 files changed, 191 insertions(+), 158 deletions(-) create mode 100644 scripts/check-relative-links.py diff --git a/.github/workflows/docs-check.yml b/.github/workflows/docs-check.yml index fb92b86..2345050 100644 --- a/.github/workflows/docs-check.yml +++ b/.github/workflows/docs-check.yml @@ -58,3 +58,6 @@ jobs: fi echo "No empty Markdown files found." + + - name: Check relative Markdown links + run: python3 scripts/check-relative-links.py diff --git a/.gitignore b/.gitignore index 994d82f..983adf4 100644 --- a/.gitignore +++ b/.gitignore @@ -19,6 +19,8 @@ Thumbs.db # Sensitive network exports configs/private/ configs/raw/ +screenshots/raw/ +screenshots/unredacted/ *.ovpn *.conf.private diff --git a/AGENTS.md b/AGENTS.md index 7b4c18d..784de4b 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -9,11 +9,11 @@ Read these first: ## Scope -Project 2 of the home network lab: migration from consumer mesh/router to managed router/switch (ER605 + managed PoE switch), Omada SDN Controller, AP-mode wireless, redundant DNS, Proxmox-hosted services. Builds on `dns` (Project 1). This repo's own scope stops at the managed baseline. VLAN segmentation, firewall policy, and SSID-to-VLAN mapping are the next phase. +Project 2 of the home network lab: the historical ER605/Omada cutover, followed by the 2026-09-27 UniFi UDM Pro and USW-24-PoE equivalent-state refresh. Deco remains in AP mode. Builds on `dns` (Project 1). The LAN is flat; VLAN segmentation, firewall policy, and SSID-to-VLAN mapping are planned. ## Directories -`configs/`, `diagrams/`, `docs/`, `screenshots/` +`configs/`, `diagrams/`, `docs/`, `screenshots/`, `screenshots-redacted/` ## Rules diff --git a/CHANGELOG.md b/CHANGELOG.md index 76c4aad..c2a0368 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -8,6 +8,17 @@ --- +### 2026-09-27 UniFi hardware refresh + +- Replaced the ER605 and TL-SG2210P with a UDM Pro and USW-24-PoE in an equivalent-state cutover. +- Kept the LAN flat, with the same gateway, DHCP, DNS, and Deco AP behavior. VLAN segmentation and firewall policy remain planned. + +### Recent documentation merges + +- 2026-09-22: redacted the ER605 WAN and reservation screenshots (#9). +- 2026-09-27: updated links to renamed public repositories (#11). +- 2026-09-28: clarified README network status and wording (#12). + ### Added - Initial project repository structure diff --git a/CURRENT-STATUS.md b/CURRENT-STATUS.md index b5da741..be95909 100644 --- a/CURRENT-STATUS.md +++ b/CURRENT-STATUS.md @@ -5,15 +5,15 @@ ![Phase](https://img.shields.io/badge/Phase-1%20Managed%20Cutover-purple) ![Docs](https://img.shields.io/badge/Docs-Portfolio%20Ready-informational) -## Phase 1 Complete: Managed Network Baseline Ready for VLAN Segmentation +## UniFi Network Core Live; VLAN Segmentation Planned --- ## Project Status -**Phase 1 is complete.** +**Phase 1 and the 2026-09-27 UniFi hardware refresh are complete.** -This repository currently documents the managed network cutover from a consumer mesh/router-controlled design to a dedicated router, managed switch, AP-mode wireless, and VLAN-ready network foundation. +The current network core is a UniFi UDM Pro and USW-24-PoE. The LAN remains flat, with Deco nodes in AP mode. Phase 1 documents the earlier ER605 and Omada cutover as history. --- @@ -21,8 +21,9 @@ This repository currently documents the managed network cutover from a consumer | Area | Status | Notes | |---|---:|---| -| ER605 router cutover | ✅ Complete | Router/firewall is now the primary routing device | -| Managed switch integration | ✅ Complete | TL-SG2210P is in the production network path | +| ER605 router cutover | ✅ Complete | Historical Phase 1 cutover, replaced by UniFi on 2026-09-27 | +| Managed switch integration | ✅ Complete | Historical TL-SG2210P integration, replaced by USW-24-PoE | +| UniFi hardware refresh | ✅ Complete | UDM Pro and USW-24-PoE form the current network core | | Deco AP mode migration | ✅ Complete | Deco mesh is no longer acting as the router | | DNS validation | ✅ Complete | Pi-hole HA DNS path remained operational | | DHCP validation | ✅ Complete | Clients received valid leases | @@ -42,9 +43,9 @@ ONT ↓ AT&T Gateway / IP Passthrough ↓ -TP-Link ER605 Router +UniFi UDM Pro ↓ -TP-Link TL-SG2210P Managed Switch +UniFi USW-24-PoE Managed Switch ├── Deco Mesh APs ├── Proxmox Host ├── Primary Pi-hole @@ -87,9 +88,9 @@ This keeps the project clean: | Task | Status | |---|---:| -| Add final physical topology diagram | ⏳ Pending | +| Add current physical topology diagram | ✅ Complete | | Add final logical topology diagram | ⏳ Pending | -| Add sanitized Omada screenshots | ⏳ Pending | +| Add sanitized Phase 1 Omada screenshots | ✅ Complete | | Add switch port mapping | ⏳ Pending | | Start VLAN/subnet design | ⏳ Pending | | Build firewall policy matrix | ⏳ Pending | diff --git a/LESSONS-LEARNED.md b/LESSONS-LEARNED.md index c1885c0..be4be87 100644 --- a/LESSONS-LEARNED.md +++ b/LESSONS-LEARNED.md @@ -133,3 +133,7 @@ That is closer to real infrastructure work than a simple home network diagram. The next focus is Phase 2: VLAN segmentation. The goal is to move from a flat managed network to a segmented design with separate zones for trusted devices, infrastructure, IoT, guest access, and lab systems. + +## 2026-09-27 UniFi Equivalent-State Refresh + +The UDM Pro and USW-24-PoE replaced the ER605 and TL-SG2210P while the LAN stayed flat. Keeping the gateway, DHCP, DNS, and Deco AP behavior the same made the hardware change easier to validate. The ER605 and Omada screenshots remain Phase 1 evidence; current-state diagrams now show UniFi. Segmentation remains a separate planned change. diff --git a/README.md b/README.md index 6230956..4d69e8c 100644 --- a/README.md +++ b/README.md @@ -2,16 +2,16 @@ ![Status](https://img.shields.io/badge/Status-Complete-brightgreen) ![Project](https://img.shields.io/badge/Project-Managed%20Network%20Infrastructure-blue) -![Routing](https://img.shields.io/badge/Routing-ER605-informational) -![Switching](https://img.shields.io/badge/Switching-Managed%20PoE%20Switch-informational) +![Routing](https://img.shields.io/badge/Routing-UDM%20Pro-informational) +![Switching](https://img.shields.io/badge/Switching-USW--24--PoE-informational) ![DNS](https://img.shields.io/badge/DNS-Pi--hole%20HA-purple) ![Platform](https://img.shields.io/badge/Platform-Proxmox-orange) -## Managed Router/Switch Cutover, Omada SDN, AP Mode, and VLAN-Ready Network Foundation +## Managed Network Cutovers, UniFi, AP Mode, and VLAN-Ready Network Foundation --- -This repository documents Project 2 of my home network infrastructure lab: the migration from a consumer mesh/router-controlled network to a managed network foundation using a dedicated router/firewall, managed switch, Omada SDN Controller, AP-mode wireless, redundant DNS, Proxmox-hosted services, and monitoring validation. +This repository documents Project 2 of my home network infrastructure lab. Phase 1 records the ER605 and Omada cutover. A later equivalent-state refresh put a UniFi UDM Pro and USW-24-PoE at the network core on 2026-09-27. Deco nodes remain in AP mode, and the LAN remains flat. VLAN segmentation and firewall policy are planned. Project 1 focused on building reliable core infrastructure services such as HA DNS, Unbound recursive DNS, monitoring, alerting, Tailscale remote access, Proxmox-hosted services, and operational validation. @@ -40,7 +40,7 @@ This project documents the cutover from a consumer home network design into a mo The main goal was to move routing and switching responsibilities away from the mesh system and into dedicated network infrastructure while keeping core services stable. -This phase introduced: +The original Phase 1 cutover introduced: - Dedicated routing with TP-Link ER605 - Managed switching with TP-Link TL-SG2210P @@ -79,9 +79,9 @@ ONT ↓ AT&T Gateway / IP Passthrough ↓ -TP-Link ER605 Router / Firewall +UniFi UDM Pro Router / Firewall ↓ -TP-Link TL-SG2210P Managed PoE Switch +UniFi USW-24-PoE Managed Switch ├── Deco Mesh APs ├── Proxmox Host ├── Primary Pi-hole Node @@ -95,7 +95,7 @@ TP-Link TL-SG2210P Managed PoE Switch ```text Client Device ↓ -ER605 DHCP-Provided DNS +UDM Pro DHCP-Provided DNS ↓ Pi-hole HA VIP ↓ @@ -127,7 +127,7 @@ Admin Endpoint ↓ Trusted LAN / Tailscale ↓ -Proxmox / Omada / Pi-hole / Monitoring Services +Proxmox / UniFi Network / Pi-hole / Monitoring Services ``` --- @@ -137,12 +137,13 @@ Proxmox / Omada / Pi-hole / Monitoring Services | Phase | Status | Focus | |---|---:|---| | Phase 1 - Managed Router/Switch Cutover | ✅ Complete | ER605 cutover, managed switch integration, Deco AP mode, baseline validation | +| UniFi Hardware Refresh (2026-09-27) | ✅ Complete | UDM Pro and USW-24-PoE replaced the ER605 and TL-SG2210P without adding segmentation | | Phase 2 - VLAN Segmentation | ⏳ Planned | VLAN IDs, subnet plan, network zones, DHCP scopes | | Phase 3 - Firewall Policy | ⏳ Planned | Inter-VLAN rules, restricted management access, IoT/guest isolation | | Phase 4 - Wireless SSID Mapping | ⏳ Planned | SSID-to-VLAN mapping for trusted, guest, IoT, and lab wireless | | Phase 5 - Monitoring and Operations | ⏳ Planned | Monitoring updates, dashboards, runbooks, backups, validation procedures | -Hardware refresh (2026-09-27): the ER605 and TL-SG2210P were replaced by a UniFi Dream Machine Pro and a USW-24-PoE in an equivalent-state cutover. The network stayed the same (flat `192.168.68.0/24`, same gateway, DHCP, and DNS), and the Deco units stay in AP mode. Phase 1 documents the ER605 and Omada cutover as it happened; Phase 2 onward runs on the UniFi hardware. +Phase 1 documents the ER605 and Omada cutover as it happened. The 2026-09-27 UniFi refresh kept the same flat LAN, gateway, DHCP, and DNS behavior. Phase 2 onward uses the UniFi hardware. --- @@ -175,8 +176,7 @@ Hardware refresh (2026-09-27): the ER605 and TL-SG2210P were replaced by a UniFi | Diagram | Status | Link | |---|---:|---| -| Topology before the UniFi refresh (Omada, flat) | Done | [View](diagrams/current-topology.md) | -| Current Topology (UniFi, flat) | Planned | Migration done 2026-09-27; diagram not drawn yet | +| Current Topology (UniFi, flat) | Done | [View](diagrams/current-topology.md) | | Phase 2 - VLAN Segmentation Design | Planned | Coming soon | | Phase 3 - Firewall Policy Flow | Planned | Coming soon | @@ -189,13 +189,13 @@ Hardware refresh (2026-09-27): the ER605 and TL-SG2210P were replaced by a UniFi | AT&T Fiber Connection | WAN connectivity | | ONT / Optical Network Terminal | Fiber handoff | | AT&T Gateway with IP Passthrough | ISP gateway | -| TP-Link ER605 | Dedicated router/firewall | -| TP-Link TL-SG2210P | Managed PoE switch | +| UniFi UDM Pro | Dedicated router/firewall | +| UniFi USW-24-PoE | Managed PoE switch | | TP-Link Deco Mesh | Wireless access points in AP mode | | Raspberry Pi 3B+ | Primary Pi-hole DNS node | | Raspberry Pi 3B | Secondary Pi-hole DNS node | | Dell OptiPlex Proxmox Host | Virtualization host | -| Omada Controller LXC | Network controller | +| UniFi Network | Network management on the UDM Pro | | Docker Monitoring VM | Monitoring service host | | Admin Workstation / Laptop | Testing and management endpoint | @@ -205,9 +205,9 @@ Hardware refresh (2026-09-27): the ER605 and TL-SG2210P were replaced by a UniFi | Tool / Service | Purpose | |---|---| -| Omada SDN Controller | Centralized management for router and switch | -| TP-Link ER605 | Routing, firewalling, DHCP, and WAN handoff | -| TP-Link TL-SG2210P | Managed switching and future VLAN trunk/access ports | +| UniFi Network | Centralized management for router and switch | +| UniFi UDM Pro | Routing, firewalling, DHCP, and WAN handoff | +| UniFi USW-24-PoE | Managed switching and future VLAN trunk/access ports | | Pi-hole | DNS filtering and visibility | | Keepalived | DNS virtual IP failover | | Gravity Sync | Pi-hole configuration synchronization | @@ -222,7 +222,7 @@ Hardware refresh (2026-09-27): the ER605 and TL-SG2210P were replaced by a UniFi --- -## Phase 1 Validation Summary +## Historical Phase 1 Validation Summary (ER605 and Omada) | Validation Area | Result | |---|---:| @@ -304,5 +304,7 @@ This repository is part of a broader infrastructure lab portfolio. | Repository | Focus | Relationship | |---|---|---| | [Home Network Infrastructure Lab](https://github.com/stayZ3RO/dns) | HA DNS, Pi-hole, Unbound, monitoring, Tailscale, Proxmox, RustDesk | Provides the core infrastructure foundation used by this project | -| [Home Network Managed Infrastructure Lab](https://github.com/stayZ3RO/netlab) | Managed router, switching, VLANs, firewall policy, network segmentation | Expands the home lab into managed network infrastructure | +| [Home Network Managed Infrastructure Lab](https://github.com/stayZ3RO/netlab) | Managed router and switching; VLANs, firewall policy, and segmentation planned | Expands the home lab into managed network infrastructure | | [VPS Cloud Infrastructure Lab](https://github.com/stayZ3RO/vps-lab) | Linux VPS hardening, Docker, DNS, HTTPS, monitoring, backups, secure access | Extends infrastructure operations into cloud-hosted services | + +See the [portfolio](https://chrisalorenzo.com/) for the live project index. diff --git a/diagrams/README.md b/diagrams/README.md index 5996bfa..7832942 100644 --- a/diagrams/README.md +++ b/diagrams/README.md @@ -1,6 +1,6 @@ # Architecture Diagrams -![Status](https://img.shields.io/badge/Status-Planned-yellow) +![Status](https://img.shields.io/badge/Status-Current-informational) ![Project](https://img.shields.io/badge/Project-Managed%20Network%20Infrastructure-blue) ![Docs](https://img.shields.io/badge/Docs-Portfolio%20Ready-informational) @@ -14,8 +14,8 @@ This folder contains architecture diagrams for the managed network infrastructur | Diagram | Status | |---|---:| -| [Current Topology (Omada, flat)](current-topology.md) | Done | -| Target Topology (UniFi) | Planned, with the router/switch migration | +| [Current Topology (UniFi, flat)](current-topology.md) | Done | +| [Phase 1 Diagrams (ER605 and Omada, historical)](../docs/phase-1-managed-network-cutover/diagrams.md) | Done | | Phase 2 - VLAN Segmentation Design | Planned | | Phase 3 - Firewall Policy Flow | Planned | diff --git a/diagrams/current-topology.md b/diagrams/current-topology.md index 1e93b82..0d6b003 100644 --- a/diagrams/current-topology.md +++ b/diagrams/current-topology.md @@ -1,51 +1,32 @@ -# Current Topology: Managed Network (Omada, flat) +# Current Topology: UniFi (flat LAN) -The network as it runs today: a single flat `192.168.68.0/24`, managed by -the Omada Controller, with the Pi-hole HA pair providing DNS behind a -Keepalived VIP. +The UDM Pro and USW-24-PoE have been the network core since the +2026-09-27 equivalent-state cutover. Deco nodes remain access points. The LAN +is still flat; VLAN segmentation and inter-VLAN firewall policy are planned. +The [Phase 1 diagrams](../docs/phase-1-managed-network-cutover/diagrams.md) +record the earlier ER605 and Omada network. ```mermaid flowchart TD - ONT["AT&T Fiber ONT"] - ER["TP-Link ER605 v2
gateway / firewall, 192.168.68.1
Omada-managed · DHCP + DNS source"] - SW["TP-Link TL-SG2210P v3
managed PoE switch, 192.168.68.2"] - DECO["Deco X25, AP mode
main node on switch port 8
other nodes: wireless mesh"] - - ONT -->|IP passthrough| ER - ER --> SW - SW -->|port 8| DECO - - subgraph CLUSTER["Proxmox cluster"] - direction LR - P1["pve01, .80"] - P2["pve02, .90"] - P3["pve03, .70"] - end - SW --> CLUSTER - - subgraph SERVICES["Hosted VMs / LXCs"] - direction TB - PH["Pi-hole HA
pihole01 .4 · pihole02 .5
Keepalived VIP .20 → client DNS"] - OC["Omada Controller VM, .3"] - MON["monitoring .94 · portainer .92
rustdesk .93 · ts-router01 / 02"] - end - CLUSTER --> SERVICES - - OC -.->|manages| ER - OC -.->|manages| SW - - classDef ext fill:#334155,stroke:#94a3b8,color:#f1f5f9 - classDef net fill:#075985,stroke:#38bdf8,color:#e0f2fe - classDef host fill:#92400e,stroke:#fbbf24,color:#fef3c7 - classDef svc fill:#166534,stroke:#4ade80,color:#dcfce7 - class ONT ext - class ER,SW,DECO net - class P1,P2,P3 host - class PH,OC,MON svc + ONT["AT&T Fiber ONT and gateway"] + UDM["UniFi UDM Pro
gateway, firewall, and DHCP"] + SW["UniFi USW-24-PoE
managed PoE switch"] + DECO["Deco nodes
AP mode"] + DNS["Pi-hole HA pair
Keepalived VIP and Unbound"] + PVE["Proxmox cluster"] + MON["Monitoring VM 294
Prometheus, Grafana, Alertmanager"] + CLIENTS["Wired and wireless clients"] + + ONT -->|IP passthrough| UDM + UDM --> SW + SW --> DECO + SW --> DNS + SW --> PVE + SW --> CLIENTS + PVE --> MON + DECO --> CLIENTS ``` -**Single flat `192.168.68.0/24` · VLAN 1 only · no segmentation.** VLAN -segmentation, inter-VLAN firewall policy, and SSID-to-VLAN mapping are the -next phase. A "Target State (UniFi)" variant of this diagram will land with -the router/switch migration. Same layout, with ER605 → UDM Pro (`.1`), -SG2210P → USW-24-PoE (`.2`), Deco unchanged. +The UDM Pro supplies DHCP, with the Pi-hole VIP as client DNS. The +2026-09-27 cutover kept the same gateway and DNS behavior; it did not +introduce segmentation. diff --git a/docs/phase-1-managed-network-cutover/README.md b/docs/phase-1-managed-network-cutover/README.md index 9233e08..bf31fda 100644 --- a/docs/phase-1-managed-network-cutover/README.md +++ b/docs/phase-1-managed-network-cutover/README.md @@ -12,7 +12,7 @@ ## Overview -Phase 1 documents the migration from a consumer mesh/router-controlled network to a managed network foundation using a dedicated router/firewall, managed switch, Omada SDN Controller, AP-mode wireless, redundant DNS, monitoring, and post-cutover validation. +Phase 1 documents the historical ER605 and Omada migration from a consumer mesh/router-controlled network to a managed foundation, including AP-mode wireless, redundant DNS, monitoring, and post-cutover validation. The UDM Pro and USW-24-PoE replaced that network core on 2026-09-27. The purpose of this phase was to complete the managed router/switch cutover first, confirm all core services survived the change, and create a stable baseline before introducing VLAN segmentation. @@ -54,21 +54,21 @@ The purpose of this phase was to complete the managed router/switch cutover firs | Evidence | Category | Purpose | |---|---|---| -| [ER605 WAN Online](../../screenshots/phase-1-managed-network-cutover/02-er605-wan-online.png) | Router / Gateway | Confirms the ER605 WAN interface came online after the cutover. | -| [ER605 LAN DHCP Configuration](../../screenshots/phase-1-managed-network-cutover/03-er605-lan-dhcp-config.png) | DHCP | Shows LAN DHCP configuration now controlled by the ER605. | -| [ER605 Address Reservations](../../screenshots/phase-1-managed-network-cutover/04-er605-address-reservations.png) | DHCP | Documents DHCP reservations for infrastructure devices. | -| [Managed Switch Online in Omada](../../screenshots/phase-1-managed-network-cutover/05-managed-switch-online-in-omada.png) | Managed Switch | Confirms the managed switch is online and visible in Omada. | -| [Managed Switch Port Map](../../screenshots/phase-1-managed-network-cutover/06-managed-switch-port-map.png) | Managed Switch | Shows active switch ports and physical connectivity. | -| [PoE Status for Pi Nodes](../../screenshots/phase-1-managed-network-cutover/07-poe-status-pi-nodes.png) | Power / Switching | Shows PoE status for infrastructure nodes connected to the managed switch. | -| [Wired Client DHCP from ER605](../../screenshots/phase-1-managed-network-cutover/10-wired-client-dhcp-from-er605.png) | Client Validation | Confirms a wired client received DHCP from the ER605-controlled network. | -| [Wi-Fi Client DHCP from ER605](../../screenshots/phase-1-managed-network-cutover/11-wifi-client-dhcp-from-er605.png) | Wireless Validation | Confirms a wireless client received DHCP from the ER605 while Deco operated in AP mode. | -| [Pi-hole Queries After Cutover](../../screenshots/phase-1-managed-network-cutover/13-pihole-queries-after-cutover.png) | DNS | Shows Pi-hole receiving queries after the managed network cutover. | -| [HA DNS VIP Reachable After Cutover](../../screenshots/phase-1-managed-network-cutover/14-ha-dns-vip-reachable-after-cutover.png) | DNS High Availability | Confirms the HA DNS virtual IP remained reachable. | -| [Proxmox Access After Cutover](../../screenshots/phase-1-managed-network-cutover/15-proxmox-access-after-cutover.png) | Infrastructure | Confirms Proxmox remained reachable after the cutover. | -| [Grafana Access After Cutover](../../screenshots/phase-1-managed-network-cutover/16-grafana-access-after-cutover.png) | Monitoring | Confirms Grafana remained reachable after the cutover. | -| [Omada Controller After Cutover](../../screenshots/phase-1-managed-network-cutover/17-omada-controller-after-cutover.png) | Management | Confirms Omada Controller remained accessible after the cutover. | -| [RustDesk Access After Cutover](../../screenshots/phase-1-managed-network-cutover/18-rustdesk-access-after-cutover.png) | Remote Access | Confirms private remote access remained available after the cutover. | -| [Final Omada Topology and Client List](../../screenshots/phase-1-managed-network-cutover/20-final-omada-topology-client-list.png) | Topology | Shows final managed network visibility after the cutover. | +| [ER605 WAN Online](../../screenshots-redacted/phase-1-managed-network-cutover/02-er605-wan-online.png) | Router / Gateway | Confirms the ER605 WAN interface came online after the cutover. | +| [ER605 LAN DHCP Configuration](../../screenshots-redacted/phase-1-managed-network-cutover/03-er605-lan-dhcp-config.png) | DHCP | Shows LAN DHCP configuration now controlled by the ER605. | +| [ER605 Address Reservations](../../screenshots-redacted/phase-1-managed-network-cutover/04-er605-address-reservations.png) | DHCP | Documents DHCP reservations for infrastructure devices. | +| [Managed Switch Online in Omada](../../screenshots-redacted/phase-1-managed-network-cutover/05-managed-switch-online-in-omada.png) | Managed Switch | Confirms the managed switch is online and visible in Omada. | +| [Managed Switch Port Map](../../screenshots-redacted/phase-1-managed-network-cutover/06-managed-switch-port-map.png) | Managed Switch | Shows active switch ports and physical connectivity. | +| [PoE Status for Pi Nodes](../../screenshots-redacted/phase-1-managed-network-cutover/07-poe-status-pi-nodes.png) | Power / Switching | Shows PoE status for infrastructure nodes connected to the managed switch. | +| [Wired Client DHCP from ER605](../../screenshots-redacted/phase-1-managed-network-cutover/10-wired-client-dhcp-from-er605.png) | Client Validation | Confirms a wired client received DHCP from the ER605-controlled network. | +| [Wi-Fi Client DHCP from ER605](../../screenshots-redacted/phase-1-managed-network-cutover/11-wifi-client-dhcp-from-er605.png) | Wireless Validation | Confirms a wireless client received DHCP from the ER605 while Deco operated in AP mode. | +| [Pi-hole Queries After Cutover](../../screenshots-redacted/phase-1-managed-network-cutover/13-pihole-queries-after-cutover.png) | DNS | Shows Pi-hole receiving queries after the managed network cutover. | +| [HA DNS VIP Reachable After Cutover](../../screenshots-redacted/phase-1-managed-network-cutover/14-ha-dns-vip-reachable-after-cutover.png) | DNS High Availability | Confirms the HA DNS virtual IP remained reachable. | +| [Proxmox Access After Cutover](../../screenshots-redacted/phase-1-managed-network-cutover/15-proxmox-access-after-cutover.png) | Infrastructure | Confirms Proxmox remained reachable after the cutover. | +| [Grafana Access After Cutover](../../screenshots-redacted/phase-1-managed-network-cutover/16-grafana-access-after-cutover.png) | Monitoring | Confirms Grafana remained reachable after the cutover. | +| [Omada Controller After Cutover](../../screenshots-redacted/phase-1-managed-network-cutover/17-omada-controller-after-cutover.png) | Management | Confirms Omada Controller remained accessible after the cutover. | +| [RustDesk Access After Cutover](../../screenshots-redacted/phase-1-managed-network-cutover/18-rustdesk-access-after-cutover.png) | Remote Access | Confirms private remote access remained available after the cutover. | +| [Final Omada Topology and Client List](../../screenshots-redacted/phase-1-managed-network-cutover/20-final-omada-topology-client-list.png) | Topology | Shows final managed network visibility after the cutover. | --- diff --git a/docs/phase-1-managed-network-cutover/diagrams.md b/docs/phase-1-managed-network-cutover/diagrams.md index 54989ed..67c3a13 100644 --- a/docs/phase-1-managed-network-cutover/diagrams.md +++ b/docs/phase-1-managed-network-cutover/diagrams.md @@ -10,7 +10,7 @@ ## Overview -This document links Phase 1 architecture diagrams for the managed network cutover. +These text diagrams record the historical Phase 1 ER605 and Omada cutover before the 2026-09-27 UniFi refresh. The [current UniFi topology](../../diagrams/current-topology.md) shows the later network core. The diagrams should make the network easy to understand without requiring access to the actual environment. @@ -29,7 +29,7 @@ The diagrams should make the network easy to understand without requiring access ## Diagram Gallery -No diagrams are currently linked. Add diagrams to `diagrams/phase-1-managed-network-cutover/` when ready. +The physical and DNS flow diagrams below record the historical Phase 1 cutover. --- diff --git a/docs/phase-1-managed-network-cutover/screenshots.md b/docs/phase-1-managed-network-cutover/screenshots.md index 93745ab..7c69753 100644 --- a/docs/phase-1-managed-network-cutover/screenshots.md +++ b/docs/phase-1-managed-network-cutover/screenshots.md @@ -12,7 +12,7 @@ This page contains screenshot evidence captured after the managed network cutover. -The screenshots validate that routing, switching, DHCP, DNS, monitoring, management access, and remote access remained operational after moving to the ER605 router, managed switch, and AP-mode wireless design. +These historical Phase 1 screenshots validate that routing, switching, DHCP, DNS, monitoring, management access, and remote access remained operational after moving to the ER605 router, managed switch, and AP-mode wireless design. The current UDM Pro and USW-24-PoE core replaced that hardware on 2026-09-27. --- @@ -20,21 +20,21 @@ The screenshots validate that routing, switching, DHCP, DNS, monitoring, managem | Evidence | Category | Purpose | |---|---|---| -| [ER605 WAN Online](../../screenshots/phase-1-managed-network-cutover/02-er605-wan-online.png) | Router / Gateway | Confirms the ER605 WAN interface came online after the cutover. | -| [ER605 LAN DHCP Configuration](../../screenshots/phase-1-managed-network-cutover/03-er605-lan-dhcp-config.png) | DHCP | Shows LAN DHCP configuration now controlled by the ER605. | -| [ER605 Address Reservations](../../screenshots/phase-1-managed-network-cutover/04-er605-address-reservations.png) | DHCP | Documents DHCP reservations for infrastructure devices. | -| [Managed Switch Online in Omada](../../screenshots/phase-1-managed-network-cutover/05-managed-switch-online-in-omada.png) | Managed Switch | Confirms the managed switch is online and visible in Omada. | -| [Managed Switch Port Map](../../screenshots/phase-1-managed-network-cutover/06-managed-switch-port-map.png) | Managed Switch | Shows active switch ports and physical connectivity. | -| [PoE Status for Pi Nodes](../../screenshots/phase-1-managed-network-cutover/07-poe-status-pi-nodes.png) | Power / Switching | Shows PoE status for infrastructure nodes connected to the managed switch. | -| [Wired Client DHCP from ER605](../../screenshots/phase-1-managed-network-cutover/10-wired-client-dhcp-from-er605.png) | Client Validation | Confirms a wired client received DHCP from the ER605-controlled network. | -| [Wi-Fi Client DHCP from ER605](../../screenshots/phase-1-managed-network-cutover/11-wifi-client-dhcp-from-er605.png) | Wireless Validation | Confirms a wireless client received DHCP from the ER605 while Deco operated in AP mode. | -| [Pi-hole Queries After Cutover](../../screenshots/phase-1-managed-network-cutover/13-pihole-queries-after-cutover.png) | DNS | Shows Pi-hole receiving queries after the managed network cutover. | -| [HA DNS VIP Reachable After Cutover](../../screenshots/phase-1-managed-network-cutover/14-ha-dns-vip-reachable-after-cutover.png) | DNS High Availability | Confirms the HA DNS virtual IP remained reachable. | -| [Proxmox Access After Cutover](../../screenshots/phase-1-managed-network-cutover/15-proxmox-access-after-cutover.png) | Infrastructure | Confirms Proxmox remained reachable after the cutover. | -| [Grafana Access After Cutover](../../screenshots/phase-1-managed-network-cutover/16-grafana-access-after-cutover.png) | Monitoring | Confirms Grafana remained reachable after the cutover. | -| [Omada Controller After Cutover](../../screenshots/phase-1-managed-network-cutover/17-omada-controller-after-cutover.png) | Management | Confirms Omada Controller remained accessible after the cutover. | -| [RustDesk Access After Cutover](../../screenshots/phase-1-managed-network-cutover/18-rustdesk-access-after-cutover.png) | Remote Access | Confirms private remote access remained available after the cutover. | -| [Final Omada Topology and Client List](../../screenshots/phase-1-managed-network-cutover/20-final-omada-topology-client-list.png) | Topology | Shows final managed network visibility after the cutover. | +| [ER605 WAN Online](../../screenshots-redacted/phase-1-managed-network-cutover/02-er605-wan-online.png) | Router / Gateway | Confirms the ER605 WAN interface came online after the cutover. | +| [ER605 LAN DHCP Configuration](../../screenshots-redacted/phase-1-managed-network-cutover/03-er605-lan-dhcp-config.png) | DHCP | Shows LAN DHCP configuration now controlled by the ER605. | +| [ER605 Address Reservations](../../screenshots-redacted/phase-1-managed-network-cutover/04-er605-address-reservations.png) | DHCP | Documents DHCP reservations for infrastructure devices. | +| [Managed Switch Online in Omada](../../screenshots-redacted/phase-1-managed-network-cutover/05-managed-switch-online-in-omada.png) | Managed Switch | Confirms the managed switch is online and visible in Omada. | +| [Managed Switch Port Map](../../screenshots-redacted/phase-1-managed-network-cutover/06-managed-switch-port-map.png) | Managed Switch | Shows active switch ports and physical connectivity. | +| [PoE Status for Pi Nodes](../../screenshots-redacted/phase-1-managed-network-cutover/07-poe-status-pi-nodes.png) | Power / Switching | Shows PoE status for infrastructure nodes connected to the managed switch. | +| [Wired Client DHCP from ER605](../../screenshots-redacted/phase-1-managed-network-cutover/10-wired-client-dhcp-from-er605.png) | Client Validation | Confirms a wired client received DHCP from the ER605-controlled network. | +| [Wi-Fi Client DHCP from ER605](../../screenshots-redacted/phase-1-managed-network-cutover/11-wifi-client-dhcp-from-er605.png) | Wireless Validation | Confirms a wireless client received DHCP from the ER605 while Deco operated in AP mode. | +| [Pi-hole Queries After Cutover](../../screenshots-redacted/phase-1-managed-network-cutover/13-pihole-queries-after-cutover.png) | DNS | Shows Pi-hole receiving queries after the managed network cutover. | +| [HA DNS VIP Reachable After Cutover](../../screenshots-redacted/phase-1-managed-network-cutover/14-ha-dns-vip-reachable-after-cutover.png) | DNS High Availability | Confirms the HA DNS virtual IP remained reachable. | +| [Proxmox Access After Cutover](../../screenshots-redacted/phase-1-managed-network-cutover/15-proxmox-access-after-cutover.png) | Infrastructure | Confirms Proxmox remained reachable after the cutover. | +| [Grafana Access After Cutover](../../screenshots-redacted/phase-1-managed-network-cutover/16-grafana-access-after-cutover.png) | Monitoring | Confirms Grafana remained reachable after the cutover. | +| [Omada Controller After Cutover](../../screenshots-redacted/phase-1-managed-network-cutover/17-omada-controller-after-cutover.png) | Management | Confirms Omada Controller remained accessible after the cutover. | +| [RustDesk Access After Cutover](../../screenshots-redacted/phase-1-managed-network-cutover/18-rustdesk-access-after-cutover.png) | Remote Access | Confirms private remote access remained available after the cutover. | +| [Final Omada Topology and Client List](../../screenshots-redacted/phase-1-managed-network-cutover/20-final-omada-topology-client-list.png) | Topology | Shows final managed network visibility after the cutover. | --- @@ -42,7 +42,7 @@ The screenshots validate that routing, switching, DHCP, DNS, monitoring, managem ### ER605 WAN Online -![ER605 WAN Online](../../screenshots/phase-1-managed-network-cutover/02-er605-wan-online.png) +![ER605 WAN Online](../../screenshots-redacted/phase-1-managed-network-cutover/02-er605-wan-online.png) Confirms the ER605 WAN interface came online after the cutover. @@ -50,7 +50,7 @@ Confirms the ER605 WAN interface came online after the cutover. ### ER605 LAN DHCP Configuration -![ER605 LAN DHCP Configuration](../../screenshots/phase-1-managed-network-cutover/03-er605-lan-dhcp-config.png) +![ER605 LAN DHCP Configuration](../../screenshots-redacted/phase-1-managed-network-cutover/03-er605-lan-dhcp-config.png) Shows LAN DHCP configuration now controlled by the ER605. @@ -58,7 +58,7 @@ Shows LAN DHCP configuration now controlled by the ER605. ### ER605 Address Reservations -![ER605 Address Reservations](../../screenshots/phase-1-managed-network-cutover/04-er605-address-reservations.png) +![ER605 Address Reservations](../../screenshots-redacted/phase-1-managed-network-cutover/04-er605-address-reservations.png) Documents DHCP reservations for infrastructure devices. @@ -66,7 +66,7 @@ Documents DHCP reservations for infrastructure devices. ### Managed Switch Online in Omada -![Managed Switch Online in Omada](../../screenshots/phase-1-managed-network-cutover/05-managed-switch-online-in-omada.png) +![Managed Switch Online in Omada](../../screenshots-redacted/phase-1-managed-network-cutover/05-managed-switch-online-in-omada.png) Confirms the managed switch is online and visible in Omada. @@ -74,7 +74,7 @@ Confirms the managed switch is online and visible in Omada. ### Managed Switch Port Map -![Managed Switch Port Map](../../screenshots/phase-1-managed-network-cutover/06-managed-switch-port-map.png) +![Managed Switch Port Map](../../screenshots-redacted/phase-1-managed-network-cutover/06-managed-switch-port-map.png) Shows active switch ports and physical connectivity. @@ -82,7 +82,7 @@ Shows active switch ports and physical connectivity. ### PoE Status for Pi Nodes -![PoE Status for Pi Nodes](../../screenshots/phase-1-managed-network-cutover/07-poe-status-pi-nodes.png) +![PoE Status for Pi Nodes](../../screenshots-redacted/phase-1-managed-network-cutover/07-poe-status-pi-nodes.png) Shows PoE status for infrastructure nodes connected to the managed switch. @@ -90,7 +90,7 @@ Shows PoE status for infrastructure nodes connected to the managed switch. ### Wired Client DHCP from ER605 -![Wired Client DHCP from ER605](../../screenshots/phase-1-managed-network-cutover/10-wired-client-dhcp-from-er605.png) +![Wired Client DHCP from ER605](../../screenshots-redacted/phase-1-managed-network-cutover/10-wired-client-dhcp-from-er605.png) Confirms a wired client received DHCP from the ER605-controlled network. @@ -98,7 +98,7 @@ Confirms a wired client received DHCP from the ER605-controlled network. ### Wi-Fi Client DHCP from ER605 -![Wi-Fi Client DHCP from ER605](../../screenshots/phase-1-managed-network-cutover/11-wifi-client-dhcp-from-er605.png) +![Wi-Fi Client DHCP from ER605](../../screenshots-redacted/phase-1-managed-network-cutover/11-wifi-client-dhcp-from-er605.png) Confirms a wireless client received DHCP from the ER605 while Deco operated in AP mode. @@ -106,7 +106,7 @@ Confirms a wireless client received DHCP from the ER605 while Deco operated in A ### Pi-hole Queries After Cutover -![Pi-hole Queries After Cutover](../../screenshots/phase-1-managed-network-cutover/13-pihole-queries-after-cutover.png) +![Pi-hole Queries After Cutover](../../screenshots-redacted/phase-1-managed-network-cutover/13-pihole-queries-after-cutover.png) Shows Pi-hole receiving queries after the managed network cutover. @@ -114,7 +114,7 @@ Shows Pi-hole receiving queries after the managed network cutover. ### HA DNS VIP Reachable After Cutover -![HA DNS VIP Reachable After Cutover](../../screenshots/phase-1-managed-network-cutover/14-ha-dns-vip-reachable-after-cutover.png) +![HA DNS VIP Reachable After Cutover](../../screenshots-redacted/phase-1-managed-network-cutover/14-ha-dns-vip-reachable-after-cutover.png) Confirms the HA DNS virtual IP remained reachable. @@ -122,7 +122,7 @@ Confirms the HA DNS virtual IP remained reachable. ### Proxmox Access After Cutover -![Proxmox Access After Cutover](../../screenshots/phase-1-managed-network-cutover/15-proxmox-access-after-cutover.png) +![Proxmox Access After Cutover](../../screenshots-redacted/phase-1-managed-network-cutover/15-proxmox-access-after-cutover.png) Confirms Proxmox remained reachable after the cutover. @@ -130,7 +130,7 @@ Confirms Proxmox remained reachable after the cutover. ### Grafana Access After Cutover -![Grafana Access After Cutover](../../screenshots/phase-1-managed-network-cutover/16-grafana-access-after-cutover.png) +![Grafana Access After Cutover](../../screenshots-redacted/phase-1-managed-network-cutover/16-grafana-access-after-cutover.png) Confirms Grafana remained reachable after the cutover. @@ -138,7 +138,7 @@ Confirms Grafana remained reachable after the cutover. ### Omada Controller After Cutover -![Omada Controller After Cutover](../../screenshots/phase-1-managed-network-cutover/17-omada-controller-after-cutover.png) +![Omada Controller After Cutover](../../screenshots-redacted/phase-1-managed-network-cutover/17-omada-controller-after-cutover.png) Confirms Omada Controller remained accessible after the cutover. @@ -146,7 +146,7 @@ Confirms Omada Controller remained accessible after the cutover. ### RustDesk Access After Cutover -![RustDesk Access After Cutover](../../screenshots/phase-1-managed-network-cutover/18-rustdesk-access-after-cutover.png) +![RustDesk Access After Cutover](../../screenshots-redacted/phase-1-managed-network-cutover/18-rustdesk-access-after-cutover.png) Confirms private remote access remained available after the cutover. @@ -154,7 +154,6 @@ Confirms private remote access remained available after the cutover. ### Final Omada Topology and Client List -![Final Omada Topology and Client List](../../screenshots/phase-1-managed-network-cutover/20-final-omada-topology-client-list.png) +![Final Omada Topology and Client List](../../screenshots-redacted/phase-1-managed-network-cutover/20-final-omada-topology-client-list.png) Shows final managed network visibility after the cutover. - diff --git a/docs/phase-1-managed-network-cutover/validation.md b/docs/phase-1-managed-network-cutover/validation.md index e842018..c342b82 100644 --- a/docs/phase-1-managed-network-cutover/validation.md +++ b/docs/phase-1-managed-network-cutover/validation.md @@ -20,22 +20,22 @@ Validate that the managed network cutover was successful and that all core servi | Validation Area | Status | Evidence | |---|---:|---| -| ER605 WAN online | ✅ Passed | [ER605 WAN Online](../../screenshots/phase-1-managed-network-cutover/02-er605-wan-online.png) | -| ER605 DHCP configuration | ✅ Passed | [ER605 LAN DHCP Configuration](../../screenshots/phase-1-managed-network-cutover/03-er605-lan-dhcp-config.png) | -| DHCP reservations | ✅ Passed | [ER605 Address Reservations](../../screenshots/phase-1-managed-network-cutover/04-er605-address-reservations.png) | -| Managed switch online | ✅ Passed | [Managed Switch Online in Omada](../../screenshots/phase-1-managed-network-cutover/05-managed-switch-online-in-omada.png) | -| Switch port mapping | ✅ Passed | [Managed Switch Port Map](../../screenshots/phase-1-managed-network-cutover/06-managed-switch-port-map.png) | -| PoE status for Pi nodes | ✅ Passed | [PoE Status for Pi Nodes](../../screenshots/phase-1-managed-network-cutover/07-poe-status-pi-nodes.png) | -| Wired client DHCP | ✅ Passed | [Wired Client DHCP from ER605](../../screenshots/phase-1-managed-network-cutover/10-wired-client-dhcp-from-er605.png) | -| Wireless client DHCP | ✅ Passed | [Wi-Fi Client DHCP from ER605](../../screenshots/phase-1-managed-network-cutover/11-wifi-client-dhcp-from-er605.png) | -| DNS through Pi-hole VIP | ✅ Passed | [DNS Validation Through Pi-hole VIP](../../screenshots/phase-1-managed-network-cutover/12-dns-validation-pi-hole-vip.png) | -| Pi-hole query visibility | ✅ Passed | [Pi-hole Queries After Cutover](../../screenshots/phase-1-managed-network-cutover/13-pihole-queries-after-cutover.png) | -| HA DNS VIP reachability | ✅ Passed | [HA DNS VIP Reachable After Cutover](../../screenshots/phase-1-managed-network-cutover/14-ha-dns-vip-reachable-after-cutover.png) | -| Proxmox access | ✅ Passed | [Proxmox Access After Cutover](../../screenshots/phase-1-managed-network-cutover/15-proxmox-access-after-cutover.png) | -| Grafana access | ✅ Passed | [Grafana Access After Cutover](../../screenshots/phase-1-managed-network-cutover/16-grafana-access-after-cutover.png) | -| Omada Controller access | ✅ Passed | [Omada Controller After Cutover](../../screenshots/phase-1-managed-network-cutover/17-omada-controller-after-cutover.png) | -| RustDesk remote access | ✅ Passed | [RustDesk Access After Cutover](../../screenshots/phase-1-managed-network-cutover/18-rustdesk-access-after-cutover.png) | -| Final Omada visibility | ✅ Passed | [Final Omada Topology and Client List](../../screenshots/phase-1-managed-network-cutover/20-final-omada-topology-client-list.png) | +| ER605 WAN online | ✅ Passed | [ER605 WAN Online](../../screenshots-redacted/phase-1-managed-network-cutover/02-er605-wan-online.png) | +| ER605 DHCP configuration | ✅ Passed | [ER605 LAN DHCP Configuration](../../screenshots-redacted/phase-1-managed-network-cutover/03-er605-lan-dhcp-config.png) | +| DHCP reservations | ✅ Passed | [ER605 Address Reservations](../../screenshots-redacted/phase-1-managed-network-cutover/04-er605-address-reservations.png) | +| Managed switch online | ✅ Passed | [Managed Switch Online in Omada](../../screenshots-redacted/phase-1-managed-network-cutover/05-managed-switch-online-in-omada.png) | +| Switch port mapping | ✅ Passed | [Managed Switch Port Map](../../screenshots-redacted/phase-1-managed-network-cutover/06-managed-switch-port-map.png) | +| PoE status for Pi nodes | ✅ Passed | [PoE Status for Pi Nodes](../../screenshots-redacted/phase-1-managed-network-cutover/07-poe-status-pi-nodes.png) | +| Wired client DHCP | ✅ Passed | [Wired Client DHCP from ER605](../../screenshots-redacted/phase-1-managed-network-cutover/10-wired-client-dhcp-from-er605.png) | +| Wireless client DHCP | ✅ Passed | [Wi-Fi Client DHCP from ER605](../../screenshots-redacted/phase-1-managed-network-cutover/11-wifi-client-dhcp-from-er605.png) | +| DNS through Pi-hole VIP | ✅ Passed | [DNS Validation Through Pi-hole VIP](../../screenshots-redacted/phase-1-managed-network-cutover/12-dns-validation-pihole-vip.png) | +| Pi-hole query visibility | ✅ Passed | [Pi-hole Queries After Cutover](../../screenshots-redacted/phase-1-managed-network-cutover/13-pihole-queries-after-cutover.png) | +| HA DNS VIP reachability | ✅ Passed | [HA DNS VIP Reachable After Cutover](../../screenshots-redacted/phase-1-managed-network-cutover/14-ha-dns-vip-reachable-after-cutover.png) | +| Proxmox access | ✅ Passed | [Proxmox Access After Cutover](../../screenshots-redacted/phase-1-managed-network-cutover/15-proxmox-access-after-cutover.png) | +| Grafana access | ✅ Passed | [Grafana Access After Cutover](../../screenshots-redacted/phase-1-managed-network-cutover/16-grafana-access-after-cutover.png) | +| Omada Controller access | ✅ Passed | [Omada Controller After Cutover](../../screenshots-redacted/phase-1-managed-network-cutover/17-omada-controller-after-cutover.png) | +| RustDesk remote access | ✅ Passed | [RustDesk Access After Cutover](../../screenshots-redacted/phase-1-managed-network-cutover/18-rustdesk-access-after-cutover.png) | +| Final Omada visibility | ✅ Passed | [Final Omada Topology and Client List](../../screenshots-redacted/phase-1-managed-network-cutover/20-final-omada-topology-client-list.png) | --- @@ -45,8 +45,8 @@ DHCP was validated from both wired and wireless clients. | Client Type | Result | Evidence | |---|---:|---| -| Wired client | ✅ Passed | [Wired Client DHCP from ER605](../../screenshots/phase-1-managed-network-cutover/10-wired-client-dhcp-from-er605.png) | -| Wireless client | ✅ Passed | [Wi-Fi Client DHCP from ER605](../../screenshots/phase-1-managed-network-cutover/11-wifi-client-dhcp-from-er605.png) | +| Wired client | ✅ Passed | [Wired Client DHCP from ER605](../../screenshots-redacted/phase-1-managed-network-cutover/10-wired-client-dhcp-from-er605.png) | +| Wireless client | ✅ Passed | [Wi-Fi Client DHCP from ER605](../../screenshots-redacted/phase-1-managed-network-cutover/11-wifi-client-dhcp-from-er605.png) | --- @@ -56,9 +56,9 @@ DNS was validated through the Pi-hole high-availability virtual IP. | Test | Result | Evidence | |---|---:|---| -| DNS resolution through VIP | ✅ Passed | [DNS Validation Through Pi-hole VIP](../../screenshots/phase-1-managed-network-cutover/12-dns-validation-pi-hole-vip.png) | -| Pi-hole receiving queries | ✅ Passed | [Pi-hole Queries After Cutover](../../screenshots/phase-1-managed-network-cutover/13-pihole-queries-after-cutover.png) | -| HA DNS VIP reachable | ✅ Passed | [HA DNS VIP Reachable After Cutover](../../screenshots/phase-1-managed-network-cutover/14-ha-dns-vip-reachable-after-cutover.png) | +| DNS resolution through VIP | ✅ Passed | [DNS Validation Through Pi-hole VIP](../../screenshots-redacted/phase-1-managed-network-cutover/12-dns-validation-pihole-vip.png) | +| Pi-hole receiving queries | ✅ Passed | [Pi-hole Queries After Cutover](../../screenshots-redacted/phase-1-managed-network-cutover/13-pihole-queries-after-cutover.png) | +| HA DNS VIP reachable | ✅ Passed | [HA DNS VIP Reachable After Cutover](../../screenshots-redacted/phase-1-managed-network-cutover/14-ha-dns-vip-reachable-after-cutover.png) | --- @@ -68,10 +68,10 @@ Core infrastructure services remained reachable after the cutover. | Service | Result | Evidence | |---|---:|---| -| Proxmox | ✅ Passed | [Proxmox Access After Cutover](../../screenshots/phase-1-managed-network-cutover/15-proxmox-access-after-cutover.png) | -| Grafana | ✅ Passed | [Grafana Access After Cutover](../../screenshots/phase-1-managed-network-cutover/16-grafana-access-after-cutover.png) | -| Omada Controller | ✅ Passed | [Omada Controller After Cutover](../../screenshots/phase-1-managed-network-cutover/17-omada-controller-after-cutover.png) | -| RustDesk | ✅ Passed | [RustDesk Access After Cutover](../../screenshots/phase-1-managed-network-cutover/18-rustdesk-access-after-cutover.png) | +| Proxmox | ✅ Passed | [Proxmox Access After Cutover](../../screenshots-redacted/phase-1-managed-network-cutover/15-proxmox-access-after-cutover.png) | +| Grafana | ✅ Passed | [Grafana Access After Cutover](../../screenshots-redacted/phase-1-managed-network-cutover/16-grafana-access-after-cutover.png) | +| Omada Controller | ✅ Passed | [Omada Controller After Cutover](../../screenshots-redacted/phase-1-managed-network-cutover/17-omada-controller-after-cutover.png) | +| RustDesk | ✅ Passed | [RustDesk Access After Cutover](../../screenshots-redacted/phase-1-managed-network-cutover/18-rustdesk-access-after-cutover.png) | --- diff --git a/docs/phase-2-vlan-segmentation/README.md b/docs/phase-2-vlan-segmentation/README.md index 424deed..4ec6563 100644 --- a/docs/phase-2-vlan-segmentation/README.md +++ b/docs/phase-2-vlan-segmentation/README.md @@ -2,7 +2,7 @@ ![Status](https://img.shields.io/badge/Status-Planned-yellow) ![Phase](https://img.shields.io/badge/Phase-2%20VLAN%20Segmentation-purple) -![Routing](https://img.shields.io/badge/Routing-ER605-informational) +![Routing](https://img.shields.io/badge/Routing-UDM%20Pro-informational) ![Switching](https://img.shields.io/badge/Switching-Managed%20PoE%20Switch-informational) ![Docs](https://img.shields.io/badge/Docs-Portfolio%20Ready-informational) diff --git a/docs/phase-3-firewall-policy/README.md b/docs/phase-3-firewall-policy/README.md index 3813ebf..70b9161 100644 --- a/docs/phase-3-firewall-policy/README.md +++ b/docs/phase-3-firewall-policy/README.md @@ -3,7 +3,7 @@ ![Status](https://img.shields.io/badge/Status-Planned-yellow) ![Phase](https://img.shields.io/badge/Phase-3%20Firewall%20Policy-purple) ![Security](https://img.shields.io/badge/Security-Sanitized%20Docs-red) -![Routing](https://img.shields.io/badge/Routing-ER605-informational) +![Routing](https://img.shields.io/badge/Routing-UDM%20Pro-informational) ![Docs](https://img.shields.io/badge/Docs-Portfolio%20Ready-informational) ## Planned Inter-VLAN Access Rules and Traffic Control Policy diff --git a/screenshots/README.md b/screenshots/README.md index 46c3aa3..225931e 100644 --- a/screenshots/README.md +++ b/screenshots/README.md @@ -1,6 +1,6 @@ # Screenshots -![Status](https://img.shields.io/badge/Status-Planned-yellow) +![Status](https://img.shields.io/badge/Status-Complete-brightgreen) ![Project](https://img.shields.io/badge/Project-Managed%20Network%20Infrastructure-blue) ![Security](https://img.shields.io/badge/Security-Sanitized%20Docs-red) ![Docs](https://img.shields.io/badge/Docs-Portfolio%20Ready-informational) @@ -9,7 +9,7 @@ --- -This folder contains sanitized screenshots used as validation evidence for the managed network infrastructure lab. +The [redacted Phase 1 screenshots](../screenshots-redacted/phase-1-managed-network-cutover/) document the historical ER605 and Omada cutover. The current network uses a UniFi UDM Pro and USW-24-PoE, with Deco nodes in AP mode. ## Screenshot Categories diff --git a/scripts/check-relative-links.py b/scripts/check-relative-links.py new file mode 100644 index 0000000..a5a725a --- /dev/null +++ b/scripts/check-relative-links.py @@ -0,0 +1,30 @@ +#!/usr/bin/env python3 +"""Check that tracked Markdown links resolve to local files.""" +from pathlib import Path +from urllib.parse import unquote, urlsplit +import re +import subprocess +import sys + +root = Path.cwd().resolve() +names = subprocess.check_output(["git", "ls-files", "-z", "--", "*.md"]).decode().split("\0") +broken = [] +for name in filter(None, names): + source = Path(name) + for line_no, line in enumerate(source.read_text().splitlines(), 1): + for match in re.finditer(r"\]\(([^)]+)\)", line): + raw = match.group(1).strip() + if not raw: + continue + url = raw[1:].split(">", 1)[0] if raw.startswith("<") else raw.split()[0] + parsed = urlsplit(url) + if parsed.scheme or parsed.netloc or not parsed.path or parsed.path.startswith("/"): + continue + target = (source.parent / unquote(parsed.path)).resolve() + if not target.is_relative_to(root) or not target.exists(): + broken.append((name, line_no, url)) + +for name, line_no, url in broken: + print(f"::error file={name},line={line_no}::Missing local link target: {url}") +print(f"Checked relative links in {len(names) - 1} tracked Markdown files; {len(broken)} broken.") +sys.exit(bool(broken))