We have a script that configures RB951 & RB952 devices for CPE. We’ve recently decided to configure CAPsMAN by default to easily expand wireless coverage w/ APs when wireless coverage is less than the customer wants. We log into the device upon delivery to change router identity, SSID and WiFi password. When the interface comes up, whether WinBox or WebFig, initally the device mode is “Home AP Dual” or “WISP AP”, by the time the above items are changed, the system has reconfigured itself to mode “CAP”. This is NOT what we want, I’ve tried on 6.39.2 and 6.40.3, same results.
Is there a way to “lock” the mode from our setup script? I THINK it happens once the certificates are generated and the system moves the wireless interfaces to cap. Pressing “Apply” or “OK” to save the above settings when in CAP mode removes “router”, “local lan”, changes admin-mac… It has forced more than one truck role… Thoughts, advice, work-arounds welcome.
The mode is (I think) guessed by the quickset page based on what settings it finds in the config. There is no way to force it.
Your problem is that after some detailed config has been changed, the quickset page becomes a ticking timebomb waiting for disaster to happen.
I have complained about it several times, but nothing has happened. I think there should be a change to allow quickset only on an unconfigured router,
or at least a command to explicitly lock it. In WebFig the quickset page can be removed in “Design Skin” but unfortunately this also removes
its nice status display (especially valuable on wireless devices). What is required is a feature to still have the quickset page but rename
it to “status” and make all fields readonly. It hasn’t happened.
Figured the Design Skin would/could be the answer; went that way and it’ll work for setup. SafeMode mandatory if you click QuickSet in WinBox. tick, tick, tick… Agreed!
Any regular MikroTik admin should know that Quickset is only for the first setup of a new MikroTik device that is to be used in a simple, standard situation.
Once you have done refinement of the configuration in the menus one should NEVER change ANYTHING using Quickset!!
Not even the router identity or SSID. It will seriously foul up some of the custom config.
Always use the appropriate menu item (System->Identity and the Wireless menu).
However, when there is a small group of experienced admins and a large number of “technically interested” (end-)users, it will unavoidable that
people use Quickset and destroy the config. That is why it should be possible to block that. Or even better, the router should itself keep
some flag like “initial status”, “quickset done”, “detailed config done” and automatically disable Quickset write operations once detailed
config has been done (bringing it back only after reset-to-defaults has been done, maybe that one can remain active on the Quickset
screen as it is hopefully obvious to everyone that this could cause some surprises).