Please implement non persistent (no flash write) change configuration possibility. This could be implemented through some global command likeany command that is performed inside that command context block should not persist change in configuration.
Some practical usages:
Code:
:nonpersistent do={ ... }Some practical usages:
- disabling/enabling interfaces or VPN servers to force reconnect used by netwatch or schedulers
- any short interval configuration change in loop where persistence is not needed, like LED light show script that turns on/off different leds in short intervals (it is possible on some routers), I know router is not Christmas tree, but it could be used for presentation, eg. on stores shelf
- reduced flash writes
- avoiding possible edge case scenario when netwatch script disables WAN (internet connection) interface to force reconnect (eg. lte) and while it's disabled power loss occurred, on next boot, because of persistence, internet connection is no longer available and can be an issue if user is not at home and wants to use for eg. BTH VPN - this is solvable with additional startup script that checks enabled states of interfaces, VPN servers, etc., but it just complicates things where it could be simpler with non persistent commands
Statistics: Posted by optio — Mon Dec 18, 2023 1:13 pm