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".

I just said as it is. When I was trying to edit script source in CLI and navigating through the code using up/down arrows, it becomes a total mess. One part of a code may appear in another part of a window, some parts are clipped, some letters can be taken from one line and painted on another line, etc. It's unusable. And it's same in both v3 and v4, so it's a RouterOS problem, not WinBox.

UPD: not 100 % sure, but probably this happens when you have tab characters in the code.
For example, if you have this useless script (note tab characters in lines 6-10) and try to edit it in CLI, it looks ok initially
.
but then, if you scroll down below line 13, it looks like this:
.

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.
.

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.

I suspect if you look at the script source as hex or byte-array, you'll find some \t or \n without \r\n. If you find something in CLI editor wrong, it totally worth it to file a support case and let Mikrotik sort it out. But I suspect it's that other editor are more flexible on line-endings than /system/script/edit which uses RouterOS windows-style \r\n.

But that a different issue that part we likely all agree on fixed font and "colors"

Yes, there are tab characters (0x09), I said about them in my example.
From what I see, RouterOS doesn't erase previous background under tab character. I've mentiioned this issue after MT suggested to use CLI in my support ticket about adding syntax highlighting, but they just ignored it...

As I said in my previous post:

Simple suggestions related to Scripts screen in WinBox4

CLI editor in RouterOS, even on terminal of Winbox, its not a "WinBox4" thing.

So, please, Keep it simple(at least for a first try.). Stay focused on Script text field.

• 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.)

Well, of course there are two components involved in the editing:
- the RouterOS /system/script/edit
- the WinBOX terminal emulator
When the two are not operating well together, it is a bug that should be solved.
It is not yet clear in which of the two the bug is. Maybe someone who considers it important can test it further.

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

URXVT
KITTY

The bug is the same, well know...
do not use other characters than \r, \n <SPACE>! etc. until the ~ because on RouterOS are unsupported and rended differently on various terminal/winbox/script, etc.

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

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

The tab character is normally used for code readability.

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

Most posters here do not have SW development background, so we get those funny statements about "archaic tab characters".
As I think we can agree that script edit in Winbox terminal should not mess up the code layout scrolling up and down in script code. So let's treat this as a bug report. Same for using proportional fonts in script edit boxes in Winbox.

At least for end users (I suppose MT has something better internally to create large default config scripts) scripting beyond a few simple lines always was hard: 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.

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.

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

Any other TAB width than 8 is seriously broken!
It usually isn't workable to change indentation by changing TAB width anyway, e.g. due to comments in the right margin.
Today, often TAB is converted to the proper amount of spaces immediately on input, so you don't have to worry about it later....

Yes, this is more a TAB vs SPACES debate. It should be possible to use TABs and not mess the output of Winbox Terminal window.

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.

Fully agree, but error reporting was recently improved a lot by adding line and character number to error log message. This really simplifies debugging compared to previous behavior.

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.

Tried KiTTY, same stuff. You are doing something wrong. It's a RouterOS bug, not WinBox terminal or other terminal.
.

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.

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

This is not an SSH level problem! SSH is only responsible for secure transport of the terminal bytestream, a successor to TELNET.
(in the old days we used serial RS232 lines for the same purpose)

What matters is the "terminal emulator", the part that sits on top of the SSH/TELNET/SERIAL connection and interprets the incoming characters. When it sees a hex 41 it displays an A. When it sees a hex 20 it shows a space.
What matters here is what it does when it sees a 09 (TAB). And of course other sequences like ESC [ n; n; C that control the cursor position, text and background color, etc.
There are "test programs" that generate complicated sequences to test if a terminal emulator works according to (ANSI) standard.

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

From my experience, I would have said the same. I worked with Windows for a long time (back when WSL didn’t exist) and had countless display issues with PuTTY/Kitty - just terrible. But I had to live with. Since switching to Linux for work, I’ve never had such problems again. I’m not talking specifically about ROS and SSH, but SSH connections to servers in general. I think using WSL with any terminal emulator should also work without issues.

In windows now, you can just start powershell or cmd and type in ssh admin@192.168.88.1, and you get connected.
These terminal windows has some support for ANSI, to support the ESC commands.
Windows now even comes with openssh server if you wish to connect your computer via ssh.
If you start powershell as Administrator, and put these powershell commands you be fine.

In Linux, the functionality of "terminal emulator" and "ssh connection" are completely separate.
You start a terminal emulator like xfce4-terminal or Konsole or xterm or whatever you like, usually with a shell running in it, and from there you start a connection using ssh or telnet or minicom or whatever. You can combine them in any way you want to.
In Windows, those two functions tend to be integrated in one program (like PuTTY or telnet.exe) and of course are of substandard quality.
It would be interesting to try the above method of setting up an ssh session from Windows and see how it performs with the script editor.

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.

OK, tried on Ubuntu, here it is:

urxvt:
.
kitty:
.
And same stuff happens when connecting to the router via physical serial port, so it's not related to ssh.

As was said, it's a RouterOS bug.

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

Thank you, didn't know about that. Anyway, the mentioned bug has a place in powershell also.

As was said, it's a RouterOS bug.

Maybe. No point arguing here. Open a new ticket with the exact problem you're see... since, yes, sometime it does take a few rounds in a ticket to convince them. But they do fix something if there is clear repo case in a ticket.

Feature request: allow the user to add custom buttons to the toolbar (stored in the workspace file) that run a specified RouterOS command when clicked.
Minimal implementation would be to specify a custom button with only a "text", which would then do a /system/script/run "text".
So you can make a script "backup" and add a button "backup" to the toolbar, when clicked it would run the script to make a backup.
(more versatile could be to have separate specification of the button text and the full RouterOS command to run when clicked)

is there any change to
have winbox,dude,netinstall and other utilities on aarch64 ?

thanks

This new version UI is very interesting. But I missed some features from v3.
1. Inline comment for separated windows (not global)
2. Table sort based on 2 columns like v3. Now I can only sort 1 column at a time and it is difficult to monitor.
3. Option to wrap text, allow change width and height for each table. some content is wrapped, some don't

@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.

@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.

In 7.13.5 it's unstable. Sometimes the problem appears, sometimes not. Depends on terminal window height, but doesn't depend on terminal itself, it's same in all SSH clients and WinBox. Also noticed, that in this version one extra empty line is added after each line. Strange.
Anyway, reported once again about this issue.

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

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

I don't think they are going back to the drawing board, they have a good foundation with WinBox 4.

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.

Thank you for your post, nz_monkey

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.

While I agree that Winbox does not need to get similar to any other firewall management client, it would certainly be clever for MT to watch, how others are designing their user interfaces.
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.

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.

If one calls real enterprise grade equipment interfaces "monkey-clicks-button" then Mikrotik can be perceived as complete toy - at least what comes to logging, log filtering and lack of any analyzing tools. Of course both of these statements are not exactly true...

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.

That's far more important than polishing the exteriour.

When exterior is unusable by design, I don't see much sense in doing anything else...

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've use WinBox4 since it came out and never find the need to use WinBox3... while it certainly missing new/improved functionality, many quibbles about tabs/dialog/keyboard/etc/etc, or even questioning need to re-create the same winbox (*when a new Dude/controller was the need).

But in fairness... WinBox4 is pretty "stable" and "data loss" has been NOT been a major or even minor issue. Now, I cannot say same about iOS app... that I feel is "risky" for data loss - but have NOT see "data loss" in WinBox4.

Log filtering doesn't return results, although the filtered item size shows on the bottom part of the window

I had the same problem and was ready to write a ticket - but after next login it started to work again. There's definitely something not quite right in log display window

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.

One thing I would love?

Select items from a grid of configuration items, press CTRL+C, and it will copy-paste the selected items into the buffer as a "/export terse".

A practical example of use with Firewall Rules:

• 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.

Note: And if do a CTRL+V on a text editor, it would paste the "export" text in the buffer on the text editor.

But it is important to think about doing this in the entire Winbox4 Framework.
Everywhere that has a grid of configuration items, this should be possible.

Obviously, this is not a simple thing to do! Even narrowing the scope as I exemplified in the case of Firewall rules is already somewhat complex. Imagine for other scenarios, for example in grids that have persistent configuration items, and dynamic items such as Routes, Queues, DHCP-Leases.

Well, I'm not bringing the complete solution here.
Just a feature request.

P.S.: Some other vendors, in their management consoles, have similar features. I'm trying to remember exactly which one, but I think it was the old Cisco PIX console. Or was it ForcePoint? I don't remember... But I remember that the Objects came out in text in a "weird" format, I think it was an XML with a MIME, or something like that.

Well, the whole topic of "how do I setup a number of similar routers" and "how do I migrate my existing router config to the new shiny box that I bought" certainly deserves a bit more attention!
For skilled users it is possible to export a config, edit it, and paste it into a new router terminal window. But for the average person that is far too difficult.
Even pasting "additional config" that I generate on a website for users of our network proves to be too much, usually when I get contacted to solve their problems it turns out they have pasted the config multiple times. In some places that results in unused extra lines (e.g. firewall, routing filters), in some places that results in outright errors (routing tables), and generally it does not work well.
And our users are technical (but usually not network-technical) people.

Apologies if this has been covered here before, or if there is a more appropriate place to post feedback about Winbox4.

What I'm wondering is whether a preference can be included to *not* pre-populate the connection settings on the left with the last-used address, credentials, etc.

Maybe I'm missing something obvious but this would appear to be a security issue for password-protected, saved connection configurations.

Cheers.

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 don't know where to report this but in winbox4 (in winbox3 works normally) in wndows like dhcp-server / leases and firewall / filter, Ctrl+D and Ctrl+E doesn't disable and enable rules, and it's frustrating because i have muscle memory for quick disabling of rules for testing and others. pls fix, Thanks!

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.

The last-used connection details are populated on the left on startup. The password is not shown but it present. One needs only to click CONNECT to use the last-used connection details.

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.

For me personally adding "inline comments" globally is not the best idea. Sometimes I prefer inline comments, like in "address-list", but on the other hand I don't like them in "filter rules".

I proposed that some weeks ago, it would be quite useful, definitely something that might improve cleanliness in our desktop.
I agree on the "inline comments" as well, it's not one-fit-all.

+1 for tabs.

Just because I don't like how Gnome or Windows manage multi-window'ed applications. KDE is almost adequate :-)

So, tabs with a simple tab search function would help a lot in most environments IMHO :-)

Menu files
Copy and drop doesn't work

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...

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...

Safe-Mode is the best example for that.
On session can be over Safe-Mode, but other can be not on Safe-Mode.

To me, it is very frequent to have two sessions simultaneously on the same router.
Especially over CLI.

I would like to love winbox 4 but my muscle memory is just too strong from winbox 3.. but keep,up,good work

First, I want to say that having a winbox version for Linux is very much appreciated.

I don't know if it's also like that on Windows, but the "save password" feature on the connection menu is honestly non-existant. Everything is stored in plain text to "~/.local/share/MikroTik/WinBox/Addresses.cdb". It doesn't need to be some infallible quantum safe solution, but at least something that would put the risk on the password strength instead of relying on the good security practices of people.

As it is now, I think it would be preferable to remove the option entirely until a better solution is implemented.
You could, for example, make use of `mkpassword` somehow to hash the password before writing it to the file, use pgp to encrypt the whole thing or simply remove it.

To verify my claim: Thank you,

Yes, encryption funcion is not yet implemented, but you can open WinBox3, set "Master Password", then use WInbox4 and passwords will be encrypted

Do you mean that we do that in winbox3 BEFORE we import the addresses into winbox4?
Or does it mean that it is safe to share the Addresses.cdb file between winbox3 and winbox4 e.g. using a symbolic link?

Winbox IPv6 connectivity, when?
Its 2025, i shouldn't have to resort to IPv4 to manage an IPv6 forwarding device.

With today's networking libraries you actually have to make effort to NOT support IPv6...
(like unnecessarily "validating" addresses before handing them over to the library)

IPv6 connection does work if address is put in brackets like this It is same with WinBox 3 and WinBox4

Winbox IPv6 connectivity, when?
Its 2025, i shouldn't have to resort to IPv4 to manage an IPv6 forwarding device.

this is already here for ages

Just a quick question for those software developers out there...

