What's new in v3.41:

*) added support for new internal WinBox protocol fields;

If you experience version related issues, then please report them to support@mikrotik.com.

Both Winbox 32-bit and 64-bit versions are available here:
https://www.mikrotik.com/download

Thanks, but - where to get winbox for mac OS???

@VadiKO,
WineSkin/Wine?

@Kanzler,
I'm not against WineSkin for Windows, please use the normal WinBox v3.41 released for Mac OS! So will it be fair?

There never has been winbox for MacOS.
On Linux boxes you can run it via Wine, I suppose MacOS has something similar.

What's new in v3.41:

*) added support for new internal WinBox protocol fields;

What are these fields? In which windows are these used, or are they not yet used by RouterOS?
Is this a fix for the "some windows won't auto-update" that was introduced long ago with V7 (and seems to be getting worse)?

There never has been winbox for MacOS.
On Linux boxes you can run it via Wine, I suppose MacOS has something similar.

Yes, Winbox runs fine with wine on Mac OS, both intel based and apple silicon.

*) added support for new internal WinBox protocol fields;

I guess they added new "protocol fields" for the new WinBox app. Now added to legacy WinBox as well so it can still be used.

This is basically WInBox release for future use. At some point, 3.41 will become the minimal supported WinBox version. For end user, this release does not change anything.

What do u mean by future use?

I am pretty excited on the upcoming changes.

I can confirm v3.41 is working even with older ROS 7.13.5.

When I asked about the problem of BGP sessions window not being auto-refreshed with RouterOS v7 I got the reply that this would require a new Winbox version.
Recently I noticed that there are also refresh issues in the IP routes window, e.g. "immediate gateway" is not updated until F5 is pressed several times and/or the specifc route line is doubleclicked first.
I seems that RouterOS development is continuing and Winbox stays behind.

Is there any plan and schedule for that "new Winbox version"? It seems 3.41 is not it.

Yes, Winbox runs fine with wine on Mac OS, both intel based and apple silicon.

Tell me more about how you do it? maybe you have a video?

Thanks )

There are already so many videos about that... did you even attempt to search?
Even Normis made one.

Thanks, I'm findin this https://www.youtube.com/watch?v=TCPhYh9Wajw

I am pretty excited on the upcoming changes.

I can confirm v3.41 is working even with older ROS 7.13.5.

Works even with 6.44.6

Works even with 6.44.6

Fortunately, yes.
I still operate a mix of v6/v7 systems, the oldest being 6.47.9, and I would hate to have a situation where I need to keep different versions of winbox to communicate with all of them...

Fortunately Winbox is portable so we do not have the same problem as it is with Dude...

What's the problem with Dude running with Wine?

What's the problem with Dude running with Wine?

There is no 64-bit version of Dude.

Still no problem... Intel - viewtopic.php?p=1057281#p1057281, M1 - viewtopic.php?p=1057281#p1009936

Edit: still running on latest macOS:

What's the problem with Dude running with Wine?

There's no problem with Wine, but rather with Windows as Dude is not portable so every time when it updates to Dude server version it has to be run as administrator for update to succeed if your normal user account does not have admin/UAC privileges on Windows. With Wine you can have multiple versions of Dude ready at any time.

Yes, that's different thing, there are ways to create portable windows app from installed one and such can be redistributed then as standalone, still it requires some amount of additional work...

Thanks, but - where to get winbox for mac OS???

Why not use webfig (www-ssl) and ssh?

Why not use webfig

Because you can't rearrange the windows into a dashboard, it can't MAC-WinBox into a RouterOS device that has no IP yet (or a broken IP), it doesn't do neighbor discovery, refreshing the browser logs you out…

While I'm here, allow me to mention the option of Crossover, which for those who don't mind spending a little money gets you a better Wine experience on macOS, and it supports the WineHQ project.

…and ssh?

Yes-and all the things! Use the best tool for each job.

While I'm here, allow me to mention the option of Crossover, which for those who don't mind spending a little money gets you a better Wine experience on macOS, and it supports the WineHQ project.

