This is just a small poll to see how people are configuring their RouterOS.

Winbox + CLI (in winbox)
Winbox GUI only

Would have been a better breakdown for winbox

Ups, all votes gone while updating poll. You can rewote.

Thought about clicking "Script", but did not.
我使用脚本很多,但对t常规任务he devices. For me this is not configuration.

I use winbox for day-to-day config work, but commandline to import blocks of standard configuration (e.g. firewall address lists or route filters).
Aside from situations where winbox is not supported, I normally do not use commandline except to make an export for later download and storage in versioning system.

This is just a small poll to see how people are configuring their RouterOS.

I mostly configure RouterOS device using WebFig and I'm not satisfied doing so, as you may guess, when using a GUI, it is very easy to forget to configure something (ie changing SSH port, ...).

I tried to configure using terminal or scripts but:
1. I find it quite hard to write idempotent scripts (ie scripts than can be run several times without any error),
2. you often face a chicken and egg problem (how can you change SSH settings from an SSH script ?) as there is no reload or reboot option I'm aware that would let you separate config edition from config implementation.

In other words, maybe I'm just saying "provisioning from scratch" with terminal is quite hard.

Another point is that many RouterOS have opiniated defaults such "ether1 has PoE-IN capability AND is acting as a WAN port".
It is not so easy to work around or against these defaults as you may need from time to time to factory reset your device.

RouterOS is capable OS overall, but if it's just what it can do, I can take some Linux distro and have the same and even more. The major difference is how easily I can do things. RouterOS CLI is already an improvement, because it provides consistent interface for all different things. And it's great for mass changes.

But WinBox takes it to whole new level, with its "WYSIWYG" and almost self-documenting approach. For example, if I want to add new firewall rule, it's just one click and I get all available options on silver platter, with understandable names, listed allowed values for some, etc. If I have at least basic understanding of networking, I don't even need manual for most of them. I fully understand why some people are so much disappointed by new routing filters in v7, because in terms of user friendliness it's huge step back.

And it doesn't end there. Things are live, rules have counters, you immediatelly see that something happens (or doesn't). Or ability to have several things open at once is huge advantage too. That's why WebFig, while not otherwise bad either, is no match for WinBox.

That's why WebFig, while not otherwise bad either, is no match for WinBox.

I'm still hoping for a WebFig that is just the same as WinBox. Sub-windows in a browser, dynamic updates. It can be done, see for example Synology NAS.

winbox is very good, it makes you understand

I mostly use winbox GUI + console, but as for "other": Serial console - It may be old-school method, but when you need it, YOU NEED IT.
It saved me having to go to remote sites many times. I always wire console from one ROS to another using null modem cable, so it's possible to access bootloader menu to do netinstall remotely or switch partitions to backup ROS install.
Too bad many devices don't have any accessible console (even though there is TTL UART on board, it's useless, there is no access to bootloader or ROS possible...WHY?).

I have template scripts that do the bulk of the work for new provisioning, but updates etc tend to be winbox gui - just really helps for multi tasking and having visual reference to objects and things you are doing in different parts of config like bridging and interfaces side by side or ppp and queues etc

I have a script to load a config and create a password for new clients I install, as for when I'm programming anything else I use primarily Winbox Gui unless it's faster to do it in terminal.