I’m not happy with the wAP default factory settings wich basically prevent them from being configured from the ethernet side wich is considered a “wan” port.
I know about the no-default=yes and the run-after-reset features. The problem is to remotely regain control over a device with a local user without strong computer skills who could make a netinstall.
What I want is to change the script that run when the user pushes the reset button for 5 seconds.
I know it can be dangerous but If I mess things up, I will do a clean netinstall.
In a worst case scenario, making a few bricks would also be a little pain considered the current waste of time trying to regain control on theses boxes.
If not possible, I highly suggest mikrotik to add a new special time to the reset button that basically do the same as /system reset-configuration no-defaults=yes
I though the netinstall script was just a one-time script. (not well documented)
I double-checked and It seems to be run on each system reset (software or button)
That’s cool.
What is strange is that it is still the original script which is displayed in /system default-configuration.
Is there a way to view this script inside routerOS ?
(could be a good or bad thing since it may embed cleartext passwords)
Is there a way to modify it thom the console without making a new netinstall ?
What will happen after a software upgrade ?
will a system reset-configuration still use my custom script ? or will it load the default that comes with the new routeros package ?
ROS upgrade will not modify the startup config / script.
Thats ok, but are you absolutely sure ?
I remembered that the default config changed on switch products when the new bridging system was introduced.
but it was the “real default”. Not a custom script pushed with netinstall.
What about the cAP mode on products that support it ?
Is there way to provide a caps-mode-script via netinstall ?
(or test the chosen mode from inside the script ?)
I agree w pcdwarf, here is a related thread i started requesting the same thing (ie return to the prior MT default-config ability to configure a brand-new device over eth1, even if done in a secure, time limited, or otherwise, way).