What is a reasonable time frame to complete a beta to official? I know it took GIMP 7 years to migrate from 2.10 to 3, but they were an incredibly small team of volunteers who contributed as they could. MT have been working on v4 since last August - almost a year now and still haven't got close to an official release. And they are a commercial outfit with paid staff presumably working 40 hours a week on the project.

If we are lucky, we might see one update every few weeks, which for reasons just given seems to me to be unacceptable.

There maybe those who argue that this is free software, but I would contend that it's not. My reasoning being that it's a utlity that is required to configure devices we buy. In other words, we pay for Winbox when we buy MT products. We can't use Winbox with any other products. So, yes, we pay for Winbox.

So, I'm really curious how this works in a software dev world. What is the reasonable time frame between a beta release and an official release? Is there even such a thing?

Don't get me wrong, I'm happy to have Winbox - especially for Linux, but the time frame for at least releasing updates (let alone finalising the release) seem to be taking the piss a bit.

Cheers.

What is a reasonable time frame to complete a beta to official? I know it took GIMP 7 years to migrate from 2.10 to 3, but they were an incredibly small team of volunteers who contributed as they could. MT have been working on v4 since last August - almost a year now and still haven't got close to an official release. And they are a commercial outfit with paid staff presumably working 40 hours a week on the project.

We don't know how many developers are on the project, how many hours a week they spend on it, and if it even is a project with defined specifications and delivery time...
It may well be a sidejob of one or two people working at support, and dividing up their time between handling tickets and working on this.
Also, when working in a company there always tend to be distractions like "important customers who need something quickly".

We don't know how many developers are on the project, how many hours a week they spend on it, and if it even is a project with defined specifications and delivery time...
It may well be a sidejob of one or two people working at support, and dividing up their time between handling tickets and working on this.
Also, when working in a company there always tend to be distractions like "important customers who need something quickly".

Thanks for your very reasoned reply. Maybe then, considering the time this has taken already, the smart money would be allocating 1-2 full-time staff to the project until final release? That way, what might take many, many more months or years currently, might only take a few weeks instead. That way they get a release out in short order satifying their customer base, and then those who were working on this project could be seconded elsewhere.

What MT risk is the longer this takes the more likely their customer base will shrink, if it's not already happening. I suspect they don't really care though about customer retention.

Your assumption is that customers buy their MikroTik hardware (or do not walk away from MikroTik) based on the existence of a new version of WinBox... but that isn't necessarily true.
I am using winbox3 for production use myself, and only try winbox4 now and then to see how it develops.
Other users prefer to use WebFig or CLI. It is not like WinBox 4 is critical software.
Personally I would be happier when developers worked on BGP bug fixes (especially after 7.16), each has their own preference.

That's right, it's not critical for now. Moreover, it's unusable for now. But if MT won't change this sh*tty design, and if some day WinBox 3 will become a brick, then their customer base will probably decrease a little bit. At least -1 (me).

Since I could not find any list of requirements to run WinBox on linux, and since it is specifically a bit of a pain on Fedora to determine all of the necessary packages, I will post the list of packages I needed to install here. All were available in default repos.

libxkbcommon
libxkbcommon-x11
libxcb
xcb-util-renderutil
xcb-util-keysyms
xcb-util-image
xcb-util-wm

There may have been more packages needed that I already had installed but I think it's likely this covers it. I am running a very fresh install of fedora xfce.

If you do this, you can see what libs being used and loaded.
Have removed the links in this list though.

MT have been working on v4 since last August - almost a year now and still haven't got close to an official release.

MikroTik will one day, out the blue, just promote Winbox to be out of beta, even if there will most certainly be tons of issues, bugs, missing features, etc.

That's just the way they do software.

If it works for you, be happy that it exists. Don't expect anything. It may take a week for something you need to be implemented, or it may take years or never. You can never be sure with MikroTik.

If it doesn't work for you (like me), then be happy for as long as Winbox v3 works with ROS.
There will be a point that ROS will no longer support Winbox v3 forcing everyone to downgrade to v4, and then I'll probably be on the same boat as teslasystems. -2.

I don't care one bit about looks and native Linux/Mac support (v3 under wine works perfectly fine for me).
I only care about usability functionality and productivity. Anything that messes up my productivity workflow (which has developed over 21 years of muscle memory with winbox) is not welcome, no matter how "modern" or "fancy" it looks. In fact almost always modernity and looks get in the way of usability and productivity.
This is what happens when kids that have only known smartphone touchscreens enter the software development workforce and try to bring their bad habits developed on their smartphones, to decades old established desktop UI paradigms, destroying everything in their path.

Winbox 4 is still shit to me. Heavy, slow, terrible UI/UX design choices and colors, and in the end of the day, not a tool to do business, but a toy to configure home routers for enthusiasts that will log in a couple of times to their router every 6 months.
Tools are used every day for hours and hours on end. Toys are used for a few minutes.

So far Winbox 4 is a toy (ie some intern's experiment that happened to know a bit Qt), not a tool to do business every day, all day.

Sign under every word. But no one hears...

For the record, I still think WinBox4 is BETTER than WinBox3. I use WinBox4 daily without operational issues. The fact WinBox4 loads way faster than Wine+WinBox3 is more than enough to accept the small different vertical vs horizontal tabs, color schemes, etc.

I'll offer we DO use less Mikrotik than we used too... BUT that has nothing to do with WinBox4. So I'm more with the gist of @pe1chl commentary on RouterOS bugs. And generally
engineering resources could have been better utilized than on a "cross-platform winbox"

But the [slow-moving] ship sailed LONG AGO on that, so I doubt repeating same commentary is going to causes Mikrotik to return the drawing-board.
And I'd imagine the "open issues" in post 1 be a reasonable assumption what Mikrotik thinks a "final" WinBox4 might look like.

If you do this, you can see what libs being used and loaded.
Have removed the links in this list though.

Code: Select all

ldd WinBox | cut -f2 | cut -f1 -d' ' | sort
/lib64/ld-linux-x86-64.so.2
libbrotlicommon.so.1
libbrotlidec.so.1... etc

The issue with that is that many distributors name their packages differently from the actual library file names they contain.
So you still would need to convert those .so.1 names to package names, different for each distribution (yay linux!).

That being said, I encountered no issue when running WinBox 4 on two "certainly not maxed-out" Debian Xfce installs.
Apparently all of those libraries already were installed for different packages I have on the system.

One thing keeping me from using WinBox 4 on my work system is that it does not work on the Xtightvnc X server that I use there.
My work Linux machine runs on a VMware server and I connect to it using VNC. The install is bullseye, still did not get around to upgrading it to see if it is magically solved.

I think for the price, v4 WinBox is great. Sure, it still needs a "lot" of work, but what ROS product doesn't.
But still, other than my time (which I guess, is still worth something), I don't have anything financially invested in it.
I do use the Mac version which I find fast (and much quicker than using Crossover), but still needs a lot of work.
I hope they make a few needed changes shortly, but I guess I can wait.
If they suddenly decide to put a price on it, then I probably would have something meaningful to say about it.
Till then, I just sigh, and plod on.. 😎

I don't have anything financially invested in it... If they suddenly decide to put a price on it, then I probably would have something meaningful to say about it.

Um, every time you buy a MT product, you invest in it. That is the price they put on it. So perhaps this is the time to "have something meaningful to say about it"?

One thing keeping me from using WinBox 4 on my work system is that it does not work on the Xtightvnc X server that I use there.
My work Linux machine runs on a VMware server and I connect to it using VNC. The install is bullseye, still did not get around to upgrading it to see if it is magically solved.

Today I upgraded it to Debian bookworm and the issue is resolved, so now I can migrate to WinBox 4.

Today I upgraded it to Debian bookworm and the issue is resolved, so now I can migrate to WinBox 4.

What were You using? I had no issues with OpenSuse Leap 15.6

Please read. The system was upgraded from Debian bullseye to Debian bookworm.
The issue was that on Xtightvnc the window of WinBox 4 could not be enlarged above a certain size.
As my desktop is 1600x1200 it would not allow to fullscreen the window, it looks like it crashed at about 1 megapixel.
(the error was "Warning: Ignoring window icon 1048578 exceeds maximum xcb request length 1048575 (:0, )")
I could not find a way to increase that maximum xcb request length but it looks like in bookworm it is higher.

The issue was that on Xtightvnc the window of WinBox 4 could not be enlarged above a certain size.
As my desktop is 1600x1200 it would not allow to fullscreen the window, it looks like it crashed at about 1 megapixel.

Weird, I run dual screens at 1440p and didn't got this one. Yes, using X11 too: no Wayland here. More specifically, I'm using xorg-x11-server-21.1.11

The development of winbox 4 is going very slowly.

I'm using xorg-x11-server-21.1.11

Is it so difficult to read? The issue occurred with Xtightvnc. That is an X server that has no physical screen but can be connected using VNC. Kind of terminal server solution.
With the normal X11 server this issue did not occur. I presume there is some way to set the max xcb request length but I have not been able to find it, and likely the compiled-in default was too low and has been changed now.

I guess Mikrotik underestimated how much work it is to rewrite Winbox - especially when disrupting several workflows and dismissing/ignoring industry UI/UX standards.

May I ask why using Xtightvnc is that because of using some game OS like Windows :), when you can use ssh with forward X11 ?
Maybe it can be solved with WSL2 in Windows ? I don't know.
I have heard that WSL2 have support for translating X11 to WinAPI.

I get it why using a server to secure with a bastion host.
And why not also secure the bastion with some hardware key like Yubikey.

No need for WSL, Xming or X-Win32 (commercial) can do that.

No need for WSL, Xming or X-Win32 (commercial) can do that.

My goal was with my answer was not to add more external programs to the stack.

May I ask why using Xtightvnc is that because of using some game OS like Windows :), when you can use ssh with forward X11 ?
Maybe it can be solved with WSL2 in Windows ? I don't know.
I have heard that WSL2 have support for translating X11 to WinAPI.

I use this because I can leave the Linux system powered 24h/day (on the server) and access it from my Windows workstation at work, or my home Linux system (via VPN), while all programs remain running. (on 20-desktop Xfce)
I used a solution that allows a similar virtual X server and then forwards the X11 protocol (I forgot the name), but it causes problems when you accidentally open something that has "nice visual effects" (e.g. in the browser) or otherwise causes a lot of screen updates.
With VNC the screen updates never go faster than the "poll rate", any other changes are discarded.
When forwarding X11 protocol, your session can get very much "behind" when there are lots of updates, and the system becomes unusable over a "slow" connection.

Is it so difficult to read? The issue occurred with Xtightvnc. That is an X server that has no physical screen but can be connected using VNC. Kind of terminal server solution.
With the normal X11 server this issue did not occur. I presume there is some way to set the max xcb request length but I have not been able to find it, and likely the compiled-in default was too low and has been changed now.

Yes, yes, sorry. Misread. Hold your horses, will you?

What's new in 4.0beta19:

*) updated Files menu for future RouterOS versions
*) use specific file browse widget for file selection fields
*) try to restore table scroll position when possible
*) do not send dynamically hidden fields

@EdPa - Can you please elaborate on:
*) use specific file browse widget for file selection fields

I still get the generic file browse popup (Linux / Gnome 48) when trying to download file from MikroTik device.

Thank you.

What's new in 4.0beta19:

*) updated Files menu for future RouterOS versions
*) use specific file browse widget for file selection fields
*) try to restore table scroll position when possible
*) do not send dynamically hidden fields

Connecting to RoMON neighbors has quit working after upgrading to 4.0beta19 (MacOS). The initial RoMON connection to a router can be established but connections to a neighbor cannot.

Rolled back to 4.0beta18.

I still get the generic file browse popup (Linux / Gnome 48) when trying to download file from MikroTik device.

It is used for "file" configuration fields, like in System - Certificate - Import - File Name (drop down).

Connecting to RoMON neighbors has quit working after upgrading to 4.0beta19 (MacOS). The initial RoMON connection to a router can be established but connections to a neighbor cannot.

Rolled back to 4.0beta18.

Yes it does not work. All you get is being stuck at "Connecting via RoMON". It does seem to be the case with Windows as well.

Target device indicates successful RoMON login event in log while WinBox is not able to proceed from "Connecting..." view.

