What's new in v3.20:

*) allow to filter by IPv6 addresses and prefixes;
*) build 64-bit Winbox as well (https://mt.lv/FeuQe);
*) do not leave files locked on computer when uploading files to router;
*) fixed problem where some fields were not shown for read only users;
*) fixed Winbox crash when copying multiple files between routers;
*) make Ctrl+A work in script fields and other multiline fields;
*) make DLL hijacking attack not work: Winbox will not look at the directory it resides in, when looking for system DLLs;
*) on update, Winbox will check that code is signed by MikroTik and not somebody else;
*) removed Drag and Drop support on 64-bit Winbox in Wine;
*) show system note at login;

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

Instructions on running Winbox 64-bit on MacOS Catalina are available here: viewtopic.php?f=2&t=152795&p=754980#p754824

If you try to upgrade directly from Winbox loader and version is not available, then you might need to wait for a while until cache in path between your device and our servers is refreshed.

*) on update, Winbox will check that code is signed by MikroTik and not somebody else;

Unfortunately this check still seems insecure.

*) removed Drag and Drop support on 64-bit Winbox in Wine;

Why?

*) removed Drag and Drop support on 64-bit Winbox in Wine;

Why?

Yeah seems kinda weird. I guess it was breaking some thing?

*) on update, Winbox will check that code is signed by MikroTik and not somebody else;

Unfortunately this check still seems insecure.

I remember your report ages ago and I always wondered how long till they fix that. I find this unbelievable that update process is vulnerable like that. Well, good to know that it is not yet fixed.
Thanks for report.

Changing the updater to use https instead of current plaintext http would be good and simple first step. It's nice bonus if it also checks new exe's signature, but in first place, it should not allow anyone on the way to intercept requests so easily.

Will their ever be a workin winbox in cata? Dont feel that Im a fan of this terminal thing..

What is "cata"?

Perhaps "MacOS Catalina"

Interface Link up/down date and time still incorrect, one of the reason I am still using 3.16.

What is "cata"?

Yes Macos Catalina..

After do Upgade in 3.20 they show the next message and only if I put [ok] allows me to continue, Why ?

Make sure you don't have anything in "/system note", because that's what the window is. From screenshot it doesn't look like you have anything there, but even single space would be enough.

On macos catalina using wine64 and automation start winbox64.
Seems all normal. hex poe (v6.45.6). cpu is around 1~5%.
But if i go to IP-FIREWALL-Address lists tab, CPU goes up to 54% immediately, then hopping between 25%-57% constantly. Only when i click other tabs, CPU returns normal.
Anyone observes the same?

What is "cata"?

Yes Macos Catalina..

Winbox is already working in macOS catalina.

What is "cata"?

Yes Macos Catalina..

Winbox is already working in macOS catalina.

Are you planing to release a real macos app?.. or is this what we have to live with?.. the old winbottler was ok.. maybe I have done somthing wrong.. but its disturbing with the terminal in the background.

Making the window full screen in wine64 with winbox64 on macos Catalina breaks winbox - Just drag the edges to full screen if you want this to work.
Also attempting to export/import addresses crashes wine64 with noexec filesystem error and hangs winbox.

Other than the above it seems to be working to an extend - we can live with it until full support is released!

Drag and drop doesnt work for my.. when I try to upload firmware.. upload button in files doesnt do anything more then hang winbox.
How far aways are we from a real winbox app for macOS? Parallels isnt an option.. to slow to start.. and resourses.

Is their anyway to get rid of terminal when winbox is started from terminal?

When start new winbox (either 32bit or 64bit) I get message: "ERROR: Colud not save conffiguration".
If I start with administrative privileges - no such error.

Also without administrative privileges I can't connect to router. And with administrative privileges - without problem

OS - Windows 7 Prof SP1 x64

Dear Mikrotik,

could you please consider changing application bar/other WinBOX window component colour while in SafeMode? Regardless of information when exiting the app it would help to identify the current mode.

Thanks in advance.

Best regards,
Bam

could you please consider changing application bar/other WinBOX window component colour while in SafeMode? Regardless of information when exiting the app it would help to identify the current mode.

+1

Why not added dark mode ?

Sent from my SM-A705FN using Tapatalk

Can you give us the ability to resize the columns in the Log window please? Mainly to be able to see full date/time. I've requested this feature many times and it still hasn't happened.

Can you give us the ability to resize the columns in the Log window please? Mainly to be able to see full date/time. I've requested this feature many times and it still hasn't happened.

wb_log.PNG

I've been asking for this for a year.
Not do.
Although promised year 3 ago do in version of 3.0
In the beta version did, then removed, promised and forgotten.

Keep getting the following error when trying to connect to any router:

"ERROR: no roteros.jg found"

Was working fine on version 3.19.

Routers are on version 6.45.6.

