What's new in v3.21:

*) added support for HiDPI displays;
*) download WinBox specific files from router only into AppData folder and not anywhere else (CVE-2020-5720);
*) enabled Drag and Drop support on 64-bit WinBox in Wine;
*) font size can be increased/decreased under "Settings/Zoom In" or "Zoom Out";
*) improved MikroTik signature checking on WinBox update;

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.

*) download WinBox specific files from router only into AppData folder and not anywhere else (CVE-2020-5720);

I could not find anything related to this CVE

*) improved MikroTik signature checking on WinBox update;

I can confirm that this now closes the remote code execution bug possible by a MITM. Using winbox auto update should be safe for now .

Also as a high DPI user, this release looks beautiful...

Had to downgrade back to 3.20. Does not work well with a resolution of 3840x2160. Log was unreadable with lines overlapping.

I found "wine winbox64.exe" produced this to standard output: which produced a Log window that had the columns too narrow and the entries all ending in "...".

Running "wine64 winbox64.exe" produced this: and it all looked normal, just like with 3.20.

Actually, now I tried it multiple times, it alternates between DPI=100 mode and DPI=120 mode.
It doesn't matter whether "wine" or "wine64" is used.
Also, it shrinks the window every time (relative to the previous time it picked the same DPI mode). This is quite irritating.

Had to downgrade back to 3.20. Does not work well with a resolution of 3840x2160. Log was unreadable with lines overlapping.

The same happened here using Wine 5.0.
Increasing DPI to 120 and 144 stay great on menus, but log became more unreadable because increase the overlapping.

About the Drag & Drop, it's only works to upload some file, if you try to download any file from Winbox, he'll crash and close.
I got this error from stdout after the Winbox crash: ACCESS VIOLATION EXCEPTION at address: _________ 4a04da

Log text lines is overlapping on 1440p monitor, 150% scaling. There's no problems in other menus.
Windows 10 (1909).

Actually, now I tried it multiple times, it alternates between DPI=100 mode and DPI=120 mode.
It doesn't matter whether "wine" or "wine64" is used.
Also, it shrinks the window every time (relative to the previous time it picked the same DPI mode). This is quite irritating.

Drink more Wine, the problem may go away!

I'll go slightly against the flow. Everyone seems to want things bigger, but I'd rather have them smaller. Or maybe better term would be more condensed. It's about one specific thing, line height.

With "standard" DPI display, WinBox 3.20 had lines 15px high. WinBox 3.21 has 16px. Right, it's just 1px difference, i.e. nothing. But it adds up. With fullscreen WinBox on FullHD resolution, I was able to see almost 56 lines (e.g. firewall rules), but now it's only 52. I won't give up RouterOS because of that. But I really like seeing more without scrolling, because it's practical.

So I have a suggestion: Keep 3.21 line height as default. Even I will admit that it probably looks better, if we're talking just about appearance (and it would look even better with vertically centered text, see last image; now it's alligned to top). But add a "condensed mode" option, which would leave out padding. With that, I'd be able to see almost 62 lines. And 62 compared to 52 is good difference.

Implementing this should be really easy, since you already have different line heights depending on DPI, so it's just one parameter used for calculation, and one on/off option in menu.

Hi-DPI support! YAY! I've been asking for this for years!
Wanted to report I'm having similar issues with viewing the log on a Windows 10 4k display, 225% scaling.
Attached is a picture of what it looks like to me. My guess is that it's not yet honoring the DPI scaling.

I'll go slightly against the flow. Everyone seems to want things bigger, but I'd rather have them smaller. Or maybe better term would be more condensed. It's about one specific thing, line height.

I 100% agree. Why the hell I have to scroll now, where up till 3.20 I had everything fit nicely in one screen? This change was completely unnecessary!

Had to downgrade back to 3.20. Does not work well with a resolution of 3840x2160. Log was unreadable with lines overlapping.

Where can I get 3.20? This is pretty bad .....