Connecting to RoMON neighbors has quit working after upgrading to 4.0beta19 (MacOS). The initial RoMON connection to a router can be established but connections to a neighbor cannot.

Yes it does not work. All you get is being stuck at "Connecting via RoMON". It does seem to be the case with Windows as well.
Target device indicates successful RoMON login event in log while WinBox is not able to proceed from "Connecting..." view.

Can confirm same on 4.0beta19, using RouterOS 7.19beta6 (and others) on both RoMON server and the RoMON device. Even devices on same LAN segment don't connect via RoMON. And as noted you can "connect to romon" and get list of RoMON devices, but when you try to connect to any found RoMON things, it hangs.

Hi!
I tried running the new Winbox on Linux (rolling release EndeavourOS), but I only get the following error: I ran the previous beta without an issue. Did someone else try this release on Linux?

Hi!
I tried running the new Winbox on Linux (rolling release EndeavourOS), but I only get the following error:

Code: Select all

[peter@kk-pc-peter Desktop]$ ./WinBox 
APP,INFO: version: "4.0beta19"
APP,INFO: loading addrs db from: "/home/peter/.local/share/MikroTik/WinBox/Addresses.cdb"
APP,INFO: loading ok
Warning: QGLXContext: Failed to create dummy context (:0, )
Warning: QRhiGles2: Failed to create temporary context (:0, )
Warning: QRhiGles2: Failed to create context (:0, )
Warning: Failed to create RHI (backend 2) (:0, )
Fatal: Failed to initialize graphics backend for OpenGL. (:0, )
Aborted (core dumped)

I ran the previous beta without an issue. Did someone else try this release on Linux?

I upgraded previous verison by yay command in Linux Manjaro. It works for me.

Connecting to RoMON neighbors has quit working after upgrading to 4.0beta19 (MacOS). The initial RoMON connection to a router can be established but connections to a neighbor cannot.

I also encountered this problem

I upgraded previous verison by yay command in Linux Manjaro. It works for me.

Thanks! I just needed a reboot, probably the last upgrade attempt has broken Nvidia GLX support as glxinfo has also complained. Clearly not an issue with Winbox.

I still get the generic file browse popup (Linux / Gnome 48) when trying to download file from MikroTik device.

It is used for "file" configuration fields, like in System - Certificate - Import - File Name (drop down).

Thank you for clarification.

Would you guys consider using some other file browser widget or even opt for default OS widget? It is not very convenient to upload/download files from router, especially, when destination folder is somewhere deep in folder structure.

Connecting to RoMON neighbors has quit working after upgrading to 4.0beta19 (MacOS). The initial RoMON connection to a router can be established but connections to a neighbor cannot.
Rolled back to 4.0beta18.

Same issue and fix on Windows.

RoMON appears to be broken in 4.0beta19

What's new in 4.0beta20:

*) fix RoMON connect (introduced in v4.0beta19)
*) fix table column sorting by string in some cases
*) Login: ESC button cancels connection process

I can connect to router using RoMon, the available devices within that network that have RoMon enabled seem to show up. I can connect to any of them but am unable to save the RoMon "agent" to that entry, or it least it doesn't seem to. Using the Legacy 3.x Inbox, it did show whether or not a RoMon agent was save with the entry but I can't seem to find it using 4.xx (Using MacOS).

What's new in 4.0beta20:

*) fix table column sorting by string in some cases

Better ...

Gateway in route list sorts by IP but if the value is a text then random order is used.
For Immediate gateway sort mixes numbers, text in an unexpected way.

*) fix RoMON connect (introduced in v4.0beta19)

Fixed for me. Thanks.

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.

While I agree that Winbox does not need to get similar to any other firewall management client, it would certainly be clever for MT to watch, how others are designing their user interfaces.
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.

A +1 by me to this. Winbox users would benefit from some serious table management functionality. Multiple column sorting, for one. This was present in Winbox 3 bust still missing in Winbox 4.

Hello,

Can you please add "new window" option in ping window like you have in old winbox? This will help a lot form my work. TY

Over a month and only a small change/bug fix release on Winbox4 from MikroTik? I hope the team is taking other considerations for the software and innovation

Unifi just released 9.1...... They are laser focused on improvements and features based on user feedback. Perhaps these are signs they're planning to leave the consumer market and focus more on professional/enterprise. Perhaps MikroTik should do the same. There's no money in consumer hardware; leave that to the other vendors slinging cheap network hardware.

Over a month and only a small change/bug fix release on Winbox4 from MikroTik? I hope the team is taking other considerations for the software and innovation

+1 - My sentiment exactly. I wonder how often they check the original post and check off things that have been done and then prioritise what remains? Because there is still a lot that remains from that list to complete. LTE signal graphs are one. Weeks to wait and only a few improvements? Really? A published roadmap would be a great idea showing what successive releases they are planning to implement the remaining changes/features.

I wonder if YOU are reading the post and see if that topic has been discussed before?

WinBox 4.0beta20 running on MacOS 15.4.1 on MacBook Pro with M2 CPU.

Is anyone else experiencing application crashes when either disconnecting a login session or when quitting the WinBox application?

Yes it has been happening since first betas on macOS

I can connect to router using RoMon, the available devices within that network that have RoMon enabled seem to show up. I can connect to any of them but am unable to save the RoMon "agent" to that entry, or it least it doesn't seem to. Using the Legacy 3.x Inbox, it did show whether or not a RoMon agent was save with the entry but I can't seem to find it using 4.xx (Using MacOS).

Im having the same problem. It is impossible to save romon agent for a device. It worked before in the earlier versions of winbox 4,

What's new in 4.0beta19:

*) updated Files menu for future RouterOS versions
*) use specific file browse widget for file selection fields
*) try to restore table scroll position when possible
*) do not send dynamically hidden fields

Probably the last option dropped the "advanced" button in wireless interface.
Is the only option the command line or there is an "hidden" feature to tell Winbox4 to show also "advanced" button?
P.S.
+1 for tab instead of drop-down boxes

Strange behavior: for example, if I change a value in the Capsman Accesslist and save it, the old value is still displayed in the list until I change the view and then switch back ... anyone else ? (MacOS)

Anyone facing crash when clicked on PPPOE SCAN on 4.0beta20 on M1 MAC?

Every time I click on appears "WinBox quit unexpectedly."

here is the log



-------------------------------------
Translated Report (Full Report Below)
-------------------------------------

Process: WinBox [33276]
Path: /Applications/WinBox.app/Contents/MacOS/WinBox
Identifier: com.mikrotik.winbox
Version: 4.0.98020 (4.0.98020)
Code Type: ARM-64 (Native)
Parent Process: launchd [1]
User ID: 501

Date/Time: 2025-05-02 21:04:24.5518 +0200
OS Version: macOS 15.3.2 (24D81)
Report Version: 12
Anonymous UUID: 8EAD5DC0-CED7-7B76-8564-F9A0CC94E42C

Sleep/Wake UUID: 9A7B7F36-A9D8-4895-A2DC-83ED096D1359

Time Awake Since Boot: 220000 seconds
Time Since Wake: 1247 seconds

System Integrity Protection: enabled

Crashed Thread: 0 Dispatch queue: com.apple.main-thread

Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000

Termination Reason: Namespace SIGNAL, Code 6 Abort trap: 6
Terminating Process: WinBox [33276]

