network: Changing user's connection is risky.
Appying networking changes to the network connection that the user uses to access FreedomBox is risky, since he might virtually brick his box. Therefore he needs a user-friendly path to do make such changes.
After some discussion in last (2020/09/12) hacking audio call, the current choice is to borrow the typical procedure for changing the screen resolution in desktops: apply the changes with a certain time-out and ask for confirmation. If after applying the changes the user is able to reconnect and confirm the changes before they time out, they remain. Otherwise the system falls automagically back to the previous (valid) configuration.
In particular this has been asked for a specific case but should be generic and applied to other use cases risking the user connection to the box. Feel free to add more use cases to the list:
- A user goes from the default DHCP-provided dynamic IP to a static one.