also it is free for those who don't mind spending a little time to setup existing free builds :)
Mine ss are from running on WineskinCX 23.7.1 (revision 3 -rc1), a Crossover wine build from Wineskin, that why there is no issue running Dude for eg.

Hopefully at some time a new Winbox version will get a settable timeout on the TCP connection with the router.
Or is that completely depending on the router side? (there must be a timeout there as well)
Anyway, make it SETTABLE.
It is very inconvenient that Winbox sessions are lost everytime there is a small hickup in the connectivity, e.g. due to DFS, BGP convergence, VPN over a dynamic IP that is changing, etc.
I would like to be able to set a timeout up to 2 or 3 minutes.

Usually the timeout is long enough. Is it possible that any device along the way sends a destination unreachable packet back? That would close the connection immediately.

Usually the timeout is long enough.

Yes usually it is. But I am trying to get the "unusual" situations covered.

from time to time, im not able to log in to the MT by using winbox, reboot fixed it.
Does anyone aware of that?

I haven't notice anything unusual here...

from time to time, im not able to log in to the MT by using winbox, reboot fixed it.
Does anyone aware of that?

Definitely! Scheduled reboot saved my (WinBox) life.
SSH worked fine the whole time. Apart from the reboot, nothing else was changed (e.g. network topology, updates).

from time to time, im not able to log in to the MT by using winbox, reboot fixed it.
Does anyone aware of that?

Never seen an issue like this. Using RouterOS since 2014.

from time to time, im not able to log in to the MT by using winbox, reboot fixed it.
Does anyone aware of that?

Never seen an issue like this. Using RouterOS since 2014.

The same, but from 2007...

Indeed, never seen that here. The only thing particular to winbox logons is that immediately after logon it sends you a large bunch of data.
That can sometimes kill the connection when it is very fragile, or there are other circumstances that you are not aware of.
E.g. when I configure CAKE queue on the internet interface, and run a L2TP VPN over that, I cannot login using winbox.
(ping and telnet/ssh login works)
That is of course a bug, I have it in a discussion topic elsewhere on the forum.

when I configure CAKE queue on the internet interface, and run a L2TP VPN over that,

Interesting, when I have time I try that.

See: viewtopic.php?t=209551

from time to time, im not able to log in to the MT by using winbox, reboot fixed it.
Does anyone aware of that?

Definitely! Scheduled reboot saved my (WinBox) life.
SSH worked fine the whole time. Apart from the reboot, nothing else was changed (e.g. network topology, updates).

Same issue here, there's no solution without reboot? I have only experieced it in CCR2116 with v7.14.2

While rearranging IPv6 firewall filter view...

after selecting "Inline comments" and then unselecting it rule action icons disappeared. If I tried to select "Detail mode" Winbox crashed immediately and did that repeatedly.

Clearing cache did not help, but after deleting the session file problem was gone and could not be reproduced any more.

There still is this nasty issue in Winbox, that has become apparent due to new features in RouterOS v7:
1 - when changing some item in a panel, although Winbox knows what value(s) have been changed (the names appear in blue), it always sets a set of ALL values in that panel in the router, and all of them appear in the log line about changed values (also the unchanged values)
2 - when a certain configuration has "template" and "instance" values (e.g. in routing and in the new wifi config), when a value is set in the "template" and inherited by the "instance", Winbox shows the inherited value as if it is a per-instance set value instead of showing it as an "unset" value for that instance.

The combination of these two issues is what is important: it leads to the loss of inheritance of values from template to instance, whenever the instance is edited in Winbox.
When you later edit the template, it should by design affect all instances created from that template, but in reality that does not work.

☝️☝️☝️☝️☝️☝️☝️

Your post should be pinned. These 2 Winbox issues are the the root cause why people get stuck and confused in wifi configuration.

Your post should be pinned. These 2 Winbox issues are the the root cause why people get stuck and confused in wifi configuration.

Is that why we can't set all Wi-Fi configuration via Configuration profiles?

We can create Configuration profile and apply Security profile to it and apply that configuration to a Wi-Fi interface - but it just doesn't work or some of their combinations.
It was required to perform lot of experiments to understand that it can't be done in that way.

Or maybe I just missed something?