Application Specific Information:
abort() called


Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 libsystem_kernel.dylib 0x1958d7720 __pthread_kill + 8
1 libsystem_pthread.dylib 0x19590ff70 pthread_kill + 288
2 libsystem_c.dylib 0x19581c908 abort + 128
3 WinBox 0x105a60f38 ASlotRef::lazyInit(CType*, bool) const + 196
4 WinBox 0x105a75480 0x104088000 + 27186304
5 WinBox 0x10599f33c MdiWindowObj::MdiWindowObj(std::__1::unique_ptr<ViewModel, std::__1::default_delete<ViewModel>>, unsigned int, nv::message, QString) + 832
6 WinBox 0x105a67204 0x104088000 + 27128324
7 WinBox 0x105a72508 0x104088000 + 27174152
8 WinBox 0x1059e3250 0x104088000 + 26587728
9 WinBox 0x105956c84 MenuButtonWidget::qt_metacall(QMetaObject::Call, int, void**) + 288
10 WinBox 0x1044333b4 0x104088000 + 3847092
11 WinBox 0x10442457c 0x104088000 + 3786108
12 WinBox 0x1044237b8 0x104088000 + 3782584
13 WinBox 0x1044b46c4 0x104088000 + 4376260
14 WinBox 0x105c50e90 0x104088000 + 29134480
15 WinBox 0x10448a324 0x104088000 + 4203300
16 WinBox 0x104489a84 0x104088000 + 4201092
17 WinBox 0x1043d911c 0x104088000 + 3477788
18 WinBox 0x104512c6c 0x104088000 + 4762732
19 WinBox 0x1044c86dc 0x104088000 + 4458204
20 WinBox 0x1044c8d0c 0x104088000 + 4459788
21 WinBox 0x104536c94 0x104088000 + 4910228
22 WinBox 0x1041456a4 0x104088000 + 775844
23 WinBox 0x104d90e80 0x104088000 + 13667968
24 WinBox 0x104daa0ec 0x104088000 + 13770988
25 WinBox 0x104747308 0x104088000 + 7074568
26 WinBox 0x1051279dc 0x104088000 + 17431004
27 WinBox 0x105128918 0x104088000 + 17434904
28 WinBox 0x1040ff4b0 0x104088000 + 488624
29 WinBox 0x1048b3260 0x104088000 + 8565344
30 WinBox 0x1048b280c 0x104088000 + 8562700
31 WinBox 0x1048ae2cc 0x104088000 + 8544972
32 WinBox 0x1048ac51c 0x104088000 + 8537372
33 WinBox 0x1048abc5c 0x104088000 + 8535132
34 WinBox 0x1047d22d4 0x104088000 + 7643860
35 WinBox 0x1047e0870 0x104088000 + 7702640
36 WinBox 0x1051279dc 0x104088000 + 17431004
37 WinBox 0x105128918 0x104088000 + 17434904
38 WinBox 0x1040ff4b0 0x104088000 + 488624
39 WinBox 0x1054cbfec 0x104088000 + 21250028
40 WinBox 0x10550a650 0x104088000 + 21505616
41 WinBox 0x104bb2a70 0x104088000 + 11709040
42 CoreFoundation 0x1959f88a4 __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 28
43 CoreFoundation 0x1959f8838 __CFRunLoopDoSource0 + 176
44 CoreFoundation 0x1959f859c __CFRunLoopDoSources0 + 244
45 CoreFoundation 0x1959f7138 __CFRunLoopRun + 840
46 CoreFoundation 0x1959f6734 CFRunLoopRunSpecific + 588
47 HIToolbox 0x1a0f65530 RunCurrentEventLoopInMode + 292
48 HIToolbox 0x1a0f6b17c ReceiveNextEventCommon + 216
49 HIToolbox 0x1a0f6b508 _BlockUntilNextEventMatchingListInModeWithFilter + 76
50 AppKit 0x19956e848 _DPSNextEvent + 660
51 AppKit 0x199ed4c24 -[NSApplication(NSEventRouting) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 688
52 AppKit 0x199561874 -[NSApplication run] + 480
53 WinBox 0x104bb04f4 0x104088000 + 11699444
54 WinBox 0x1041088ec 0x104088000 + 526572
55 WinBox 0x1040ffb98 0x104088000 + 490392
56 WinBox 0x10597420c main + 13600
57 dyld 0x195590274 start + 2840

Thread 1:
0 libsystem_pthread.dylib 0x19590b0e8 start_wqthread + 0

Thread 2:
0 libsystem_pthread.dylib 0x19590b0e8 start_wqthread + 0

Thread 3:: QQmlThread
0 libsystem_kernel.dylib 0x1958d7830 poll + 8
1 WinBox 0x10423594c 0x104088000 + 1759564
2 WinBox 0x10423919c 0x104088000 + 1773980
3 WinBox 0x1041088ec 0x104088000 + 526572
4 WinBox 0x1041bed48 0x104088000 + 1273160
5 WinBox 0x1042373a8 0x104088000 + 1766312
6 libsystem_pthread.dylib 0x1959102e4 _pthread_start + 136
7 libsystem_pthread.dylib 0x19590b0fc thread_start + 8

Thread 4:: QNetworkAccessManager thread
0 libsystem_kernel.dylib 0x1958d7830 poll + 8
1 WinBox 0x1042359a8 0x104088000 + 1759656
2 WinBox 0x10423919c 0x104088000 + 1773980
3 WinBox 0x1041088ec 0x104088000 + 526572
4 WinBox 0x1041bed48 0x104088000 + 1273160
5 WinBox 0x1042373a8 0x104088000 + 1766312
6 libsystem_pthread.dylib 0x1959102e4 _pthread_start + 136
7 libsystem_pthread.dylib 0x19590b0fc thread_start + 8

Thread 5:: QQuickPixmapReader
0 libsystem_kernel.dylib 0x1958d7830 poll + 8
1 WinBox 0x10423594c 0x104088000 + 1759564
2 WinBox 0x10423919c 0x104088000 + 1773980
3 WinBox 0x1041088ec 0x104088000 + 526572
4 WinBox 0x1041bed48 0x104088000 + 1273160
5 WinBox 0x1048c41d4 0x104088000 + 8634836
6 WinBox 0x1042373a8 0x104088000 + 1766312
7 libsystem_pthread.dylib 0x1959102e4 _pthread_start + 136
8 libsystem_pthread.dylib 0x19590b0fc thread_start + 8

Thread 6:
0 libsystem_pthread.dylib 0x19590b0e8 start_wqthread + 0

Thread 7:: QSGRenderThread
0 libsystem_kernel.dylib 0x1958d26ec __psynch_cvwait + 8
1 libsystem_pthread.dylib 0x195910894 _pthread_cond_wait + 1204
2 WinBox 0x104243494 0x104088000 + 1815700
3 WinBox 0x1042433c8 0x104088000 + 1815496
4 WinBox 0x104963e54 0x104088000 + 9289300
5 WinBox 0x104963f4c 0x104088000 + 9289548
6 WinBox 0x104964464 0x104088000 + 9290852
7 WinBox 0x1042373a8 0x104088000 + 1766312
8 libsystem_pthread.dylib 0x1959102e4 _pthread_start + 136
9 libsystem_pthread.dylib 0x19590b0fc thread_start + 8

Thread 8:: com.apple.NSEventThread
0 libsystem_kernel.dylib 0x1958cef54 mach_msg2_trap + 8
1 libsystem_kernel.dylib 0x1958e1604 mach_msg2_internal + 80
2 libsystem_kernel.dylib 0x1958d7af8 mach_msg_overwrite + 480
3 libsystem_kernel.dylib 0x1958cf29c mach_msg + 24
4 CoreFoundation 0x1959f8a4c __CFRunLoopServiceMachPort + 160
5 CoreFoundation 0x1959f72ac __CFRunLoopRun + 1212
6 CoreFoundation 0x1959f6734 CFRunLoopRunSpecific + 588
7 AppKit 0x199693278 _NSEventThread + 148
8 libsystem_pthread.dylib 0x1959102e4 _pthread_start + 136
9 libsystem_pthread.dylib 0x19590b0fc thread_start + 8

Thread 9:: com.apple.CFSocket.private
0 libsystem_kernel.dylib 0x1958d9fbc __select + 8
1 CoreFoundation 0x195a1f638 __CFSocketManager + 704
2 libsystem_pthread.dylib 0x1959102e4 _pthread_start + 136
3 libsystem_pthread.dylib 0x19590b0fc thread_start + 8

Thread 10:
0 libsystem_pthread.dylib 0x19590b0e8 start_wqthread + 0

Thread 11:: CVDisplayLink
0 libsystem_kernel.dylib 0x1958d26ec __psynch_cvwait + 8
1 libsystem_pthread.dylib 0x1959108c0 _pthread_cond_wait + 1248
2 CoreVideo 0x19ed743a4 CVDisplayLink::waitUntil(unsigned long long) + 316
3 CoreVideo 0x19ed7347c CVDisplayLink::runIOThread() + 504
4 libsystem_pthread.dylib 0x1959102e4 _pthread_start + 136
5 libsystem_pthread.dylib 0x19590b0fc thread_start + 8


Thread 0 crashed with ARM Thread State (64-bit):
x0: 0x0000000000000000 x1: 0x0000000000000000 x2: 0x0000000000000000 x3: 0x0000000000000000
x4: 0x000000016bd72948 x5: 0x0000000000000020 x6: 0x000000000000000a x7: 0x0000600003cbe1e0
x8: 0xa15a5023db24ee68 x9: 0xa15a5022240ce628 x10: 0x0000000000000002 x11: 0x0000010000000000
x12: 0x00000000fffffffd x13: 0x0000000000000000 x14: 0x0000000000000000 x15: 0x0000000000000000
x16: 0x0000000000000148 x17: 0x00000002078c22c0 x18: 0x0000000000000000 x19: 0x0000000000000006
x20: 0x0000000000000103 x21: 0x00000001ff280920 x22: 0x000000011d790e90 x23: 0x0000000106d07970
x24: 0x0000600003e0a1f0 x25: 0x000000016bd72bb8 x26: 0x0000000000000000 x27: 0x00006000007afcf0
x28: 0x0000000000000000 fp: 0x000000016bd729b0 lr: 0x000000019590ff70
sp: 0x000000016bd72990 pc: 0x00000001958d7720 cpsr: 0x40001000
far: 0x0000000000000000 esr: 0x56000080 Address size fault

Binary Images:
0x104088000 - 0x1066effff com.mikrotik.winbox (4.0.98020) <b0283b8c-1112-3f1d-b395-335af19a6cfe> /Applications/WinBox.app/Contents/MacOS/WinBox
0x106b84000 - 0x106ba3fff com.apple.security.csparser (3.0) <fb85321b-0fa8-3ace-941c-abef6c37ff36> /System/Library/Frameworks/Security.framework/Versions/A/PlugIns/csparser.bundle/Contents/MacOS/csparser
0x10b66c000 - 0x10b677fff libobjc-trampolines.dylib (*) <3d687e9b-e092-3632-bc1d-74b19d492de0> /usr/lib/libobjc-trampolines.dylib
0x10f300000 - 0x10f9a3fff com.apple.AGXMetal13-3 (324.6) <4127f44c-9853-3b87-b300-dc4614ed8bcc> /System/Library/Extensions/AGXMetal13_3.bundle/Contents/MacOS/AGXMetal13_3
0x1958ce000 - 0x195908ff7 libsystem_kernel.dylib (*) <eee9d0d3-dffc-37cb-9ced-b27cd0286d8c> /usr/lib/system/libsystem_kernel.dylib
0x195909000 - 0x195915fff libsystem_pthread.dylib (*) <642faf7a-874e-37e6-8aba-2b0cc09a3025> /usr/lib/system/libsystem_pthread.dylib
0x1957a3000 - 0x195824ffb libsystem_c.dylib (*) <92699527-645f-3d8d-aed8-1cfb0c034e15> /usr/lib/system/libsystem_c.dylib
0x19597b000 - 0x195e6ffff com.apple.CoreFoundation (6.9) <190e6a36-fcaa-3ea3-94bb-7009c44653da> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
0x1a0e5a000 - 0x1a1161fff com.apple.HIToolbox (2.1.1) <950f1236-acaf-379d-819f-6c6b0b5deabd> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.framework/Versions/A/HIToolbox
0x199533000 - 0x19a96ffff com.apple.AppKit (6.9) <b88a44c1-d617-33dc-90ed-b6ab417c428e> /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit
0x19558a000 - 0x19560bf3f dyld (*) <398a133c-9bcb-317f-a064-a40d3cea3c0f> /usr/lib/dyld
0x0 - 0xffffffffffffffff ??? (*) <00000000-0000-0000-0000-000000000000> ???
0x19ed71000 - 0x19edd1fff com.apple.CoreVideo (1.8) <0fcfe924-013c-3974-9fdf-58f9a8d71845> /System/Library/Frameworks/CoreVideo.framework/Versions/A/CoreVideo

External Modification Summary:
Calls made by other processes targeting this process:
task_for_pid: 0
thread_create: 0
thread_set_state: 0
Calls made by this process:
task_for_pid: 0
thread_create: 0
thread_set_state: 0
Calls made by all processes on this machine:
task_for_pid: 0
thread_create: 0
thread_set_state: 0

VM Region Summary:
ReadOnly portion of Libraries: Total=1.6G resident=0K(0%) swapped_out_or_unallocated=1.6G(100%)
Writable regions: Total=1.7G written=771K(0%) resident=771K(0%) swapped_out=0K(0%) unallocated=1.7G(100%)

VIRTUAL REGION
REGION TYPE SIZE COUNT (non-coalesced)
=========== ======= =======
Accelerate framework 256K 2
Activity Tracing 256K 1
CG image 2160K 5
ColorSync 576K 28
CoreAnimation 304K 18
CoreGraphics 32K 2
CoreUI image data 992K 7
Foundation 16K 1
JS VM Gigacage 4096K 1
JS VM Isolated Heap 6464K 5
Kernel Alloc Once 32K 1
MALLOC 1.6G 74
MALLOC guard page 288K 18
STACK GUARD 56.2M 12
Stack 21.4M 13
VM_ALLOCATE 656K 21
__AUTH 5139K 656
__AUTH_CONST 69.7M 898
__CTF 824 1
__DATA 24.9M 881
__DATA_CONST 25.2M 909
__DATA_DIRTY 2748K 333
__FONT_DATA 2352 1
__INFO_FILTER 8 1
__LINKEDIT 609.2M 5
__OBJC_RW 2374K 1
__TEXT 1.0G 929
__TPRO_CONST 272K 2
mapped file 215.8M 53
owned unmapped memory 400K 1
page table in kernel 771K 1
shared memory 880K 15
=========== ======= =======
TOTAL 3.7G 4896



-----------
Full Report
-----------

{"app_name":"WinBox","timestamp":"2025-05-02 21:04:27.00 +0200","app_version":"4.0.98020","slice_uuid":"b0283b8c-1112-3f1d-b395-335af19a6cfe","build_version":"4.0.98020","platform":1,"bundleID":"com.mikrotik.winbox","share_with_app_devs":0,"is_first_party":0,"bug_type":"309","os_version":"macOS 15.3.2 (24D81)","roots_installed":0,"name":"WinBox","incident_id":"15FABD4A-966A-4C65-81ED-068FA5691145"}
{
"uptime" : 220000,
"procRole" : "Foreground",
"version" : 2,
"userID" : 501,
"deployVersion" : 210,
"modelCode" : "MacBookAir10,1",
"coalitionID" : 25152,
"osVersion" : {
"train" : "macOS 15.3.2",
"build" : "24D81",
"releaseType" : "User"
},
"captureTime" : "2025-05-02 21:04:24.5518 +0200",
"codeSigningMonitor" : 1,
"incident" : "15FABD4A-966A-4C65-81ED-068FA5691145",
"pid" : 33276,
"translated" : false,
"cpuType" : "ARM-64",
"roots_installed" : 0,
"bug_type" : "309",
"procLaunch" : "2025-05-02 21:03:44.4316 +0200",
"procStartAbsTime" : 5487403679352,
"procExitAbsTime" : 5488365518073,
"procName" : "WinBox",
"procPath" : "\/Applications\/WinBox.app\/Contents\/MacOS\/WinBox",
"bundleInfo" : {"CFBundleShortVersionString":"4.0.98020","CFBundleVersion":"4.0.98020","CFBundleIdentifier":"com.mikrotik.winbox"},
"storeInfo" : {"deviceIdentifierForVendor":"65C8BA59-6DED-5A31-B19F-AE27427C344B","thirdParty":true},
"parentProc" : "launchd",
"parentPid" : 1,
"coalitionName" : "com.mikrotik.winbox",
"crashReporterKey" : "8EAD5DC0-CED7-7B76-8564-F9A0CC94E42C",
"lowPowerMode" : 1,
"codeSigningID" : "com.mikrotik.winbox",
"codeSigningTeamID" : "SV69C8EQQ8",
"codeSigningFlags" : 570503953,
"codeSigningValidationCategory" : 6,
"codeSigningTrustLevel" : 4294967295,
"instructionByteStream" : {"beforePC":"fyMD1f17v6n9AwCRcuD\/l78DAJH9e8Go\/w9f1sADX9YQKYDSARAA1A==","atPC":"AwEAVH8jA9X9e7+p\/QMAkWfg\/5e\/AwCR\/XvBqP8PX9bAA1\/WcAqA0g=="},
"bootSessionUUID" : "0972D96B-03F9-4DD0-995B-B44B90428D12",
"wakeTime" : 1247,
"sleepWakeUUID" : "9A7B7F36-A9D8-4895-A2DC-83ED096D1359",
"sip" : "enabled",
"exception" : {"codes":"0x0000000000000000, 0x0000000000000000","rawCodes":[0,0],"type":"EXC_CRASH","signal":"SIGABRT"},
"termination" : {"flags":0,"code":6,"namespace":"SIGNAL","indicator":"Abort trap: 6","byProc":"WinBox","byPid":33276},
"asi" : {"libsystem_c.dylib":["abort() called"]},
"extMods" : {"caller":{"thread_create":0,"thread_set_state":0,"task_for_pid":0},"system":{"thread_create":0,"thread_set_state":0,"task_for_pid":0},"targeted":{"thread_create":0,"thread_set_state":0,"task_for_pid":0},"warnings":0},
"faultingThread" : 0,
"threads" : [{"triggered":true,"id":3498625,"threadState":{"x":[{"value":0},{"value":0},{"value":0},{"value":0},{"value":6104230216},{"value":32},{"value":10},{"value":105553179959776},{"value":11626693502941064808},{"value":11626693495574292008},{"value":2},{"value":1099511627776},{"value":4294967293},{"value":0},{"value":0},{"value":0},{"value":328},{"value":8716559040},{"value":0},{"value":6},{"value":259},{"value":8575781152,"symbolLocation":224,"symbol":"_main_thread"},{"value":4789440144},{"value":4409293168},{"value":105553181319664},{"value":6104230840},{"value":0},{"value":105553124326640},{"value":0}],"flavor":"ARM_THREAD_STATE64","lr":{"value":6804275056},"cpsr":{"value":1073745920},"fp":{"value":6104230320},"sp":{"value":6104230288},"esr":{"value":1442840704,"description":" Address size fault"},"pc":{"value":6804043552,"matchesCrashFrame":1},"far":{"value":0}},"queue":"com.apple.main-thread","frames":[{"imageOffset":38688,"symbol":"__pthread_kill","symbolLocation":8,"imageIndex":4},{"imageOffset":28528,"symbol":"pthread_kill","symbolLocation":288,"imageIndex":5},{"imageOffset":497928,"symbol":"abort","symbolLocation":128,"imageIndex":6},{"imageOffset":27103032,"symbol":"ASlotRef::lazyInit(CType*, bool) const","symbolLocation":196,"imageIndex":0},{"imageOffset":27186304,"imageIndex":0},{"imageOffset":26309436,"symbol":"MdiWindowObj::MdiWindowObj(std::__1::unique_ptr<ViewModel, std::__1::default_delete<ViewModel>>, unsigned int, nv::message, QString)","symbolLocation":832,"imageIndex":0},{"imageOffset":27128324,"imageIndex":0},{"imageOffset":27174152,"imageIndex":0},{"imageOffset":26587728,"imageIndex":0},{"imageOffset":26012804,"symbol":"MenuButtonWidget::qt_metacall(QMetaObject::Call, int, void**)","symbolLocation":288,"imageIndex":0},{"imageOffset":3847092,"imageIndex":0},{"imageOffset":3786108,"imageIndex":0},{"imageOffset":3782584,"imageIndex":0},{"imageOffset":4376260,"imageIndex":0},{"imageOffset":29134480,"imageIndex":0},{"imageOffset":4203300,"imageIndex":0},{"imageOffset":4201092,"imageIndex":0},{"imageOffset":3477788,"imageIndex":0},{"imageOffset":4762732,"imageIndex":0},{"imageOffset":4458204,"imageIndex":0},{"imageOffset":4459788,"imageIndex":0},{"imageOffset":4910228,"imageIndex":0},{"imageOffset":775844,"imageIndex":0},{"imageOffset":13667968,"imageIndex":0},{"imageOffset":13770988,"imageIndex":0},{"imageOffset":7074568,"imageIndex":0},{"imageOffset":17431004,"imageIndex":0},{"imageOffset":17434904,"imageIndex":0},{"imageOffset":488624,"imageIndex":0},{"imageOffset":8565344,"imageIndex":0},{"imageOffset":8562700,"imageIndex":0},{"imageOffset":8544972,"imageIndex":0},{"imageOffset":8537372,"imageIndex":0},{"imageOffset":8535132,"imageIndex":0},{"imageOffset":7643860,"imageIndex":0},{"imageOffset":7702640,"imageIndex":0},{"imageOffset":17431004,"imageIndex":0},{"imageOffset":17434904,"imageIndex":0},{"imageOffset":488624,"imageIndex":0},{"imageOffset":21250028,"imageIndex":0},{"imageOffset":21505616,"imageIndex":0},{"imageOffset":11709040,"imageIndex":0},{"imageOffset":514212,"symbol":"__CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__","symbolLocation":28,"imageIndex":7},{"imageOffset":514104,"symbol":"__CFRunLoopDoSource0","symbolLocation":176,"imageIndex":7},{"imageOffset":513436,"symbol":"__CFRunLoopDoSources0","symbolLocation":244,"imageIndex":7},{"imageOffset":508216,"symbol":"__CFRunLoopRun","symbolLocation":840,"imageIndex":7},{"imageOffset":505652,"symbol":"CFRunLoopRunSpecific","symbolLocation":588,"imageIndex":7},{"imageOffset":1094960,"symbol":"RunCurrentEventLoopInMode","symbolLocation":292,"imageIndex":8},{"imageOffset":1118588,"symbol":"ReceiveNextEventCommon","symbolLocation":216,"imageIndex":8},{"imageOffset":1119496,"symbol":"_BlockUntilNextEventMatchingListInModeWithFilter","symbolLocation":76,"imageIndex":8},{"imageOffset":243784,"symbol":"_DPSNextEvent","symbolLocation":660,"imageIndex":9},{"imageOffset":10099748,"symbol":"-[NSApplication(NSEventRouting) _nextEventMatchingEventMask:untilDate:inMode:dequeue:]","symbolLocation":688,"imageIndex":9},{"imageOffset":190580,"symbol":"-[NSApplication run]","symbolLocation":480,"imageIndex":9},{"imageOffset":11699444,"imageIndex":0},{"imageOffset":526572,"imageIndex":0},{"imageOffset":490392,"imageIndex":0},{"imageOffset":26133004,"symbol":"main","symbolLocation":13600,"imageIndex":0},{"imageOffset":25204,"symbol":"start","symbolLocation":2840,"imageIndex":10}]},{"id":3498641,"frames":[{"imageOffset":8424,"symbol":"start_wqthread","symbolLocation":0,"imageIndex":5}],"threadState":{"x":[{"value":6105378816},{"value":4355},{"value":6104842240},{"value":0},{"value":409604},{"value":18446744073709551615},{"value":0},{"value":0},{"value":0},{"value":0},{"value":0},{"value":0},{"value":0},{"value":0},{"value":0},{"value":0},{"value":0},{"value":0},{"value":0},{"value":0},{"value":0},{"value":0},{"value":0},{"value":0},{"value":0},{"value":0},{"value":0},{"value":0},{"value":0}],"flavor":"ARM_THREAD_STATE64","lr":{"value":0},"cpsr":{"value":4096},"fp":{"value":0},"sp":{"value":6105378816},"esr":{"value":1442840704,"description":" Address size fault"},"pc":{"value":6804254952},"far":{"value":0}}},{"id":3498657,"frames":[{"imageOffset":8424,"symbol":"start_wqthread","symbolLocation":0,"imageIndex":5}],"threadState":{"x":[{"value":6106525696},{"value":23299},{"value":6105989120},{"value":0},{"value":409604},{"value":18446744073709551615},{"value":0},{"value":0},{"value":0},{"value":0},{"value":0},{"value":0},{"value":0},{"value":0},{"value":0},{"value":0},{"value":0},{"value":0},{"value":0},{"value":0},{"value":0},{"value":0},{"value":0},{"value":0},{"value":0},{"value":0},{"value":0},{"value":0},{"value":0}],"flavor":"ARM_THREAD_STATE64","lr":{"value":0},"cpsr":{"value":4096},"fp":{"value":0},"sp":{"value":6106525696},"esr":{"value":1442840704,"description":" Address size fault"},"pc":{"value":6804254952},"far":{"value":0}}},{"id":3498682,"name":"QQmlThread","threadState":{"x":[{"value":4},{"value":0},{"value":4294967295},{"value":4294967296},{"value":8796093024512},{"value":0},{"value":0},{"value":0},{"value":9223372036854775807},{"value":1},{"value":1},{"value":0},{"value":2043},{"value":2045},{"value":2436739140},{"value":2434641915},{"value":230},{"value":8716560112},{"value":0},{"value":1},{"value":105553179787696},{"value":9223372036854775807},{"value":4848680160},{"value":4294967296},{"value":0},{"value":0},{"value":0},{"value":0},{"value":0}],"flavor":"ARM_THREAD_STATE64","lr":{"value":4364392780},"cpsr":{"value":1610616832},"fp":{"value":6114962896},"sp":{"value":6114962832},"esr":{"value":1442840704,"description":" Address size fault"},"pc":{"value":6804043824},"far":{"value":0}},"frames":[{"imageOffset":38960,"symbol":"poll","symbolLocation":8,"imageIndex":4},{"imageOffset":1759564,"imageIndex":0},{"imageOffset":1773980,"imageIndex":0},{"imageOffset":526572,"imageIndex":0},{"imageOffset":1273160,"imageIndex":0},{"imageOffset":1766312,"imageIndex":0},{"imageOffset":29412,"symbol":"_pthread_start","symbolLocation":136,"imageIndex":5},{"imageOffset":8444,"symbol":"thread_start","symbolLocation":8,"imageIndex":5}]},{"id":3498692,"name":"QNetworkAccessManager thread","threadState":{"x":[{"value":4},{"value":0},{"value":115122},{"value":4294967296},{"value":0},{"value":4294967295},{"value":3},{"value":16383},{"value":115121999208},{"value":115121},{"value":115121000000},{"value":0},{"value":255},{"value":127},{"value":719325294},{"value":717226225},{"value":230},{"value":8716560112},{"value":0},{"value":1},{"value":105553180158384},{"value":1000000},{"value":4830486704},{"value":4294967296},{"value":0},{"value":0},{"value":0},{"value":0},{"value":0}],"flavor":"ARM_THREAD_STATE64","lr":{"value":4364392872},"cpsr":{"value":2684358656},"fp":{"value":6117830096},"sp":{"value":6117830032},"esr":{"value":1442840704,"description":" Address size fault"},"pc":{"value":6804043824},"far":{"value":0}},"frames":[{"imageOffset":38960,"symbol":"poll","symbolLocation":8,"imageIndex":4},{"imageOffset":1759656,"imageIndex":0},{"imageOffset":1773980,"imageIndex":0},{"imageOffset":526572,"imageIndex":0},{"imageOffset":1273160,"imageIndex":0},{"imageOffset":1766312,"imageIndex":0},{"imageOffset":29412,"symbol":"_pthread_start","symbolLocation":136,"imageIndex":5},{"imageOffset":8444,"symbol":"thread_start","symbolLocation":8,"imageIndex":5}]},{"id":3498696,"name":"QQuickPixmapReader","threadState":{"x":[{"value":4},{"value":0},{"value":4294967295},{"value":4294967296},{"value":4719134064},{"value":36},{"value":0},{"value":0},{"value":9223372036854775807},{"value":1},{"value":1},{"value":0},{"value":2043},{"value":2045},{"value":3412210568},{"value":3410111264},{"value":230},{"value":8716560112},{"value":0},{"value":1},{"value":105553179670608},{"value":9223372036854775807},{"value":4830156608},{"value":4294967296},{"value":0},{"value":0},{"value":0},{"value":0},{"value":0}],"flavor":"ARM_THREAD_STATE64","lr":{"value":4364392780},"cpsr":{"value":1610616832},"fp":{"value":6118976896},"sp":{"value":6118976832},"esr":{"value":1442840704,"description":" Address size fault"},"pc":{"value":6804043824},"far":{"value":0}},"frames":[{"imageOffset":38960,"symbol":"poll","symbolLocation":8,"imageIndex":4},{"imageOffset":1759564,"imageIndex":0},{"imageOffset":1773980,"imageIndex":0},{"imageOffset":526572,"imageIndex":0},{"imageOffset":1273160,"imageIndex":0},{"imageOffset":8634836,"imageIndex":0},{"imageOffset":1766312,"imageIndex":0},{"imageOffset":29412,"symbol":"_pthread_start","symbolLocation":136,"imageIndex":5},{"imageOffset":8444,"symbol":"thread_start","symbolLocation":8,"imageIndex":5}]},{"id":3498697,"frames":[{"imageOffset":8424,"symbol":"start_wqthread","symbolLocation":0,"imageIndex":5}],"threadState":{"x":[{"value":6119550976},{"value":8203},{"value":6119014400},{"value":0},{"value":409604},{"value":18446744073709551615},{"value":0},{"value":0},{"value":0},{"value":0},{"value":0},{"value":0},{"value":0},{"value":0},{"value":0},{"value":0},{"value":0},{"value":0},{"value":0},{"value":0},{"value":0},{"value":0},{"value":0},{"value":0},{"value":0},{"value":0},{"value":0},{"value":0},{"value":0}],"flavor":"ARM_THREAD_STATE64","lr":{"value":0},"cpsr":{"value":4096},"fp":{"value":0},"sp":{"value":6119550976},"esr":{"value":1442840704,"description":" Address size fault"},"pc":{"value":6804254952},"far":{"value":0}}},{"id":3498705,"name":"QSGRenderThread","threadState":{"x":[{"value":260},{"value":0},{"value":15616},{"value":0},{"value":0},{"value":160},{"value":0},{"value":0},{"value":6120123640},{"value":0},{"value":0},{"value":2},{"value":2},{"value":0},{"value":0},{"value":0},{"value":305},{"value":8716558968},{"value":0},{"value":105553135483008},{"value":105553135483072},{"value":6120124640},{"value":0},{"value":0},{"value":15616},{"value":15617},{"value":15872},{"value":0},{"value":0}],"flavor":"ARM_THREAD_STATE64","lr":{"value":6804277396},"cpsr":{"value":1610616832},"fp":{"value":6120123760},"sp":{"value":6120123616},"esr":{"value":1442840704,"description":" Address size fault"},"pc":{"value":6804023020},"far":{"value":0}},"frames":[{"imageOffset":18156,"symbol":"__psynch_cvwait","symbolLocation":8,"imageIndex":4},{"imageOffset":30868,"symbol":"_pthread_cond_wait","symbolLocation":1204,"imageIndex":5},{"imageOffset":1815700,"imageIndex":0},{"imageOffset":1815496,"imageIndex":0},{"imageOffset":9289300,"imageIndex":0},{"imageOffset":9289548,"imageIndex":0},{"imageOffset":9290852,"imageIndex":0},{"imageOffset":1766312,"imageIndex":0},{"imageOffset":29412,"symbol":"_pthread_start","symbolLocation":136,"imageIndex":5},{"imageOffset":8444,"symbol":"thread_start","symbolLocation":8,"imageIndex":5}]},{"id":3498710,"name":"com.apple.NSEventThread","threadState":{"x":[{"value":268451845},{"value":21592279046},{"value":8589934592},{"value":236425064742912},{"value":0},{"value":236425064742912},{"value":2},{"value":4294967295},{"value":18446744073709550527},{"value":2},{"value":0},{"value":0},{"value":0},{"value":55047},{"value":0},{"value":0},{"value":18446744073709551569},{"value":8716541432},{"value":0},{"value":4294967295},{"value":2},{"value":236425064742912},{"value":0},{"value":236425064742912},{"value":6121267304},{"value":8589934592},{"value":21592279046},{"value":21592279046},{"value":4412409862}],"flavor":"ARM_THREAD_STATE64","lr":{"value":6804084228},"cpsr":{"value":4096},"fp":{"value":6121267152},"sp":{"value":6121267072},"esr":{"value":1442840704,"description":" Address size fault"},"pc":{"value":6804008788},"far":{"value":0}},"frames":[{"imageOffset":3924,"symbol":"mach_msg2_trap","symbolLocation":8,"imageIndex":4},{"imageOffset":79364,"symbol":"mach_msg2_internal","symbolLocation":80,"imageIndex":4},{"imageOffset":39672,"symbol":"mach_msg_overwrite","symbolLocation":480,"imageIndex":4},{"imageOffset":4764,"symbol":"mach_msg","symbolLocation":24,"imageIndex":4},{"imageOffset":514636,"symbol":"__CFRunLoopServiceMachPort","symbolLocation":160,"imageIndex":7},{"imageOffset":508588,"symbol":"__CFRunLoopRun","symbolLocation":1212,"imageIndex":7},{"imageOffset":505652,"symbol":"CFRunLoopRunSpecific","symbolLocation":588,"imageIndex":7},{"imageOffset":1442424,"symbol":"_NSEventThread","symbolLocation":148,"imageIndex":9},{"imageOffset":29412,"symbol":"_pthread_start","symbolLocation":136,"imageIndex":5},{"imageOffset":8444,"symbol":"thread_start","symbolLocation":8,"imageIndex":5}]},{"id":3499128,"name":"com.apple.CFSocket.private","threadState":{"x":[{"value":4},{"value":0},{"value":105553181835872},{"value":0},{"value":0},{"value":0},{"value":0},{"value":0},{"value":6115537120},{"value":0},{"value":12507149521},{"value":31},{"value":9},{"value":4830934592},{"value":72057602613807673,"symbolLocation":72057594037927937,"symbol":"OBJC_CLASS_$___NSCFArray"},{"value":8575879736,"symbolLocation":0,"symbol":"OBJC_CLASS_$___NSCFArray"},{"value":93},{"value":8716547728},{"value":0},{"value":32},{"value":8575886224,"symbolLocation":0,"symbol":"__CFActiveSocketsLock"},{"value":1},{"value":4561332368},{"value":5},{"value":105553181835872},{"value":105553181835904},{"value":8594597312,"symbolLocation":0,"symbol":"__kCFNull"},{"value":0},{"value":8575885312,"symbolLocation":16,"symbol":"OBJC_METACLASS_$_NSConstantArray"}],"flavor":"ARM_THREAD_STATE64","lr":{"value":6805386808},"cpsr":{"value":1610616832},"fp":{"value":6115536832},"sp":{"value":6115503056},"esr":{"value":1442840704,"description":" Address size fault"},"pc":{"value":6804053948},"far":{"value":0}},"frames":[{"imageOffset":49084,"symbol":"__select","symbolLocation":8,"imageIndex":4},{"imageOffset":673336,"symbol":"__CFSocketManager","symbolLocation":704,"imageIndex":7},{"imageOffset":29412,"symbol":"_pthread_start","symbolLocation":136,"imageIndex":5},{"imageOffset":8444,"symbol":"thread_start","symbolLocation":8,"imageIndex":5}]},{"id":3499153,"frames":[{"imageOffset":8424,"symbol":"start_wqthread","symbolLocation":0,"imageIndex":5}],"threadState":{"x":[{"value":6105952256},{"value":0},{"value":6105415680},{"value":0},{"value":278532},{"value":18446744073709551615},{"value":0},{"value":0},{"value":0},{"value":0},{"value":0},{"value":0},{"value":0},{"value":0},{"value":0},{"value":0},{"value":0},{"value":0},{"value":0},{"value":0},{"value":0},{"value":0},{"value":0},{"value":0},{"value":0},{"value":0},{"value":0},{"value":0},{"value":0}],"flavor":"ARM_THREAD_STATE64","lr":{"value":0},"cpsr":{"value":4096},"fp":{"value":0},"sp":{"value":6105952256},"esr":{"value":0,"description":" Address size fault"},"pc":{"value":6804254952},"far":{"value":0}}},{"id":3499180,"name":"CVDisplayLink","threadState":{"x":[{"value":260},{"value":0},{"value":30976},{"value":0},{"value":0},{"value":65704},{"value":0},{"value":19219875},{"value":30977},{"value":0},{"value":0},{"value":2},{"value":2},{"value":0},{"value":0},{"value":0},{"value":305},{"value":8716558968},{"value":0},{"value":4843125304},{"value":4843125368},{"value":1},{"value":19219875},{"value":0},{"value":30976},{"value":30977},{"value":31232},{"value":8539847928,"symbolLocation":0,"symbol":"CVHostTimeBase::sToNanosDenominator"},{"value":8539847960,"symbolLocation":0,"symbol":"kZeroVideoTime"}],"flavor":"ARM_THREAD_STATE64","lr":{"value":6804277440},"cpsr":{"value":2684358656},"fp":{"value":6116109744},"sp":{"value":6116109600},"esr":{"value":1442840704,"description":" Address size fault"},"pc":{"value":6804023020},"far":{"value":0}},"frames":[{"imageOffset":18156,"symbol":"__psynch_cvwait","symbolLocation":8,"imageIndex":4},{"imageOffset":30912,"symbol":"_pthread_cond_wait","symbolLocation":1248,"imageIndex":5},{"imageOffset":13220,"symbol":"CVDisplayLink::waitUntil(unsigned long long)","symbolLocation":316,"imageIndex":12},{"imageOffset":9340,"symbol":"CVDisplayLink::runIOThread()","symbolLocation":504,"imageIndex":12},{"imageOffset":29412,"symbol":"_pthread_start","symbolLocation":136,"imageIndex":5},{"imageOffset":8444,"symbol":"thread_start","symbolLocation":8,"imageIndex":5}]}],
"usedImages" : [
{
"source" : "P",
"arch" : "arm64",
"base" : 4362633216,
"CFBundleShortVersionString" : "4.0.98020",
"CFBundleIdentifier" : "com.mikrotik.winbox",
"size" : 40271872,
"uuid" : "b0283b8c-1112-3f1d-b395-335af19a6cfe",
"path" : "\/Applications\/WinBox.app\/Contents\/MacOS\/WinBox",
"name" : "WinBox",
"CFBundleVersion" : "4.0.98020"
},
{
"source" : "P",
"arch" : "arm64e",
"base" : 4407705600,
"CFBundleShortVersionString" : "3.0",
"CFBundleIdentifier" : "com.apple.security.csparser",
"size" : 131072,
"uuid" : "fb85321b-0fa8-3ace-941c-abef6c37ff36",
"path" : "\/System\/Library\/Frameworks\/Security.framework\/Versions\/A\/PlugIns\/csparser.bundle\/Contents\/MacOS\/csparser",
"name" : "csparser",
"CFBundleVersion" : "61439.81.1"
},
{
"source" : "P",
"arch" : "arm64e",
"base" : 4486250496,
"size" : 49152,
"uuid" : "3d687e9b-e092-3632-bc1d-74b19d492de0",
"path" : "\/usr\/lib\/libobjc-trampolines.dylib",
"name" : "libobjc-trampolines.dylib"
},
{
"source" : "P",
"arch" : "arm64e",
"base" : 4549771264,
"CFBundleShortVersionString" : "324.6",
"CFBundleIdentifier" : "com.apple.AGXMetal13-3",
"size" : 6963200,
"uuid" : "4127f44c-9853-3b87-b300-dc4614ed8bcc",
"path" : "\/System\/Library\/Extensions\/AGXMetal13_3.bundle\/Contents\/MacOS\/AGXMetal13_3",
"name" : "AGXMetal13_3",
"CFBundleVersion" : "324.6"
},
{
"source" : "P",
"arch" : "arm64e",
"base" : 6804004864,
"size" : 241656,
"uuid" : "eee9d0d3-dffc-37cb-9ced-b27cd0286d8c",
"path" : "\/usr\/lib\/system\/libsystem_kernel.dylib",
"name" : "libsystem_kernel.dylib"
},
{
"source" : "P",
"arch" : "arm64e",
"base" : 6804246528,
"size" : 53248,
"uuid" : "642faf7a-874e-37e6-8aba-2b0cc09a3025",
"path" : "\/usr\/lib\/system\/libsystem_pthread.dylib",
"name" : "libsystem_pthread.dylib"
},
{
"source" : "P",
"arch" : "arm64e",
"base" : 6802780160,
"size" : 532476,
"uuid" : "92699527-645f-3d8d-aed8-1cfb0c034e15",
"path" : "\/usr\/lib\/system\/libsystem_c.dylib",
"name" : "libsystem_c.dylib"
},
{
"source" : "P",
"arch" : "arm64e",
"base" : 6804713472,
"CFBundleShortVersionString" : "6.9",
"CFBundleIdentifier" : "com.apple.CoreFoundation",
"size" : 5197824,
"uuid" : "190e6a36-fcaa-3ea3-94bb-7009c44653da",
"path" : "\/System\/Library\/Frameworks\/CoreFoundation.framework\/Versions\/A\/CoreFoundation",
"name" : "CoreFoundation",
"CFBundleVersion" : "3302.1.400"
},
{
"source" : "P",
"arch" : "arm64e",
"base" : 6994370560,
"CFBundleShortVersionString" : "2.1.1",
"CFBundleIdentifier" : "com.apple.HIToolbox",
"size" : 3178496,
"uuid" : "950f1236-acaf-379d-819f-6c6b0b5deabd",
"path" : "\/System\/Library\/Frameworks\/Carbon.framework\/Versions\/A\/Frameworks\/HIToolbox.framework\/Versions\/A\/HIToolbox",
"name" : "HIToolbox"
},
{
"source" : "P",
"arch" : "arm64e",
"base" : 6867333120,
"CFBundleShortVersionString" : "6.9",
"CFBundleIdentifier" : "com.apple.AppKit",
"size" : 21221376,
"uuid" : "b88a44c1-d617-33dc-90ed-b6ab417c428e",
"path" : "\/System\/Library\/Frameworks\/AppKit.framework\/Versions\/C\/AppKit",
"name" : "AppKit",
"CFBundleVersion" : "2575.40.6"
},
{
"source" : "P",
"arch" : "arm64e",
"base" : 6800580608,
"size" : 532288,
"uuid" : "398a133c-9bcb-317f-a064-a40d3cea3c0f",
"path" : "\/usr\/lib\/dyld",
"name" : "dyld"
},
{
"size" : 0,
"source" : "A",
"base" : 0,
"uuid" : "00000000-0000-0000-0000-000000000000"
},
{
"source" : "P",
"arch" : "arm64e",
"base" : 6959861760,
"CFBundleShortVersionString" : "1.8",
"CFBundleIdentifier" : "com.apple.CoreVideo",
"size" : 397312,
"uuid" : "0fcfe924-013c-3974-9fdf-58f9a8d71845",
"path" : "\/System\/Library\/Frameworks\/CoreVideo.framework\/Versions\/A\/CoreVideo",
"name" : "CoreVideo",
"CFBundleVersion" : "672.10"
}
],
"sharedCache" : {
"base" : 6799769600,
"size" : 4865835008,
"uuid" : "5700d77a-6190-36e0-884d-fee6d586d62f"
},
"vmSummary" : "ReadOnly portion of Libraries: Total=1.6G resident=0K(0%) swapped_out_or_unallocated=1.6G(100%)\nWritable regions: Total=1.7G written=771K(0%) resident=771K(0%) swapped_out=0K(0%) unallocated=1.7G(100%)\n\n VIRTUAL REGION \nREGION TYPE SIZE COUNT (non-coalesced) \n=========== ======= ======= \nAccelerate framework 256K 2 \nActivity Tracing 256K 1 \nCG image 2160K 5 \nColorSync 576K 28 \nCoreAnimation 304K 18 \nCoreGraphics 32K 2 \nCoreUI image data 992K 7 \nFoundation 16K 1 \nJS VM Gigacage 4096K 1 \nJS VM Isolated Heap 6464K 5 \nKernel Alloc Once 32K 1 \nMALLOC 1.6G 74 \nMALLOC guard page 288K 18 \nSTACK GUARD 56.2M 12 \nStack 21.4M 13 \nVM_ALLOCATE 656K 21 \n__AUTH 5139K 656 \n__AUTH_CONST 69.7M 898 \n__CTF 824 1 \n__DATA 24.9M 881 \n__DATA_CONST 25.2M 909 \n__DATA_DIRTY 2748K 333 \n__FONT_DATA 2352 1 \n__INFO_FILTER 8 1 \n__LINKEDIT 609.2M 5 \n__OBJC_RW 2374K 1 \n__TEXT 1.0G 929 \n__TPRO_CONST 272K 2 \nmapped file 215.8M 53 \nowned unmapped memory 400K 1 \npage table in kernel 771K 1 \nshared memory 880K 15 \n=========== ======= ======= \nTOTAL 3.7G 4896 \n",
"legacyInfo" : {
"threadTriggered" : {
"queue" : "com.apple.main-thread"
}
},
"logWritingSignature" : "39a9cb82c5db52550113610af4478b9410ab6032",
"trialInfo" : {
"rollouts" : [
{
"rolloutId" : "642da32dea3b2418c750f848",
"factorPackIds" : {
"VISUAL_INTELLIGENCE_VICTORIA" : "66d8b2f77cd4b62688efd2cf"
},
"deploymentId" : 240000004
},
{
"rolloutId" : "67d07cd6a7affa169ae21f45",
"factorPackIds" : {

},
"deploymentId" : 240000002
}
],
"experiments" : [

]
}
}

Model: MacBookAir10,1, BootROM 11881.81.4, proc 8:4:4 processors, 8 GB, SMC
Graphics: Apple M1, Apple M1, Built-In
Display: Color LCD, 2560 x 1600 Retina, Main, MirrorOff, Online
Memory Module: LPDDR4, Hynix
AirPort: spairport_wireless_card_type_wifi (0x14E4, 0x4378), wl0: Sep 28 2024 04:40:32 version 18.20.462.0.7.8.175 FWID 01-10fa77df
IO80211_driverkit-1345.10 "IO80211_driverkit-1345.10" Dec 14 2024 17:47:07
AirPort:
Bluetooth: Version (null), 0 services, 0 devices, 0 incoming serial ports
Network Service: Wi-Fi, AirPort, en0
USB Device: USB31Bus
USB Device: USB31Bus
Thunderbolt Bus: MacBook Air, Apple Inc.
Thunderbolt Bus: MacBook Air, Apple Inc.

@ripemango

Dont't you think that attaching log file to the post would be much better than direct copy&paste of 501 lines? How many screens you have to scroll on a mobile device?

What's new in 4.0beta19:

*) updated Files menu for future RouterOS versions
*) use specific file browse widget for file selection fields
*) try to restore table scroll position when possible
*) do not send dynamically hidden fields

