The hardest part of my NAS dashboard was getting traffic to reach it
说明与用途
在部署 NAS 仪表板以实现基于规则的代理路由时,需要手动配置 IP、检查冲突并从客户端进行测试,以确保客户端采用新的网关和 DNS 设置。
问题
Deploying a NAS‑based device‑flow dashboard required ensuring that client devices use the NAS‑hosted proxy routing, but automatic DHCP configuration and network topology made it hard for clients to adopt the new gateway and DNS settings.
结果
The release 0.1.0 includes a prebuilt Linux x86‑64 controller image, a NAS Compose installation file, and 105 automated tests. The dashboard supports multiple languages and appearance themes. The installer now requires manual IP entry and client‑side testing to avoid gateway and address conflicts.
工作流
- Install NAS controller image and NAS Compose file
- Configure core IP, panel IP and DHCP range manually
- Validate IP ranges and check for responsive conflicts
- Disable other DHCP servers on the network
- Enable DHCP on the NAS after confirming single‑client routing
- Test proxy routing from a client device on the same LAN
证据
A client can retain its old gateway until it renews its DHCP lease.
The installer now explicitly asks for a test from another device on the same LAN.
I checked 105 automated tests, container startup and isolated DHCP exchanges in CI.
- 记录日期: 2026-10-09T12:10:50.096Z