raffav - In most cases, updated software is released before the CVE is published (https://nvd.nist.gov/vuln/detail/CVE-2020-5720)
hngjared, sid5632, null31, hel, brotherdust, proximus - We will resolve this problem in upcoming RouterOS releases. Winbox 3.20 is available here - https://download.mikrotik.com/routeros/ ... winbox.exe (winbox64.exe for 64bit version)
null31 - Can you reproduce this crash constantly? What exactly do you do? If I click with the mouse right button on a file and choose "Download" option, then WinBox works just fine for me
Sob, MichalPospichal - We will change default line height in upcoming WinBox releases

I'll go slightly against the flow. Everyone seems to want things bigger, but I'd rather have them smaller. Or maybe better term would be more condensed. It's about one specific thing, line height.

+1

Finally I see someone talking about UI efficiency and not looks!
I too want to be able to see as much information as possible in a single screen without scrolling.

I'll go slightly against the flow. Everyone seems to want things bigger, but I'd rather have them smaller. Or maybe better term would be more condensed. It's about one specific thing, line height.

+1

Finally I see someone talking about UI efficiency and not looks!
I too want to be able to see as much information as possible in a single screen without scrolling.

Come on guys, this is ridiculous. MikroTik changes line height. The next days you have to add one more firewall rule and MikroTik has to change line height again? Or how it is meant to go? Copy terminal output of "/ip firewall export" to your favorite text editor and set font size to 1. Now you can view all of your settings whatever winbox update gets released.

*scnr*

@Buster2: Don't worry, not again, because if it was even smaller, text wouldn't fit anymore.

Read my original post, I hope it was clear, I didn't suggest to unconditionally squash the lines for everyone, I understand that other people may not like it. I suggested a simple, disabled-by-default option, which I believe would be useful not only for me, but also for some others.

I know the currend trend is exactly opposite, making everything huge, 1cm fonts, vast spacing around, which results in ten lines per screen, etc. I find it horribly mistaken, because working with something like that is painful. And no, the 1px line height increase in WinBox is nowhere near that and nothing suggests that MikroTik would want to go that way. It's just that they are doing some changes now, so I suggested something related to that. Don't try to find anything else in that.

Hello!
Is it possible to correct the font on System Note? (since 3.20)
Art is not possible to add anymore, because when the note window opens, it looks weird.

Like this:
viewtopic.php?t=152988#p763628

I know that @normis said that note is not for art, but Mikrotik WiKi says different
https://wiki.mikrotik.com/wiki/Manual:System/Note

And now every router here has a ASCII art with our company logo, but it looks really awkward

Thanks.

What about designing your logo in notepad or any other text editor and copy+paste into Note?
No one except admin is able to contemplate this logo as a Note

null31 - Can you reproduce this crash constantly? What exactly do you do? If I click with the mouse right button on a file and choose "Download" option, then WinBox works just fine for me

I sent the details to support under the ticket #SUP-7835.
The problem is just with drag&drop download and yes, is reproducible. The "right click > download" is working fine.

Come on guys, this is ridiculous. MikroTik changes line height. The next days you have to add one more firewall rule and MikroTik has to change line height again? Or how it is meant to go? Copy terminal output of "/ip firewall export" to your favorite text editor and set font size to 1. Now you can view all of your settings whatever winbox update gets released.

The thing is it is not only FW rules, it is everything. Every single window now has less viewable data to work with, which makes your advice to copy it elsewhere even more riddiculous.
And no, Mikrotik does not have to change the heigh of the lines for me when I add more FW rules/whatever else, it would be completely sufficient to keep the original height.

But I would like to thank strods for noticing and hopefully bringing back the original (or variable) line height in future versions.

I think a simple menu option under "hide paswords" to enable or disable HiDPI support would suit to our needs.

I can't get WinBox to update itself this time.
I run WinBox.exe on my desktop, use "Tools -> Check for updates", can see the patch notes for v3.21 and when I click "Update" it downloads and then restarts WinBox, but is still running v3.20.
Attempting to run WinBox.exe on my desktop as admin has the same result, but it doesn't start WinBox by itself after supposed download.

I am just gonna download it off the website, but I am curious as to what the issue here is and if it is my company network or a general issue.

Note is not for art, it's for notes.

Note is not for art, it's for notes.

But I do what wiki:Note say... and CLI & WinBox difference: .
.
P.S. Beep is originally made for Beeps, not for play a "Star Wars -- The Imperial March" or "A_Bit_of_Sounds"

Like the new Winbox!!! This is a step in the right direction.
- Yes "log" is not displaying correctly for now, but "setting/Zoom out" twice and all is good.
- It also allows now to see again the "Wireless" settings correctly on one page with normal screen

good work! just correct the problems

PS: My note still looks beautiful ..... to me

@Sib:

"It allows ..." does not mean that it should be full ASCII editor.
Is it possible now to make such a piece of art? Yes or no?
As I wrote ... use any editor to prepare your logo and just paste it into a note.

font size can be increased/decreased under "Settings/Zoom In" or "Zoom Out"

Really curious to test that...

@SiB

Exactly. The wiki says you can add ASCII art to your HOME ROUTER. Your use case doesn't count your running a professional production network no ASCII for you.

Is it not possible to alter the existing ASCII to account for the new way its presented? Or to temporarily utilize a reduced complexity note?

@BartoszP

As I wrote ... use any editor to prepare your logo and just paste it into a note.

Sorry but what you say is not correct. ROS give us one Note for CLI and WinBox - not separated.
Currently we can only edit one note and this is used on both CLI motd and WinBox splashscreen who is just a new feature and should have other font with "fixed/monospaced width" propertis and give us both result's the same.

MikroTik Team, please change WinBox font at Note splashscreen to "monospaced font"="fixed width"="where all characters are identical in width" like in CLI to repair situation.

*) added support for HiDPI displays;

Finally! Thanks!
Now it looks pretty good on LInux under Wine on 4k display.

I tried both new versions (3.20 and 3.21 x64) and they both crash 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?

I got V3.21 working. I cannot explain why, but this worked.

Opening V3.19 and using the Tools / Check for Update command. This performed an in-place upgrade and in doing so overwrote the executable file.