Probably the last option dropped the "advanced" button in wireless interface.
Is the only option the command line or there is an "hidden" feature to tell Winbox4 to show also "advanced" button?
P.S.
+1 for tab instead of drop-down boxes

Wireless advanced missing - bug confirmed, SUP-187229.

Today I downloaded and decided to try Winbox4beta20 (win10x64). I immediately saw a couple of bugs in the interface:
1. In the third Winbox I could open Static and Cache in separate windows in DNS. Here I can't do it.
2. Next situation: I have Сapsman running. I go to Wireless and click Scanner button. Winbox crashes(
3. When I launched Winbox3, I clicked on any line in Neighbors and the focus jumped to the password field. Now this does not happen. It is not convenient(

Is it possible to fix it?

It keeps forgetting my layout, even if I save it (several times even). Found the zoom setting, that takes away some of the bloatiness.
Overall nice and welcome upgrade. But.. For instance... New Firewall rule - What is that?! The old design was way better.

What's new in 4.0beta19:

*) updated Files menu for future RouterOS versions

I have a very bad feeling about that. What is that and is it gonna be done for WinBox 3 either?

I think it is to accommodate a situation where there are more than a couple of files in a tree, e.g. when using it as a fileserver.
(rose-storage)

My biggest concern about this is if such "future RouterOS version" comes out, WinBox 3 may show "not supported"...

Yes, that will happen for sure. Whether it is next month, next year, in 5 years or in 10 years time, we don't know.
The issue with many files is apparent when you use a https://mikrotik.com/product/rds2216

Any eta for the option to export logins?

I have noticed a strange crash-on-disconnect issue on Winbox 4.0beta20 (also tested on 3.41, doesn't happen there):

• If I disconnect from a remote router (SXT LTE6 Kit connected over WireGuard to our main router RB5009) when the log window is open with some filters set up, Winbox crashes.
• Interestingly, if I add or remove a filter and disconnect without pressing the "Update" button, Winbox disconnects normally (on next login the filters are back to how they were originally).
• If there aren't any filters set up in the log window, Winbox disconnects normally.
• If the log window is not open, Winbox disconnects normally.
• The same thing happens on 3 different remote SXT LTE6 Kits using different ISPs, but doesn't seem to happen when I do the same on a local router over LAN (aforementioned RB5009).

All devices have RouterOS 7.18.2. I'm not sure if this has been noticed before, also I don't know if it's an issue with the WireGuard connection, or with the Winbox connection having to be L3-routed to its destination, or just the long distance and ping. Also maybe the issue is only with the SXT LTE6 Kit, but I have yet to test it on the one I have at home to see if it behaves the same locally.

Update: I tested with my home SXT (which is on separate VLAN so the Winbox connection has to go through my main router), and it works normally. So it's more likely that the crash has something to do with the high ping to the remote routers.

Good afternoon.
I have a Big Sur macOS version 11.7.10, it is not allowed to update anymore.
I can only install to Winbox4.0Beta09, from this version, it does not let me update at 20.
From 9 passes to 12, 13, 14, 16 ... 20.
I have uninstalled and from scratch, previously erasing everything, I have tried the following versions:
- 12
- 13
- 20
And always the same error.

WinBox 00 by P. Ramiro, en Flickr

Someone can give me some light.
Thank you so much
Greetings

Any eta for the option to export logins?

Plus One Here !! :-)

I have noticed a strange crash-on-disconnect issue on Winbox 4.0beta20 (also tested on 3.41, doesn't happen there):

Yes it does happen from time to time but I have not been able to establish any pattern in this behaviour. This does not seem to be new...

Any eta for the option to export logins?

Plus One Here !! :-)

This is NOT the place to ask for RouterOS improvements. It is for WinBox 4.

Plus One Here !! :-)

