The hardest part of my NAS dashboard was getting traffic to reach it

Description and use

Deploying a NAS dashboard for rule‑based proxy routing required manual IP configuration, conflict checks, and client‑side testing to ensure clients adopt the new gateway and DNS settings.

Problem

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.

Outcome

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.

Workflow

• 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

Evidence

A client can retain its old gateway until it renews its DHCP lease.

Source

The installer now explicitly asks for a test from another device on the same LAN.

Source

I checked 105 automated tests, container startup and isolated DHCP exchanges in CI.

Source