Summary
When the setup wizard sets a static IP, write the config to the host OS's network manager (systemd-networkd, netplan, or NetworkManager — detected at runtime) so the OS re-applies the settings on boot. This is the right fix for "settings should persist across reboot."
Context
Successor to #321, which proposed having seed re-apply config on startup. That pattern is a configurator-appliance model (Ekahau Sidekick / UniFi style) and conflicts with the 2026-05-19 strategy reset positioning seed as a troubleshooting tool. The underlying user need ("my static IP doesn't survive reboot") is real, but the correct solution is OS integration, not a seed-side apply-on-startup hook.
Acceptance criteria
Out of scope
Priority
Medium — operator pain is real but workaround (manually editing OS config) exists.
Summary
When the setup wizard sets a static IP, write the config to the host OS's network manager (systemd-networkd, netplan, or NetworkManager — detected at runtime) so the OS re-applies the settings on boot. This is the right fix for "settings should persist across reboot."
Context
Successor to #321, which proposed having seed re-apply config on startup. That pattern is a configurator-appliance model (Ekahau Sidekick / UniFi style) and conflicts with the 2026-05-19 strategy reset positioning seed as a troubleshooting tool. The underlying user need ("my static IP doesn't survive reboot") is real, but the correct solution is OS integration, not a seed-side apply-on-startup hook.
Acceptance criteria
/etc/network/interfaces, BSD, etc.) — fail-loud, not silently no-op.networksetup) — Windows handled separately or out of scope.Out of scope
wpa_supplicant/NetworkManagervia existing connect flow).Priority
Medium — operator pain is real but workaround (manually editing OS config) exists.