This is NOT the place to ask for RouterOS improvements. It is for WinBox 4.

I think it's about exporting logins saved inside winbox, it has nothing to do with users inside routers.
I hope...

I have noticed a strange crash-on-disconnect issue on Winbox 4.0beta20 (also tested on 3.41, doesn't happen there):

Yes it does happen from time to time but I have not been able to establish any pattern in this behaviour. This does not seem to be new...

In my case it crashes every time when disconnecting from the remote routers with the log open and filters set up, only under those exact conditions. I think I also had similar unpredictable random crashes on disconnect under different conditions, but in this specific case the crash happens every time.

PS: I also think that the addresses.WBX export feature should be in Winbox 4.
Also, when that feature gets added it would be nice to be able to choose which entries I want to export, so that when someone on site needs to log into just a few devices there, I can send them just the exported entries for those devices instead of all of them.

This is NOT the place to ask for RouterOS improvements. It is for WinBox 4.

I think it's about exporting logins saved inside winbox, it has nothing to do with users inside routers.
I hope...

Yes, it is the option to export logins in winbox, since it has the import option, but exporting is not yet available!

What's new in 4.0beta21:

*) reintroduce tab support in the top menu of forms, with the ability to open multiple tabs using Shift + left-click.
*) fix date fields to allow year until 2106
*) user interface: remove input field wrapping feature
*) fix missing status fields for some interface instances (e.g. legacy wireless)
*) fix restoring object instance from workspace if opened from "generic" table
*) form: make default graph width a little bigger
*) fix restoring some table windows from workspace
*) fix restore Advanced Mode buttons
*) user interface: darker shadow for focused window
*) fix crash on opening some type of query type windows (PPP/Wireless Scan)