What I was doing previously was downloading winbox64.exe directly from the MikroTik website, and running it in the same folder as my existing winbox.exe

I do not know why it was necessary to use the Tools / Check for Updates command. Prior to V3.20 my process to upgrade winbox was to simply overwrite the executable in my installation folder, which, no longer appears to work.

People who asked to do the interface smaller probably work on a FullHD monitor because on a 4K monitor (3840x2160) the interface looks incredibly small even with the maximal zoom.

Please make the interface bigger or add more zoom levels.

Compared to minimum zoom, maximum zoom has fonts a little bit less than double size. So physical size on equally sized 4k monitor (with max zoom) would be smaller than on FullHD (with min zoom). In practice, most 4k monitors are larger than FullHD. But still, if you prefer bigger fonts, I agree that even current maximum may not be enough and there should be option to zoom in even further, which shouldn't be difficult to add.

People who asked to do the interface smaller probably work on a FullHD monitor because on a 4K monitor (3840x2160) the interface looks incredibly small even with the maximal zoom.

Please make the interface bigger or add more zoom levels.

QHD, and I still prefer it smaller than the default.
The more information that can be displayed in one window at a time, the best. Otherwise, what is the point of upgrading to a higher resolution monitor? (IMHO)

Efficiency is more important to me than looks. And modern looks (ie: large everything) is a waste of screen real estate.

Can the software developer for Winbox make the columns in the LOG window resize-able please? They are currently fixed and as such when the "Zoom In" feature is used, it is impossible to see the exact time of events because the column is truncated due to it being too narrow for the field data.

I noticed lock icon (encryption indicator) in Winbox 3.21 gone (as well as the options to use encryption). Does this mean Winbox traffic is no longer being encrypted?

(I too experience problems with my 4K display with 200% scaling on Windows 1909)

Zoom In function does not remembered, so new connection to new devices gone back to default zoom...
And new zoom in function does not enlarge rows... Too bad...

Just updated to this.

On Retina screen, default presentation is way too small to read.
At max zoom, it is barely smaller than the previous Winbox, and Log window (only!) is totally unreadable because the top and bottom of every line is sheared off.

Needs at least one more zoom level; needs to remember the zoom level or be able set a default zoom level other than "smallest"; and a fix for log window is needed before this can be used in production.

Just the opposite, there is no longer any possibility to use unsecured connection in Winbox.

Which is great.

Log window (only!) is totally unreadable because the top and bottom of every line is sheared off.

a fix for log window is needed before this can be used in production.

Furthermore, /log print in Terminal is also useless because scrolling back Terminal screen to anything before the final contents results in sheared off, unreadable lines. With new WInbox, it is impossible to examine log at all without drag-and-dropping log file to local PC and examining it there. And this causes you to lose "memory" entries. Very bad regression.

Log window (only!) is totally unreadable because the top and bottom of every line is sheared off.

a fix for log window is needed before this can be used in production.

Furthermore, /log print in Terminal is also useless because scrolling back Terminal screen to anything before the final contents results in sheared off, unreadable lines. With new WInbox, it is impossible to examine log at all without drag-and-dropping log file to local PC and examining it there. And this causes you to lose "memory" entries. Very bad regression.

+1
https://alaincasault.com/wp-content/upl ... 764404.jpg

Log entry DPI issue already fixed in internal build.

Log entry DPI issue already fixed in internal build.

This is great!
When can we expect a release?

Cheers,

AC

Make font selectable! Default font - is piece of crap, really.

Log entry DPI issue already fixed in internal build.

How did they fix this? I reported above that the log window columns crop the data at the right side edge because the columns are too narrow in the zoomed view. They also lack headers to be able to manually resize them to the desired width.

Log entry DPI issue already fixed in internal build.

How did they fix this?

I guess Normis' answer means that the fix is already done and is waiting for the next release (presumably 3.22).

Didn't someone said the log for WinBox 3.21 should be fixed later with new RouterOS version?

I reported above that the log window columns crop the data at the right side edge because the columns are too narrow in the zoomed view. They also lack headers to be able to manually resize them to the desired width.

Well, yes, but that's always been a deficiency in the log window.

Just the opposite, there is no longer any possibility to use unsecured connection in Winbox.

RouterOS long-term 6.45.8
WinBox v3.21
I not use the standard admin username, but long username with also random character, for example "MyUser_HWC5RacbovLAnPtVOjYr2zstWAs022Gb".
I test to simply capture traffic of the connection to router with Wireshark and I see that the username was send in clear text in the first frame.
In any https comunication the encryption is befor of any transfer of data. As is there be for username.

Can you work to implement the encrption befor of any other data?

Waiting for your kind reply, thank you.
Best regards

In any https comunication the encryption is befor of any transfer of data.

Like SNI?

Or like DNS ?

... I refer to SSL/TLS encryction use in Https.
In this case the SNI is not applicable, and more simple because one IP[:Port] is one device.

... I refer to SSL/TLS encryction use in Https.
In this case the SNI is not applicable,

Did you ever check how SNI actually works?

Winbox v3.22 has been released:

viewtopic.php?f=21&t=158605