Any ideas of what it could be?

when will this finally be fixed?

Keep getting the following error when trying to connect to any router:

"ERROR: no roteros.jg found"

Was working fine on version 3.19.

Routers are on version 6.45.6.

Any ideas of what it could be?

I am getting the same since latest Win 10 update.
I had a student in class last week who was not getting neighbour discovery but we got around this by statically configuring an IP on his Windows machine.

My machine was updated yesterday and since the update I have the same problem you do. My workaround is to use winbox 3.18 (don't have 3.19)

*) removed Drag and Drop support on 64-bit Winbox in Wine;

Why?

Yeah seems kinda weird. I guess it was breaking some thing?

It rarely worked as it was, I wish it would have been fixed rather than removed. Everything else in the Mac Winbox port worked pretty well except file transfer in and out via drag and drop.

Not a major issue, more of an annoyance, double click does not work under "Neighbors" tab

*) removed Drag and Drop support on 64-bit Winbox in Wine;

Why?

Yeah seems kinda weird. I guess it was breaking some thing?

It rarely worked as it was, I wish it would have been fixed rather than removed. Everything else in the Mac Winbox port worked pretty well except file transfer in and out via drag and drop.

Upgrading to latest Wine Staging 4.19 will fix these issues, new Winbox 3.21 will have drag/drop and file transfers again.

What's new in v3.20:

1) Does the program Winbox use encryption to connect to hardware device?
2) Сan I use Winbox without fear in adverse networks?
3) Is there any protection in the connection from the Man in the middle (MITM) attack?

*) removed Drag and Drop support on 64-bit Winbox in Wine;

Why?

Yeah seems kinda weird. I guess it was breaking some thing?

It rarely worked as it was, I wish it would have been fixed rather than removed. Everything else in the Mac Winbox port worked pretty well except file transfer in and out via drag and drop.

Upgrading to latest Wine Staging 4.19 will fix these issues, new Winbox 3.21 will have drag/drop and file transfers again.

Great news. I'm unfamiliar with the term "Wine Staging." Are you talking about the pre-cooked Mac Winbox that is (or was once) available from the MikroTik website Software page, or am I going to have to learn how to roll my own (which I've tried before and never got to work)?

What's new in v3.20:

1) Does the program Winbox use encryption to connect to hardware device?
2) Сan I use Winbox without fear in adverse networks?
3) Is there any protection in the connection from the Man in the middle (MITM) attack?

From Winbox v3.14, the following security features are used:
Winbox.exe is signed with an Extended Validation certificate, issued by SIA Mikrotīkls (MikroTik).
WinBox uses ECSRP for key exchange and authentication (requires new winbox version).
Both sides verify that other side knows password (no man in the middle attack is possible).
Winbox in RoMON mode requires that agent is the latest version to be able to connect to latest version routers.
Winbox uses AES128-CBC-SHA as encryption algorithm (requires winbox version 3.14 or above).

https://wiki.mikrotik.com/wiki/Manual:Winbox#Summary

Great news. I'm unfamiliar with the term "Wine Staging."

I am referring to the official Wine download page, "Staging" is the latest and most updated release, as opposed to Stable: https://dl.winehq.org/wine-builds/macosx/download.html

1) Does the program Winbox use encryption to connect to hardware device?
2) Сan I use Winbox without fear in adverse networks?
3) Is there any protection in the connection from the Man in the middle (MITM) attack?

Yes, but since this is an administration tool, under no circumstances should you be leaving the management port open to the world. Always initiate an IPsec session before administering your devices.

Still no native Linux client

Please fix fonts, my ASCII Art not work :(

Note is orginally made for notes, not for art

Note is orginally made for notes, not for art :)

Beep is originally made for Beeps, not for play a "Star Wars -- The Imperial March" or "A_Bit_of_Sounds"

Future Suggestion: Please fix font or give us option in WinBox to not display this "Note PopUp/SplashScreen" and we will be happy with Ascii Art at terminal :). Thanks!.

Still no native Linux client

+ 1

Note is orginally made for notes, not for art

Future Suggestion: Please fix font or give us option in WinBox to not display this "Note PopUp/SplashScreen" and we will be happy with Ascii Art at terminal . Thanks!.

I suspect this was in response to a perceived legal issue, to ensure that any login note is immediately presented to and acknowledged by any breacher using Winbox.

Note is orginally made for notes, not for art

Beep is originally made for Beeps, not for play a "Star Wars -- The Imperial March"

LMAO

Made my day, thanks a lot!

I tried this new version (3.20 x64) and it crashes on any host I try to connect to in the "downloading descriptors" phase. I tried clearing the cache, moving the sessions folder, nothing has helped. 3.19 does not do this. Any idea as to why this is happening?

Winbox v3.21 has been released:

viewtopic.php?f=21&t=157150