Thank you! It's great to have tabs back - that’s a big improvement. The "Shift + click" multi-select feature is quite interesting. But it would really help to have some way to learn about these features. Without reading the changelog, I would never have thought to try "Shift + click" for selecting multiple tabs. Maybe a tooltip or a small "quick help" panel could help users discover these things. Winbox will keep evolving, and with more shortcuts coming, it would be useful to have a place where users can easily look them up.

Good morning
WinBox v4.0beta21, is it compatible with macOS Big Sur v11.7.10 (4-core Intel Core i7)?
I can only install WinBox v4.0beta9.

Thank you very much.

No, it is not compatible with macos BigSur. See changelog.

Good morning
WinBox v4.0beta21, is it compatible with macOS Big Sur v11.7.10 (4-core Intel Core i7)?
I can only install WinBox v4.0beta9.

Thank you very much.

4-core intel core i7 you can upgrade macOS to a new version. https://dortania.github.io/OpenCore-Legacy-Patcher/

No, it is not compatible with macos BigSur. See changelog.

Code: Select all

What's new in v4.0beta13:

*) bump minimal macOS version to 12.0, because 11.0 is EOL and dropped by Qt

Thank you very much.

Good morning
WinBox v4.0beta21, is it compatible with macOS Big Sur v11.7.10 (4-core Intel Core i7)?
I can only install WinBox v4.0beta9.

