WORKING NOTES / PROJECT INDEX
Network: Project Index
I keep detailed working notes for the network. This index links each section to the corresponding project write-up, from gateway configuration and DNS to switching, monitoring and the IPv6 problems I have worked through.
The status column distinguishes running configurations, individual tests, earlier approaches and ideas that are not finished yet.
| Section | Work | Status | Read more |
|---|---|---|---|
| 01 | Network inventory, hardware roles and logical topology | Implemented and audited | Hardware and lab setup |
| 02 | WAN uplinks; IPv4, IPv6 prefix delegation; VLAN address-plan design | Implemented | Gateway and IPv6 |
| 03 | DHCPv4, RDNSS, AdGuard/Unbound, conditional AD DNS, dynamic DNS and ACME | Implemented; selected checks | DNS, DHCP and guest services |
| 04 | Firewall segmentation, NAT, policy routing and invalid stale state troubleshooting | Observed selected events | Gateway operations and fixes |
| 05 | Home WireGuard, policy-routed commercial VPN and selected forwarded application | Verified selected paths | Gateway and IPv6 |
| 06 | FreeRADIUS EAP-TLS, local-first directory fallback and CRL update persistence | Observed selected auth/failover | Certificate-based access |
| 07 | Dual-stack guest Captive Portal with dynamically generated AAAA | Configured and observed response | DNS, DHCP and guest services |
| 08 | Suricata IPS controlled block, Zenarmor policy block and LLDP | Observed selected tests | Gateway operations and fixes |
| 09 | Managed-switch IPv6/802.1X behavior and configuration diagnostics | Observed selected paths | Switching, Wi-Fi and 802.1X |
| 10 | Enterprise Wi-Fi; Grandstream membership/PVID; UniFi controller backup inspection | Observed / offline extraction | Switching, Wi-Fi and 802.1X |
| 11 | NAS ULA self-healing, Docker routes, proxy, infrastructure applications and update runbook | Implemented / selected tests | NAS and Docker |
| 12 | Service/metrics monitoring and operating automation | Implemented / selected tests | Gateway operations and fixes |
| 13 | OPNsense backup, update, custom hook and recovery discipline | Documented and exercised | Gateway operations and fixes |
| 14 | Earlier post-update audit and selected performance/security observations | Observed historically | Gateway operations and fixes |
| 15 | Status matrix: confirmed configuration versus open questions | Methodology retained | How I describe project status |
| 16 | Source-evidence hierarchy: live output, exports, operational notes | Methodology retained | How I investigate problems |
| 17 | Detailed OPNsense configuration export and service-level settings | Private source only | Gateway operations and fixes |
| 18 | Backup/export evidence boundaries and preservation plan | Methodology retained | Keeping the working files |
| 19 | OPNsense 26.7.7, RADIUS persistence and post-upgrade audits | Observed | Gateway operations and fixes |
| A | Read-only diagnostics for routing, DNS, RADIUS, VPN, IPS, NAS | Explained generically | Troubleshooting notes |
| B | Persistence and restoration of custom firewall/NAS hooks | Runbook documented | Gateway operations and fixes |
| C | Working configuration patterns for VPN, proxy and portal update logic | Sanitized design | DNS, DHCP and guest services |
| D | WAN IPv6 monitor source-address incident and temporary recovery | Observed historical | WAN IPv6 source problem |
| E | Post-reboot WAN/DDNS audit and UPS/NUT troubleshooting | Observed selected checks | Gateway operations and fixes |
| F | Dedicated Proxmox upstream VLAN and ACL/NAT path | Observed selected checks | Firewall test methods |
| G | Postboot review, guest restrictions and monitoring notifications | Observed / some open | Gateway operations and fixes |
| H | Persistent workaround for provider IPv6 source-selection failure | Implemented / checked | WAN IPv6 source problem |
| I | Selected-client WireGuard full-tunnel IPv4/IPv6 and dynamic NPTv6 | Observed on one client | WireGuard and NPTv6 |
How to use this index
The older entries show how the network changed over time. For an individual incident or test, the linked article explains what I checked, what worked and what I still want to try.