📣 WinBox 4 is here 📣

Announcements
2361

Thanks for checking, Paternot. It is the only application with these rendering issues - and I use quite a lot of different applications for my daily work. Maybe something with QT is misconfigured on my system. I am on xorg, modesetting driver on Intel graphics.

edit: there is a tool called “qt5ct” (Qt5 Configuration Tool) and it’s interface looks ugly as well. So I think it is some Qt issue on my system. I mostly (like 99%) use GTK based applications. Wireshark is based on Qt 6.9.0 and looks good.

I consulted the Arch Linux Wiki Qt page and found this cross-reference to HiPDI wiki article: https://wiki.archlinux.org/title/HiDPI#Qt_5

QT_ENABLE_HIGHDPI_SCALING=0 WinBox

:exploding_head::exploding_head::exploding_head:

Now THIS is something completely different. Interface has decent size even on 100% WinBox zoom level. No more rendering crapola.
It is most likely because of these default env vars on my system:

$ env | grep QT
QT_QPA_PLATFORMTHEME=qt5ct
QT_AUTO_SCREEN_SCALE_FACTOR=1
QT_ENABLE_HIGHDPI_SCALING=1

What also helps to fix jigged fonts is described in Qt6 docs: https://doc.qt.io/qt-6/highdpi.html

QT_USE_PHYSICAL_DPI=1 WinBox
2362

I welcome the small usability enhancements for the 4.0betta22 release.

However, missing expansion arrows for sizing of Windows… you have to just click and drag, and hope the window will expand… In most cases - does not work.

Update

Expansion arrows returned after the app was left open while I posted this. Returned to Winbox, and I was able to resize window with the resize arrows. Unsure why it took awhile after initially loading Winbox.

OS: Mac OS.
Screen Shot 2025-06-02 at 11.20.37 AM.png

2363

Also – why is there |6 within IP v4 and IPv6 button images.
Screen Shot 2025-06-02 at 11.26.23 AM.png

2364

Mine is using

$ env | grep QT
QT_SCREEN_SCALE_FACTORS=HDMI-0=1;DP-0=1;DP-1=1;HDMI-1=1;DP-2=1;DP-3=1;
QT_IM_MODULE=xim
QT_AUTO_SCREEN_SCALE_FACTOR=0
QT_IM_SWITCHER=imsw-multi

I’m also on
KDE Frameworks 5.115.0
Qt 5.15.12

2365

Export in Winbox4

Mikrotik send:
Thank you for contacting MikroTik Support.
Thank you for your request, if there will be more, similar requests like yours, we will see how this can be added in future versions.

2366

There is no “|6” inside these icons. It indicates a node in a bus network diagram IMHO.

2367

Finally this happened.

By the way, in previous beta outlines were added to fields, but not for all. Where are outlines for checkboxes and radio buttons? Where is the logic? It’s improved, but still looks shitty
.
Outlines.png
And glad to see improved highlighting contrast. Even though there are still no outlines, it has become better.

2368

Wasn’t even looking for anything and ran across this filter just hanging out past the box.
Screenshot 2025-06-02 200711.png

2369

It’s good to see other people riding Mikrotik for these features !

2370

Because this is deemed very essential and I don’t see any reason why they can’t support it :slight_smile:

2371

Will the port {src.Port , dsc.port }filtering feature have available?
WinBox_2q6MJj52Lo.png

2372

In the next version of RouterOS the port values will be split from the address columns for the IPv4 connection tracking table (currently already the case for IPv6) and you’ll be able to sort and filter by their values. This doesn’t depend on the WinBox version.


*) firewall - reorganized firewall connection tracking table values and make them persistent between IPv4 and IPv6;

Here you can see the relevant updates in the documentation: https://help.mikrotik.com/docs/pages/diffpagesbyversion.action?pageId=130220087&selectedPageVersions=23&selectedPageVersions=24

2373

In WinBox 3 you can filter by port, in WinBox 4 you can’t do it. It’s not about splitting.

2374

Yes, and that a special handling/hack built into WinBox 3 that parses/splits the dst-address and src-address field values. Up to 7.19.1 you don’t have access to the ports with neither /ip firewall connection find nor /ip firewall connection print proplist=. The hack is actually against the philosophy of having WinBox simply mapping what available to the command line / fetching the available property definitions from RouterOS.

That’s why the change in 7.20 is better than building the special handling into WinBox 4, because sorting & filtering would work automatically, independent of the WinBox version, and also in scripts and on command line.
conntrack-720.png

2375

Should probably say Ctrl-Scroll on Windows?

2376

Daft question, but if the only other file in the ZIP is assets/images/winbox.img, can’t you just embed that in the .exe and give us a straight-up exe like before? Winbox4.exe?

2377

Yes. This stupid folder with icon image is completely useless and annoying. When you delete it, there are no any problems and the app is working, but it creates again and again. For what? Remove it!

2378

Wee quick one, any chance of an ARM 64bit binary release? (e.g Raspberry Pi 5)

2379

I hope at some point they will offload more of the filter to the router. As far as I understand, the “winbox protocol” is not that much different from the API protocol, with the addition of the property definitions download. But in API it is possible to fetch data while giving a filter specification that will be applied by the router (i.e. it sends only the data that matches the filter).
In Winbox, when you view some data applying a strict filter, it still downloads the full data and applies the filter inside Winbox.
That can really load a (slow) connection when you are trying to view a large firewall connections table (for example) when interested in data about a single system or port or whatever.

2380

Handy feature but it is way too coarse to be useful - at least on macOS