Thank you very much.

4-core intel core i7 you can upgrade macOS to a new version. https://dortania.github.io/OpenCore-Legacy-Patcher/

Thank you very much.

Will Winbox 3 still be supported by future ROS releases? My love for ROS is also due to the simplicity and style of Winbox 3.

What's new in 4.0beta21:

*) reintroduce tab support in the top menu of forms, with the ability to open multiple tabs using Shift + left-click.
*) user interface: remove input field wrapping feature
*) fix missing status fields for some interface instances (e.g. legacy wireless)

Glad to see some little movements in the right direction.

Tabs back is a nice improvement. Now I would like graphs in WinBox 4 to have WinBox 3 feature parity. You cannot click on the graph anymore to see stats where you clicked.

Also open windows like PPPoE interface window are not saved if you quit WinBox. This was fixed in the past and now broken again.

With new 4.0beta21

in dark mode time to time blinks ?

Please can the ping tool be fixed to work like the winbox3, where if you type an address in the "Ping To" if you press enter, it clears the box.
It gets really frustrating if you enter an address and hit enter to ping, and then the box is cleared. This seems to happen on the second address you ping, even in .21

Why are you so easily "frustrated"???
Besides that, there seems to be no difference in the operation here. type address, ENTER starts the ping, another ENTER stops it.

not sure why , but for me:
*) reintroduce tab support in the top menu of forms, with the ability to open multiple tabs using Shift + left-click.

does not work at all. Can anyone describe more?

not sure why , but for me:
*) reintroduce tab support in the top menu of forms, with the ability to open multiple tabs using Shift + left-click.

does not work at all. Can anyone describe more?

I couldn't get that work either (tested macOS).

Also, the ⌘/Meta+Scroll Wheel for ZOOM is rather "twitchy" (i.e. a slight move of mouse/trackpad is a LOT of zoom). Noticed when testing above - since I tried all the control key combo to unsuccessfully "open multiple tabs".

While I – sorta – got used to the "rightside-tabs"... I have to agree that the "tabs-on-top" is more expected and reduces the clutter when a form/dialog has "actions"/config stuff in the right-side.

@infabo

can u advice more

not sure why , but for me:
*) reintroduce tab support in the top menu of forms, with the ability to open multiple tabs using Shift + left-click.

does not work at all. Can anyone describe more?

What exactly doesn't work?
I can use tabs as in v3 and if I hold Shift, it will open all selected tabs on one page.
Though, I think it was unnecessary to completely remove collapse/expand mechanism.

And now there is no header for first selected tab. For example, if I choose 'Rx Stats' and 'Status' tabs, it shows header for 'Status' section, but doesn't show it for 'Rx Stats' section.
And contrast. Fields use bold and black font, but headers are in regular and gray font... Absolutely silly design again. MT, may be you finally fire your designers?
.

MacOS 15.5

Thank you for bringing back the tabs. Didn't realize how much I missed them. Thanks to everyone that was pushing for this. Looks much cleaner. Everything works fine for me, including the shift + left click multiple tabs. Screenshot below

What's new in 4.0beta21:

*) reintroduce tab support in the top menu of forms, with the ability to open multiple tabs using Shift + left-click.

Thank you Mikrotik dev team.

A return to sanity at last !

Placement of Remove is very bad - it should be in separate place and away from window closing button

Please can the ping tool be fixed to work like the winbox3, where if you type an address in the "Ping To" if you press enter, it clears the box.
It gets really frustrating if you enter an address and hit enter to ping, and then the box is cleared. This seems to happen on the second address you ping, even in .21

I think you have to re-fine your bugreport. I see absolutely no difference in behavior of "Winbox 3.41" and latest Winbox 4. You enter the address, hit "start" (or just enter key) and it clears the output-box and starts pinging. It acts exactly the same in 3.41 and in 4 beta21.

Placement of Remove is very bad - it should be in separate place and away from window closing button

I totally agree! I've hit the remove button by mistake plenty of times just because of the poor placement. It would also be great if there were an opt-in option to show a confirmation popup when trying to delete something, like "Are you sure?" or something along those lines.

Feature request: show the username. I can't find it anywhere on the active Winbox session window. Window title does not count - as window titles are not part of UI.

Opening WinBox with IP/Route previously opened results with only 2 columns visible. Closing & opening resolves problem.

This definitely needs to change: while selecting tabs on right side it is too easy to accidentally hit Remove - especially after getting used to actual tabs being in that same place before.
Remove needs to be located away from all other actions/buttons. Copy is less dangerous when clicked accidentally as this opens the form for new object, while Remove is a destructive action (only redemption here is that this action has confirmation prompt in it).

After accidentally clicking Remove, you can click Undo.

While I like that ESC will close a dialog box... it should NOT close it if the dialog form is DIRTY (fields modified), i.e. should prompt to Apply+Close, Ignore Changes, or Edit if you CHANGED a field.

Well, the whole coding around "if you changed a field" should be completely overhauled...
- it should only actually set fields (and log that) which you have changed
- it should not save values that originally were inherited from somewhere else (a template, a profile) and which you did not change
As part of that work, this confirmation action can also be added...

I made a small test... and it looks like even Mikrotik Pro mobile app does this correctly i.e. changes only the value that is actually changed - if system log messages can be taken as credible source of information on this.

That is interesting... does it also respect the inheritance of values from a higher level?
i.e. when you e.g. make a Template in Routing or a Configuration or Security in WiFi, define values in that, then you use that in a lower-level item (a Connection in Routing or a WiFi interface in WiFi) does it understand that when you modify some other property of that item, it should not copy the values from the higher level into the item but rather should leave then "blank" (i.e. "inherited")?

WinBox 4.0beta21
When I copy any existing rule in the Firewall, the "New" label no longer appears in the header. This makes it difficult to distinguish new rules from existing ones. Please consider bringing back this useful feature.

That is interesting... does it also respect the inheritance of values from a higher level?
i.e. when you e.g. make a Template in Routing or a Configuration or Security in WiFi, define values in that, then you use that in a lower-level item (a Connection in Routing or a WiFi interface in WiFi) does it understand that when you modify some other property of that item, it should not copy the values from the higher level into the item but rather should leave then "blank" (i.e. "inherited")?

It is very simple to test for anyone - open Winbox and log window in it. Then log in to devic with mobile app, try to change parameters and look for messages in the log. Then you can try to change same parameters from Winbox and you can compare how log messages look on both cases.

Unfortunately there's one big caveat with mobile app: app is not able to read or set some parameters properly - therefore it can screw some things up. I have seen this with wifi parameter settings so far but it might concern other settings as well...

Return the blue active window frame as it was earlier and make a VISIBLE inactive window frame!
This looks absolutely disgusting, no any visible borders between two windows.
.

since v7.21 does not allow us to use winbox 3, will be a possibility to have Winbox 3 skin in the new Winbox 4?

i dont want to use the new winbox, sorry (im not only one person)

since v7.21 does not allow us to use winbox 3, will be a possibility to have Winbox 3 skin in the new Winbox 4?

i dont want to use the new winbox, sorry (im not only one person)

Not sure that the skin will help a lot, it has tons of other problems.

But we should rather demand to update WinBox 3 to make it work with new RouterOS version. Because I don't see any signs that this sh*tty piece of software will become better in the nearest future.

Could we please discontinue Winbox 4 and keep Winbox 3 alive forever?

Could we please discontinue Winbox 4 and keep Winbox 3 alive forever?

This is the best idea.

BTW, normis said in some another topic, that the biggest reason for making a new version is that "WinBox 3 is so old, that some issues can't be fixed". Would be interesting to know, what are these issues, that can't be fixed because of the age.

Winbox 4 has, objectively speaking, significantly more issues than Winbox 3 - and this is likely to remain the case for the foreseeable future.

fyi: winbox 3 doesn't work on v7.21

I think Winbox 3 will be compatible by 3.42.

Two problems with downloading from files. Firstly, you used to be able to drag and drop on Windows into File Explorer. That doesn't work anymore. So one is forced to use Right-click/download except this doesn't remember the last folder used so each you have to navigate to the folder each time. Very tedious! To be fair, old WinBox didn't remember the folder either but as I tended to use drag & drop, it wasn't as annoying.

I'm sure this question has been asked before but I'm not going to scroll back through 8 pages... I assume the non-Windows user interface is because a standard GUI API has been used that works on Windows, Linux and MAC?

Can't download files. Winbox 4.0beta21. RoS 7.19 and 7.18.2 - both on an RB5009.

How to reproduce:
Open "files" menu. Select some file. Click "Download". Choose directory (we could have some work here too). Click "save" button. File isn't downloaded.

Two problems with downloading from files. Firstly, you used to be able to drag and drop on Windows into File Explorer. That doesn't work anymore.

To be precise, it doesn't work when dragging from WinBox to Desktop, but works vice versa. And it was in the list of known issues since September...

Can't download files. Winbox 4.0beta21. RoS 7.19 and 7.18.2 - both on an RB5009.

How to reproduce:
Open "files" menu. Select some file. Click "Download". Choose directory (we could have some work here too). Click "save" button. File isn't downloaded.

If file is in some subdirectory on device (be it /flash or other) then downloading it will create subdirectory with same name in the location file is downloaded i.e. whole path will be in the directory on your computer. It is confusing but might simplify things when downloading multiple files or full directories from the device.

If file is in some subdirectory on device (be it /flash or other) then downloading it will create subdirectory with same name in the location file is downloaded i.e. whole path will be in the directory on your computer. It is confusing but might simplify things when downloading multiple files or full directories from the device.

It isn't. I tested with files on the device's root directory.

Please, make "Select from:" not a drop-down list, but buttons: "Neighbors", "Saved", "RoMON Neigbors".
I would also like to add "saving the state" of the selection made.

Two problems with downloading from files. Firstly, you used to be able to drag and drop on Windows into File Explorer. That doesn't work anymore.

To be precise, it doesn't work when dragging from WinBox to Desktop, but works vice versa. And it was in the list of known issues since September...

Ahh... we really need a list of reported issues maintained somewhere so we don't reinvent the wheel. Do I infer from your post that such a thing exists?

Ahh... we really need a list of reported issues maintained somewhere so we don't reinvent the wheel. Do I infer from your post that such a thing exists?

Well, there are many of them in this topic

One in the very first post (outdated and absolutely not complete).

Also few lists in the middle posted by MT (very similar and also outdated):
viewtopic.php?p=1094934#p1094934
viewtopic.php?p=1095826#p1095826

And there is my own list (MT, have you seen it??): viewtopic.php?p=1132369#p1132369
These are just bugs, I don't even talk about appearance, usability and scaling issues.

Totally agree that everything should be gathered somewhere in one place.

@MikroTik, perhaps y'all can formally clarify how long WinBox3 will be supported?

There has just a lot of commentary, both here and release threads, worrying about when winbox3 will stop working:

Winbox 4 is not forced yet, v7.21 is alpha and should be treated as such.

There, I fixed it for you.

I saw an updated winbox 3.42 today... so clearly y'all have some commitment to its future – why not say when it be EOL'ed (perhaps 8.x?) so we can stop the FUD about it's immenient demise?