MikroTik

But...this is unfair:

They suggested to use CLI, it has syntax highlighting, but it's buggy as hell and unusable.

I don't think the the CLI /system/script/edit is "buggy".

:local var1
:local var2
:local var3
:local var4
:local var5
	:local var6
	:local var7
	:local var8
	:local var9
	:local var10
:local var11
:local var12
:local var13
:local var14
:local var15
:local var16
:local var17
:local var18
:local var19
:local var20

I use the editor from CLI via ssh, no issues there. So I do not agree about the RouterOS issue.

I use the editor from CLI via ssh, no issues there. So I do not agree about the RouterOS issue.

Same issues in PuTTY via SSH.

:put [:convert to=hex [/system/script/get SCRIPTNAME source]]

Simple suggestions related to Scripts screen in WinBox4

• Monospaced (Just in that text box field, for the alignment porpoise.)
• Line numbers (I imagine is piece of cake.)
• And XY cursor position. (Also piece of cake.)

To me, the TAB character feels like an archaic relic from a time when every single bit had to be carefully conserved.

Get some serious terminal emulator (not putty or winbox terminal). Then you won't see/have any issues.

The tab character is often preferred by those who want the flexibility to adjust indentation to their personal preference.

No proper error reporting, no way to end a script in the control flow without showing an error, no line numbers, no syntax check without running a script, no means for debugging except printing debug messages to log, etc.

Get some serious terminal emulator (not putty or winbox terminal). Then you won't see/have any issues.

KITTY

Ok, that hints that the bug is actually not in RouterOS but in the terminal emulator part of WinBox 4.
So those that claimed "not a WinBox bug, go away!" were probably wrong.

Maybe their SSH server is not fully compatible with Windows SSH clients.

What matters is the "terminal emulator", the part that sits on top of the SSH/TELNET/SERIAL connection and interprets the incoming characters.

You probably confused. Windows KiTTY is a PuTTY clone (or whatever - https://www.9bis.net/kitty/index.html).

I am talking about https://sw.kovidgoyal.net/kitty/

Get some WSL terminal and you are good - even on Windows. It is not a ROS bug per se. Maybe their SSH server is not fully compatible with Windows SSH clients.

In windows now, you can just start powershell or cmd and type in ssh admin@192.168.88.1, and you get connected.

As was said, it's a RouterOS bug.

@teslasystems I am not able to reproduce this bug. But I have to admit, I only have ROS 7.13.5 for testing this right now. Maybe the bug does not exist in that ROS version. I made sure to enter the TAB character and make terminal height as small as possible. But no matter how hard I try, I don't see this glitch.

No updates from 'Tik on Winbox? I hope they're going back to drawing board. It needs work, even as a beta [cough Alpha release]. Others are innovating and gaining market share. We're currently testing OPNSense hardware appliances.... also other vendors.

https://www.deciso.com/wp-content/uploa ... series.pdf

In your previous posts I have noticed you often refer to Palo Alto Networks, OPNSense and other Enterprise/SMB firewalls, I think you may be forgetting that Mikrotik's primary market is not as an enterprise firewall, and that they have almost 30 years of history making RouterOS.

RouterOS users have come to love the workflows that exist in WinBox and expect these. While WinBox 4 is not perfect, Mikrotik are taking our feedback seriously, where it makes sense and falls in line with their history as well as future vision.

I expect that over the beta period WinBox 4 will improve to the point where the workflows are similar to WinBox 3 and the majority of users will be able to daily-drive WinBox 4. Will it turn into an Enterprise Firewall style UI for the "Monkey Clicks Button" ex Desktop admin types ? I don't think so and I certainly hope not.

That's far more important than polishing the exteriour.

Main thing with Winbox 4 has to be getting rid of bugs that can cause data loss or mess up the configuration. That's far more important than polishing the exteriour.

I would love to see more advanced filtering, sorting , multi select/paste, export/import (csv/cleartext) features from every table, but especially from IP/Firewall.

• You log into a device that already has the rules you need and know they are OK, select only the entries you want, CTRL+C.
• You log into the device you want to apply the rules to, CTRL+V.
• And now, all you need to do is reorder the newly inserted rules.

Passwords are not shown on left side if address list is password-protected and is not unlocked. There was a bug related to this but it is fixed more than one release ago.

I would have an interesting proposition to implement. 📣
If you are already making a new Winbox, I would suggest that in one Winbox you could open connections to different routers, and switching between them was done using tabs - like in browsers. Of course, tabs placed in the title bar to make good use of space - like in most new browsers.

Different sessions in tabs inside same window can be acceptable idea if there is a choice to use same window or separate windows. The point of separate windows is ability to see different sessions simultaneously - which is not possible if they are in tabs of a single window like in web browser .Web browsers do have the ability to open multiple windows after all - so ability to use multiple windows should be normal to expect in case of Winbox as well...