Is there some option to remove the quick set fields and buttons from the homepage of the router?
We use a number of MikroTik RB2011 as true routers in a meshed network, not the typical “port 1 is internet and the remainder is NATted to there” setup.
After configuration, the Quick Set page still comes up every time we login to the device, with fields marked red and a button “apply configuration” lurking to destroy the setup.
I fear a bit that one time it will be used to accidentally destroy the configuration.
On Wireless devices, which we also have, the home page shows a connect list of users and is quickly refreshed,
consuming bandwidth and CPU on the client while you are preparing your work.
Is there no way to remove those things and show a static homepage with only some static fields like the router name?
When we want to configure or debug something, we can use the menu.
Ok but that is not the problem. I don’t need to protect against malicious people, just against confusion and mishap.
E.g. someone in the team who is alerted by the error indications on the homepage and trying to correct them, or
wanting to click the “Search for updates” button and instead hitting “Apply configuration”.
At least the other menus scare the potential “modifier” away.
Veni, vidi, and that’s it. No urge to click anything with immediate consequences.
"Look! An error. Let’s click ‘Fix it’ "
If the operator has less than adequate knowledge, he should not be given access to the full configuration interface. I suggest considering the use of API to make a special program that only does what the operator needs to do, without distracting him with other menus.
The worst feature of quickset is that it is changing the configuration without hitting the apply button. Or at least it used to some time ago when I was checking it.
It is useful for dummies but really annoying for experienced users.
I would like to have it as separate package that I would automatically uninstall in every new device.
Quick Set IS great for individual installs in a home or small office setting but for larger scale deployments not so much. For me, the issue is mostly that I make a lot of “advanced” setting changes via scripts/api and find Quick Set page distracting. With Quick Set disabled the Interfaces page comes up first which is much more useful. The other reason is that Quick Set defaults to Router mode even if the device is actually configured as a bridge. If you forget to change the mode to Bridge, pressing Apply Configuration on the Quick Set page will alter the config to Router mode.
Now, I’m not complaining at all. I’m just highlighting a few reasons I push a skin that hides it to all my devices. What would be really cool though is the ability to configure Quick Set via script/api to include arbitrary items from any other page. Then I could configure it to display the items that my script sets and the status items applicable to my network.
Apparently I am unable to explain the nature of my worries to you.
I think I’ll let it rest, and see what the skin feature can do. It looks like other posters have understood what I mean.
In my opinion, there is always a trade off b/w advanced features and having a simple control panel.
It’s kinda having and enjoying the features of a 747 Boeing while preferring a simple control panel, say, of a single-engine Cessna.
My understanding is Quick Set is designed for simple config and, perhaps, as some sort of a quick summary. Advanced configuring should be done under specific tabs for flexibility and greater granularity.
A good compromise may be the switch to turn Quick Set on, or off. This way, new home users (?) are not alienated, who represent a growing strategic market segment of MT users.
MTeeker: that was what I was requesting, but I did not yet know the capabilities of the “Design Skin” feature then.
Now that I have experimented a bit on my own router it appears to be possible to do what I like.
Like you mention: it is not about shielding advanced features, but about shielding the simplified interface that makes
too many assumptions that are not valid for our config. (like “port 1 is internet, needs to be handled as special case”)
Well, I have been experimenting with Design Skin, and although in general it works in a very intuitive way and works well to hide menu items and tabs that are not required, the home page appears to be an exception to that…
I see many items with checkmarks that are not all appearing on the actual homepage, and some items for which there are no checkmarks. At the top there is a “show by default” checkmark that appears to affect the entire page.
Is there some place where this is documented? I could not find it in te Wiki documentation.
What do you mean the “Quick Set Page comes up every time we login”? Are you logging in via Winbox, WebFig, SSH?
I’m assuming that it is via WinBox where having a saved session at startup is quite possible. Solution is to change the session on the WinBox connection page. You can create a saved session from within WinBox that has whatever windows up that you want. Then in the Winbox connection screen, select the router to connect to, select the desired saved session, then use the Add/Set button to save that router and session combination to your saved routers.
WebFig.
In the latest version the QuickSet page has been moved to a separate “tab” and a browser cookie remembers the last
selected tab, but I still think there should be an option to disable QuickSet. The page can remain visible but it should
not make changes to the configuration when that option has been selected.
? The QuickSet is at least in user-friendly language, not like the Wireless Advanced menu, for example.