Repository navigation
NAS Device Flow 0.1.0 is the first regular release: manage direct versus smart routing per device from a NAS-hosted panel.
Changes
- Korean joins Chinese, English, Japanese, Spanish and French in the main panel. The temporary installer remains bilingual (Chinese/English).
- Installer addresses are explicit: detect the actual interface, NAS address, subnet and default gateway; leave core, panel and future DHCP range blank. Each field explains its purpose. Browser and terminal installers check ranges and responsive conflicts; an ARP silence does not guarantee an unused address.
- Device name provenance follows the configured router adapter. Switching or losing an adapter clears stale router metadata while preserving manual names and proxy policy. A missing source falls back to “Router”, never Huawei.
- Clarify the NAS management IP:9088 installer versus the independent macvlan production-panel IP. Verify the production panel from another device on the same LAN.
Install / upgrade
For a new NAS GUI install, download setup.compose.yaml, set x-project-path to your actual NAS Docker folder (also change the setup port if 9088 is occupied), and follow the guide (中文). The setup YAML path edit is only the first step, not a complete network configuration. Fix the NAS management address, manually enter unused core/panel IPs and a future DHCP range, exclude static addresses from DHCP, and provide a compatible YAML subscription. Test one manually configured client before disabling main-router/other LAN DHCP and enabling NAS DHCP in the panel. Restore client automatic IP/DNS, renew leases and verify the actual gateway/DNS. The installer does not configure the router or force lease renewal. The standalone controller image archive is available for NAS GUI import when GHCR is unreachable; the Mihomo image still requires download.
For an existing installation, privately back up your deployment folder, change the controller image to ghcr.io/azbuilddev/nas-device-flow-controller:0.1.0, and recreate the controller while preserving all original networking and runtime mounts. Do not rerun the installer over an existing deployment. Do not import another machine's generated deployment YAML.
Configuration clarifications (2026-10-09)
Optional router name adapters are disabled by default and require manual configuration and router credentials. Available names/models depend on the router; exact device models and automatic router-brand detection are not promised. The panel DHCP controls act on NAS DHCP only. Current English and Chinese documentation clarify these steps. This documentation correction does not change the 0.1.0 tag, image or attachments.
Validation and scope
105 automated tests plus Linux CI Compose, Docker build, offline/foreign-UID container smoke and isolated DHCP checks passed. Korean persistence and the bilingual blank-address fields were checked in a browser using fictional data. The public controller image was downloaded anonymously in full and its OCI digests verified; Release attachments have SHA256 checksums.
Supported scope remains Linux x86-64 NAS and IPv4. The original deployment was verified on UGREEN DXP4800/UGOS Pro; fresh full-LAN installs on other NAS hardware remain unverified. OpenWrt/MikroTik name adapters have simulated tests only. IPv6 needs separate handling; automatic gateway failover is not provided. Changing language does not change the mainland-China routing preset.