WinBox v3.40 released!

Tue Oct 10, 2023 3:04 pm

What's new in v3.40:

Important note!!!

Upgrade from older WinBox versions will not work. Manual WinBox upgrade is required.

*) fit BTH QR code into default settings window;
*) fixed WinBox upgrade procedure (introduced in v3.39);

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

zandhaas · Tue Oct 10, 2023 3:27 pm

*) fit BTH QR code into default settings window;

Now I can see only the top 20% of the QR-code instead of the top 80% in the previous release. So it has become worse.

Tue Oct 10, 2023 4:00 pm

Also RouterOS upgrade will be required. BTH is not yet released as stable feature. Will work just fine in upcoming betas.

fragtion · Tue Oct 10, 2023 4:06 pm

I get "ERROR: Upgrade file was corrupted" when trying to upgrade from v3.38 using the "Update" button. Tried retrying it several times with same result.

winboxupgradefailed.png

So it seems the upgrade problem was introduced earlier than v3.39 ... ?

Edit: Ok, I see the news says "Upgrade from older WinBox versions will not work. Manual WinBox upgrade is required". I will just update it manually, no trouble :)

ToTheFull · Tue Oct 10, 2023 4:14 pm

Did you read TFM
Works for me, just replace old with NEW!

ErfanDL · Tue Oct 10, 2023 6:46 pm

another update without dark mode !

optio · Tue Oct 10, 2023 6:57 pm

Update works over wine :P

rextended · Tue Oct 10, 2023 7:58 pm

another update without dark mode !

Another useless post, this included.

wallywalrus · Tue Oct 10, 2023 8:34 pm

Update works over wine :P

+1 including CrossOver on MacOS

optio · Tue Oct 10, 2023 9:06 pm

Actually I'm also using CrossOver wine fork on Mac (Gcenx build), maybe with official wine it's different. Wine is supporting Windows API WinVerifyTrust, if this API is used in Winbox to verify PE certificate.

zandhaas · Tue Oct 10, 2023 9:10 pm

Also RouterOS upgrade will be required. BTH is not yet released as stable feature. Will work just fine in upcoming betas.

I'm running ROS version 7.12 beta9 in which BTH is active and configured.
Or do you mean this winbox version with BTH is only working with ROS version 7.13 betaxx and above?

Spirch · Tue Oct 10, 2023 11:11 pm

add option: auto safe mode on startup :-(

nichky · Wed Oct 11, 2023 2:36 am

another update without dark mode !

why u make them hard live?

what that will change?

vinigas · Thu Oct 19, 2023 8:26 pm

another update without dark mode !
why u make them hard live?

what that will change?

It will make people to not become narrow-eyed every time Winbox opens in dark room with dark-themed OS.

Also it probably won't happen until complete UI component library redesign (basically Winbox rewrite). Real solution is to make your community open-source tool, like what Portainer did to Docker. RouterOS have really good API for that.

gigabyte091 · Fri Oct 20, 2023 7:05 am

I agree with @vinigas, it would be nice to have dark mode...

mkx · Fri Oct 20, 2023 8:50 am

While it would be nice to have dark mode (I don't care though), the question why are certain users nagging about it with every new winbox version is highly relevant. Release threads in this forum (such as this) should be used to report bugs (possibly specific to the particular version). And lack of dark mode is not a bug, it's a missing feature. Go and harass MT via proper support channels (e.g. sales department).

RavenWing71 · Fri Oct 27, 2023 8:57 pm

Every time I execute the new Winbox64.exe on Windows 10, I get the software install warning "The app you're trying to install isn't a Microsoft-verified app" from Windows. I have also tried the 32-bit version of v3.40.
I have Windows set to warn when I'm installing an app from somewhere other than the windows store. This makes it harder for accidental installs of spyware to occur. So, I would rather not turn it off.
Note: I did not get this warning with the 32-bit v3.37.

PS: I hate forced dark mode. I work on the edge of a retail sales floor. There is so much light behind my monitor that it is nearly impossible to read most "Dark Mode" interfaces.

Fri Oct 27, 2023 9:04 pm

PS: I hate forced dark mode. I work on the edge of a retail sales floor. There is so much light behind my monitor that it is nearly impossible to read most "Dark Mode" interfaces.

who say anything about Forced ??

always a dark mode is something SELECTABLE

Fri Oct 27, 2023 9:07 pm

Every time I execute the new Winbox64.exe on Windows 10, I get the software install warning "The app you're trying to install isn't a Microsoft-verified app" from Windows.
I have Windows set to warn when I'm installing an app from somewhere other than the windows store. This makes it harder for accidental installs of spyware to occur. So, I would rather not turn it off.
Note: I did not get this warning with v3.37.

i tryed today and i dont have any warning, please re-download maybe something changed, or configure properly your system

RavenWing71 · Fri Oct 27, 2023 9:09 pm

PS: I hate forced dark mode. I work on the edge of a retail sales floor. There is so much light behind my monitor that it is nearly impossible to read most "Dark Mode" interfaces.

who say anything about Forced ??

always a dark mode is something SELECTABLE

You want to tell Ubiquiti that? They force dark mode in the settings portion of their management software...

RavenWing71 · Fri Oct 27, 2023 9:16 pm

Every time I execute the new Winbox64.exe on Windows 10, I get the software install warning "The app you're trying to install isn't a Microsoft-verified app" from Windows.
I have Windows set to warn when I'm installing an app from somewhere other than the windows store. This makes it harder for accidental installs of spyware to occur. So, I would rather not turn it off.
Note: I did not get this warning with v3.37.
i tryed today and i dont have any warning, please re-download maybe something changed, or configure properly your system

Check in the Settings app under Apps > Apps & Features heading > Choose where to get apps. Mine is set to "Anywhere, but warn me before installing an app that's not from the Microsoft Store." Every time I run v3.40 of Winbox I get the warning. For some reason Windows thinks Winbox is an installer instead of an app. It did not think this with v3.37.

K0NCTANT1N · Sun Oct 29, 2023 10:58 am

Download the application again from the website.

I don't confirm. Verified. Microsoft Windows [Version 10.0.19045.3448]

Sertik · Thu Nov 09, 2023 12:16 pm

I don’t really understand what we’re talking about here. Downloaded new Winbox. Launched. Everything is working. What is the BTH?

Thu Nov 09, 2023 12:25 pm

What is the BTH?

BTH = Back To Home
Not yet available in stable versions, only testing versions.

gigabyte091 · Thu Nov 09, 2023 3:38 pm

Correction, it's available in 7.12 stable.

Thu Nov 09, 2023 3:59 pm

Showoff ...

anav · Sun Nov 12, 2023 4:17 pm

Not all functions are in winbox though, so partially correct ;-PP

gigabyte091 · Sun Nov 12, 2023 6:08 pm

But statement was about is BTH available in 7.12 not are all functions available in Winbox :PPP

evellin · Mon Nov 27, 2023 11:37 am

Works for me on Mac with crossOver but I have still the "Open In New Window" issue.

Waiting for a MacOs native Winbox :)

sterod · Tue Nov 28, 2023 3:11 am

Has anyone else experienced the System / Reboot button in Winbox no longer works? I have to reboot all my devices using the /system reboot command from the Terminal

Tue Nov 28, 2023 6:42 am

I've done quite a bit of reboots already using Winbox 3.40 / System / Reboot ...

gigabyte091 · Tue Nov 28, 2023 7:14 am

No problem with reboots or shutdowns on 3.40.

Hejsan · Wed Dec 06, 2023 4:02 pm

I'm with @evellin :) Waiting for native macOS WinBox as well

phascogale · Thu Dec 07, 2023 1:30 am

While a native version would be good, I am finding no pain (Winbox itself aside) running Winbox in Crossover. Until yesterday I used Wine, but MacOS refused to believe it truly had permitted directory accesses without reminders, then with Sonoma 14.1.2 it started dropping out during sessions so I tried Crossover which was immediately stable (and appears to run VCDS as well, for a total digression) so I will pay money for that.

optio · Thu Dec 07, 2023 12:03 pm

There is a free macOS Crossover wine solution, mentioned in topic ?t=196622

phascogale · Thu Dec 07, 2023 12:35 pm

196622 produced no hits in Search and your mention is not a link.

Are you referring to alternative builds? I am quite happy to support codeweavers who have provided a working solution. For their price, it is not worth my time either to seek alternative builds or to find and compile the source with even slight attendant risk of 'issues'.

rextended · Thu Dec 07, 2023 1:49 pm

196622 produced no hits in Search and your mention is not a link.

Really?

viewtopic.php?t=196622

phascogale · Fri Dec 08, 2023 2:25 am

Yes, really :) but thank you for the link. There appears to be some less literal interpretation of “search for 196622” that I have missed in this forum software.

I had seen that topic before by searching Crossover so I take it that would be the Gcenx build to which I referred above.

Anyway, happy to get on with stuff using Winbox in Crossover. I finally start configuration of the RB5009 today, with a second hap ax lite to follow. Since the first Mikrotik in May I have quite enjoyed the journey despite RouterOS/Winbox idiosyncrasies.

Fri Dec 08, 2023 9:00 am

Why use crossover, when Wine works perfectly on macs? If you found an issue, let's solve it together, but there is no need to pay for commercial emulators

Kentzo · Fri Dec 08, 2023 6:31 pm

Why use crossover, when Wine works perfectly on macs?

IIRC there is no maintainer for macOS in the Wine project.

optio · Fri Dec 08, 2023 10:13 pm

Guessing norims has no need to run Dude (or any other win32 app) on Mac or is still on Intel Mac.

phascogale · Sat Dec 09, 2023 1:37 am

normis, wine worked perfectly for me for months, then I had dropouts not apparently attributable to Winbox actions on my part (i.e. doing nothing at the time), so I ascribed the problem to the 14.1.2 MacOS update and tried something else which immediately worked. I can imagine that under the hood there is no difference, that some error or other on my part or cosmic rays from the universe meant I did not properly distinguish association from cause and effect. That does not bother me. It is not as if I am attacking Wine, which I still have.

I am also influenced by the fact that a totally unrelated application useful to me installed under Crossover where it did not under Wine, one attempt each. Personal circumstances.

robmaltsystems · Sat Dec 09, 2023 2:01 pm

WinBox won't auto-upgrade. Says "ERROR: Upgrade file was corrupt":

Not a big problem but thought I'd mention it.

optio · Sat Dec 09, 2023 2:50 pm

@robmaltsystems 3rd line in 1st post (also in your screenshot)

robmaltsystems · Sat Dec 09, 2023 3:15 pm

Doh just proves that people don't read IT messages 😉 In my defence, because it failed, I didn't read any more. So change request, implement colour in the Winbox status box and make that red.

sinisa · Tue Dec 12, 2023 10:27 am

Why use crossover, when Wine works perfectly on macs? If you found an issue, let's solve it together, but there is no need to pay for commercial emulators

Speaking of "...let's solve it together...", I have reported this long time ago, viewtopic.php?p=937667#p937667, but no fix ever. Only "Works for me" and "I THINK it is a Wine issue", none of them from Mikrotik people...

So let me try again: fresh install of OpenSUSE LEAP 15.5 and OpenSUSE Tumbleweed, Wine 8.0 and 8.2.1, when you select "Open in new window" and then "Connect" it just returns to the initial screen, then after about 30 seconds new Winbox windows appears with "Router disconnected", then countdown from 5, then new window opens just fine.

I cannot believe that I an the only one seeing this...

By the way, after clicking "Connect" nothing should change in original window, cursor should remain in exactly the same spot (as it is now, the whole window is refreshed and the point of "open in new windows" is lost because I have to scroll down again to find where I was...).

I have done some tcpdump-ing, this is first attempt - unsuccessful

09:18:53.115667 IP 192.168.11.156.49786 > 192.168.11.105.8291: Flags [S], seq 2848251094, win 32120, options [mss 1460,sackOK,TS val 2736750616 ecr 0,nop,wscale 7], length 0
09:18:53.116002 IP 192.168.11.105.8291 > 192.168.11.156.49786: Flags [S.], seq 2694802751, ack 2848251095, win 65160, options [mss 1460,sackOK,TS val 3584758348 ecr 2736750616,nop,wscale 4], length 0
09:18:53.116015 IP 192.168.11.156.49786 > 192.168.11.105.8291: Flags [.], ack 1, win 251, options [nop,nop,TS val 2736750617 ecr 3584758348], length 0
09:18:53.127478 IP 192.168.11.156.49786 > 192.168.11.105.8291: Flags [P.], seq 1:42, ack 1, win 251, options [nop,nop,TS val 2736750628 ecr 3584758348], length 41
09:18:53.127817 IP 192.168.11.105.8291 > 192.168.11.156.49786: Flags [.], ack 42, win 4070, options [nop,nop,TS val 3584758359 ecr 2736750628], length 0
09:18:53.180619 IP 192.168.11.105.8291 > 192.168.11.156.49786: Flags [P.], seq 1:52, ack 42, win 4070, options [nop,nop,TS val 3584758412 ecr 2736750628], length 51
09:18:53.180630 IP 192.168.11.156.49786 > 192.168.11.105.8291: Flags [.], ack 52, win 251, options [nop,nop,TS val 2736750681 ecr 3584758412], length 0
09:18:53.181562 IP 192.168.11.156.49786 > 192.168.11.105.8291: Flags [P.], seq 42:76, ack 52, win 251, options [nop,nop,TS val 2736750682 ecr 3584758412], length 34
09:18:53.181773 IP 192.168.11.105.8291 > 192.168.11.156.49786: Flags [.], ack 76, win 4068, options [nop,nop,TS val 3584758413 ecr 2736750682], length 0
09:18:53.204018 IP 192.168.11.105.8291 > 192.168.11.156.49786: Flags [P.], seq 52:86, ack 76, win 4068, options [nop,nop,TS val 3584758436 ecr 2736750682], length 34
09:18:53.204123 IP 192.168.11.156.49786 > 192.168.11.105.8291: Flags [P.], seq 76:192, ack 86, win 251, options [nop,nop,TS val 2736750705 ecr 3584758436], length 116
09:18:53.204420 IP 192.168.11.105.8291 > 192.168.11.156.49786: Flags [.], ack 192, win 4061, options [nop,nop,TS val 3584758436 ecr 2736750705], length 0
09:18:53.206168 IP 192.168.11.105.8291 > 192.168.11.156.49786: Flags [P.], seq 86:460, ack 192, win 4061, options [nop,nop,TS val 3584758438 ecr 2736750705], length 374
09:18:53.206276 IP 192.168.11.156.49786 > 192.168.11.105.8291: Flags [P.], seq 192:308, ack 460, win 249, options [nop,nop,TS val 2736750707 ecr 3584758438], length 116
09:18:53.206534 IP 192.168.11.105.8291 > 192.168.11.156.49786: Flags [.], ack 308, win 4054, options [nop,nop,TS val 3584758438 ecr 2736750707], length 0
09:18:53.207344 IP 192.168.11.105.8291 > 192.168.11.156.49786: Flags [P.], seq 460:592, ack 308, win 4054, options [nop,nop,TS val 3584758439 ecr 2736750707], length 132
09:18:53.208311 IP 192.168.11.156.49786 > 192.168.11.105.8291: Flags [P.], seq 308:440, ack 592, win 249, options [nop,nop,TS val 2736750709 ecr 3584758439], length 132
09:18:53.208568 IP 192.168.11.105.8291 > 192.168.11.156.49786: Flags [.], ack 440, win 4046, options [nop,nop,TS val 3584758440 ecr 2736750709], length 0
09:18:53.209473 IP 192.168.11.105.8291 > 192.168.11.156.49786: Flags [P.], seq 592:1740, ack 440, win 4046, options [nop,nop,TS val 3584758441 ecr 2736750709], length 1148
09:18:53.210023 IP 192.168.11.156.49786 > 192.168.11.105.8291: Flags [P.], seq 440:572, ack 1740, win 249, options [nop,nop,TS val 2736750711 ecr 3584758441], length 132
09:18:53.210258 IP 192.168.11.105.8291 > 192.168.11.156.49786: Flags [.], ack 572, win 4038, options [nop,nop,TS val 3584758442 ecr 2736750711], length 0
09:18:53.211145 IP 192.168.11.105.8291 > 192.168.11.156.49786: Flags [P.], seq 1740:1888, ack 572, win 4038, options [nop,nop,TS val 3584758443 ecr 2736750711], length 148
09:18:53.252913 IP 192.168.11.156.49786 > 192.168.11.105.8291: Flags [.], ack 1888, win 249, options [nop,nop,TS val 2736750754 ecr 3584758443], length 0

and this is ~35 seconds later

09:19:28.429673 IP 192.168.11.156.50344 > 192.168.11.105.8291: Flags [S], seq 2116529504, win 32120, options [mss 1460,sackOK,TS val 2736785930 ecr 0,nop,wscale 7], length 0
09:19:28.430054 IP 192.168.11.105.8291 > 192.168.11.156.50344: Flags [S.], seq 3680094689, ack 2116529505, win 65160, options [mss 1460,sackOK,TS val 3584793661 ecr 2736785930,nop,wscale 4], length 0
09:19:28.430067 IP 192.168.11.156.50344 > 192.168.11.105.8291: Flags [.], ack 1, win 251, options [nop,nop,TS val 2736785931 ecr 3584793661], length 0
09:19:28.441530 IP 192.168.11.156.50344 > 192.168.11.105.8291: Flags [P.], seq 1:42, ack 1, win 251, options [nop,nop,TS val 2736785942 ecr 3584793661], length 41
09:19:28.441875 IP 192.168.11.105.8291 > 192.168.11.156.50344: Flags [.], ack 42, win 4070, options [nop,nop,TS val 3584793673 ecr 2736785942], length 0
09:19:28.460981 IP 192.168.11.105.8291 > 192.168.11.156.50344: Flags [P.], seq 1:52, ack 42, win 4070, options [nop,nop,TS val 3584793692 ecr 2736785942], length 51
09:19:28.460989 IP 192.168.11.156.50344 > 192.168.11.105.8291: Flags [.], ack 52, win 251, options [nop,nop,TS val 2736785962 ecr 3584793692], length 0
09:19:28.461867 IP 192.168.11.156.50344 > 192.168.11.105.8291: Flags [P.], seq 42:76, ack 52, win 251, options [nop,nop,TS val 2736785963 ecr 3584793692], length 34
09:19:28.462033 IP 192.168.11.105.8291 > 192.168.11.156.50344: Flags [.], ack 76, win 4068, options [nop,nop,TS val 3584793693 ecr 2736785963], length 0
09:19:28.489387 IP 192.168.11.105.8291 > 192.168.11.156.50344: Flags [P.], seq 52:86, ack 76, win 4068, options [nop,nop,TS val 3584793721 ecr 2736785963], length 34
09:19:28.489605 IP 192.168.11.156.50344 > 192.168.11.105.8291: Flags [P.], seq 76:192, ack 86, win 251, options [nop,nop,TS val 2736785990 ecr 3584793721], length 116
09:19:28.489920 IP 192.168.11.105.8291 > 192.168.11.156.50344: Flags [.], ack 192, win 4061, options [nop,nop,TS val 3584793721 ecr 2736785990], length 0
09:19:28.492581 IP 192.168.11.105.8291 > 192.168.11.156.50344: Flags [P.], seq 86:460, ack 192, win 4061, options [nop,nop,TS val 3584793724 ecr 2736785990], length 374
09:19:28.492724 IP 192.168.11.156.50344 > 192.168.11.105.8291: Flags [P.], seq 192:308, ack 460, win 249, options [nop,nop,TS val 2736785994 ecr 3584793724], length 116
09:19:28.493013 IP 192.168.11.105.8291 > 192.168.11.156.50344: Flags [.], ack 308, win 4054, options [nop,nop,TS val 3584793724 ecr 2736785994], length 0
09:19:28.494076 IP 192.168.11.105.8291 > 192.168.11.156.50344: Flags [P.], seq 460:592, ack 308, win 4054, options [nop,nop,TS val 3584793725 ecr 2736785994], length 132
09:19:28.496609 IP 192.168.11.156.50344 > 192.168.11.105.8291: Flags [P.], seq 308:440, ack 592, win 249, options [nop,nop,TS val 2736785997 ecr 3584793725], length 132
09:19:28.496945 IP 192.168.11.105.8291 > 192.168.11.156.50344: Flags [.], ack 440, win 4046, options [nop,nop,TS val 3584793728 ecr 2736785997], length 0
09:19:28.498084 IP 192.168.11.105.8291 > 192.168.11.156.50344: Flags [P.], seq 592:1740, ack 440, win 4046, options [nop,nop,TS val 3584793729 ecr 2736785997], length 1148
09:19:28.498810 IP 192.168.11.156.50344 > 192.168.11.105.8291: Flags [P.], seq 440:572, ack 1740, win 249, options [nop,nop,TS val 2736786000 ecr 3584793729], length 132
09:19:28.499088 IP 192.168.11.105.8291 > 192.168.11.156.50344: Flags [.], ack 572, win 4038, options [nop,nop,TS val 3584793730 ecr 2736786000], length 0
09:19:28.500265 IP 192.168.11.105.8291 > 192.168.11.156.50344: Flags [P.], seq 1740:1888, ack 572, win 4038, options [nop,nop,TS val 3584793732 ecr 2736786000], length 148
09:19:28.534424 IP 192.168.11.156.50344 > 192.168.11.105.8291: Flags [P.], seq 572:672, ack 1888, win 249, options [nop,nop,TS val 2736786035 ecr 3584793732], length 100
09:19:28.534789 IP 192.168.11.105.8291 > 192.168.11.156.50344: Flags [.], ack 672, win 4032, options [nop,nop,TS val 3584793766 ecr 2736786035], length 0
09:19:28.536356 IP 192.168.11.105.8291 > 192.168.11.156.50344: Flags [P.], seq 1888:2004, ack 672, win 4032, options [nop,nop,TS val 3584793768 ecr 2736786035], length 116
09:19:28.579582 IP 192.168.11.156.50344 > 192.168.11.105.8291: Flags [.], ack 2004, win 249, options [nop,nop,TS val 2736786080 ecr 3584793768], length 0
09:19:28.602815 IP 192.168.11.156.50344 > 192.168.11.105.8291: Flags [P.], seq 672:788, ack 2004, win 249, options [nop,nop,TS val 2736786104 ecr 3584793768], length 116
09:19:28.624811 IP 192.168.11.156.50344 > 192.168.11.105.8291: Flags [.], seq 788:2236, ack 2004, win 249, options [nop,nop,TS val 2736786126 ecr 3584793768], length 1448
09:19:28.625489 IP 192.168.11.105.8291 > 192.168.11.156.50344: Flags [.], ack 2236, win 4005, options [nop,nop,TS val 3584793857 ecr 2736786104], length 0
09:19:28.625503 IP 192.168.11.156.50344 > 192.168.11.105.8291: Flags [P.], seq 2236:2308, ack 2004, win 249, options [nop,nop,TS val 2736786126 ecr 3584793857], length 72
09:19:28.627110 IP 192.168.11.156.50344 > 192.168.11.105.8291: Flags [.], seq 2308:3756, ack 2004, win 249, options [nop,nop,TS val 2736786128 ecr 3584793857], length 1448
09:19:28.627676 IP 192.168.11.105.8291 > 192.168.11.156.50344: Flags [.], ack 3756, win 4005, options [nop,nop,TS val 3584793859 ecr 2736786126], length 0
09:19:28.627678 IP 192.168.11.156.50344 > 192.168.11.105.8291: Flags [P.], seq 3756:4340, ack 2004, win 249, options [nop,nop,TS val 2736786128 ecr 3584793859], length 584
09:19:28.631744 IP 192.168.11.105.8291 > 192.168.11.156.50344: Flags [P.], seq 2004:2120, ack 4340, win 4005, options [nop,nop,TS val 3584793863 ecr 2736786128], length 116
09:19:28.631748 IP 192.168.11.156.50344 > 192.168.11.105.8291: Flags [P.], seq 4340:5396, ack 2120, win 249, options [nop,nop,TS val 2736786133 ecr 3584793863], length 1056
09:19:28.643868 IP 192.168.11.105.8291 > 192.168.11.156.50344: Flags [.], seq 2120:3568, ack 5396, win 4005, options [nop,nop,TS val 3584793875 ecr 2736786133], length 1448
09:19:28.643941 IP 192.168.11.105.8291 > 192.168.11.156.50344: Flags [P.], seq 3568:5016, ack 5396, win 4005, options [nop,nop,TS val 3584793875 ecr 2736786133], length 1448
09:19:28.643947 IP 192.168.11.156.50344 > 192.168.11.105.8291: Flags [.], ack 5016, win 249, options [nop,nop,TS val 2736786145 ecr 3584793875], length 0
09:19:28.644030 IP 192.168.11.156.50344 > 192.168.11.105.8291: Flags [P.], seq 5396:5512, ack 5016, win 249, options [nop,nop,TS val 2736786145 ecr 3584793875], length 116
09:19:28.644079 IP 192.168.11.105.8291 > 192.168.11.156.50344: Flags [.], seq 5016:6464, ack 5396, win 4005, options [nop,nop,TS val 3584793875 ecr 2736786133], length 1448
09:19:28.644181 IP 192.168.11.105.8291 > 192.168.11.156.50344: Flags [P.], seq 6464:7912, ack 5396, win 4005, options [nop,nop,TS val 3584793875 ecr 2736786133], length 1448
....

So, "...let's solve it together...", please.

Tue Dec 12, 2023 12:11 pm

Guessing norims has no need to run Dude (or any other win32 app) on Mac or is still on Intel Mac.

When was last update to Dude?

optio · Tue Dec 12, 2023 1:00 pm

It was just example for comment "Why use crossover, when Wine works perfectly on macs?". It's not in all cases. And others also mentioned issues with 64-bit app. I had Winbox window freezes several times and I had to kill process (not sure if is related to wine) but it doesn't occur on other applications which are run by wine.

Tue Dec 12, 2023 1:11 pm

We have same situation on our local setups, will see if this can be fixed in upcoming releases, thanks for report.

Why use crossover, when Wine works perfectly on macs? If you found an issue, let's solve it together, but there is no need to pay for commercial emulators

Speaking of "...let's solve it together...", I have reported this long time ago, viewtopic.php?p=937667#p937667, but no fix ever. Only "Works for me" and "I THINK it is a Wine issue", none of them from Mikrotik people...

So let me try again: fresh install of OpenSUSE LEAP 15.5 and OpenSUSE Tumbleweed, Wine 8.0 and 8.2.1, when you select "Open in new window" and then "Connect" it just returns to the initial screen, then after about 30 seconds new Winbox windows appears with "Router disconnected", then countdown from 5, then new window opens just fine.

I cannot believe that I an the only one seeing this...

By the way, after clicking "Connect" nothing should change in original window, cursor should remain in exactly the same spot (as it is now, the whole window is refreshed and the point of "open in new windows" is lost because I have to scroll down again to find where I was...).

I have done some tcpdump-ing, this is first attempt - unsuccessful

09:18:53.115667 IP 192.168.11.156.49786 > 192.168.11.105.8291: Flags [S], seq 2848251094, win 32120, options [mss 1460,sackOK,TS val 2736750616 ecr 0,nop,wscale 7], length 0
09:18:53.116002 IP 192.168.11.105.8291 > 192.168.11.156.49786: Flags [S.], seq 2694802751, ack 2848251095, win 65160, options [mss 1460,sackOK,TS val 3584758348 ecr 2736750616,nop,wscale 4], length 0
09:18:53.116015 IP 192.168.11.156.49786 > 192.168.11.105.8291: Flags [.], ack 1, win 251, options [nop,nop,TS val 2736750617 ecr 3584758348], length 0
09:18:53.127478 IP 192.168.11.156.49786 > 192.168.11.105.8291: Flags [P.], seq 1:42, ack 1, win 251, options [nop,nop,TS val 2736750628 ecr 3584758348], length 41
09:18:53.127817 IP 192.168.11.105.8291 > 192.168.11.156.49786: Flags [.], ack 42, win 4070, options [nop,nop,TS val 3584758359 ecr 2736750628], length 0
09:18:53.180619 IP 192.168.11.105.8291 > 192.168.11.156.49786: Flags [P.], seq 1:52, ack 42, win 4070, options [nop,nop,TS val 3584758412 ecr 2736750628], length 51
09:18:53.180630 IP 192.168.11.156.49786 > 192.168.11.105.8291: Flags [.], ack 52, win 251, options [nop,nop,TS val 2736750681 ecr 3584758412], length 0
09:18:53.181562 IP 192.168.11.156.49786 > 192.168.11.105.8291: Flags [P.], seq 42:76, ack 52, win 251, options [nop,nop,TS val 2736750682 ecr 3584758412], length 34
09:18:53.181773 IP 192.168.11.105.8291 > 192.168.11.156.49786: Flags [.], ack 76, win 4068, options [nop,nop,TS val 3584758413 ecr 2736750682], length 0
09:18:53.204018 IP 192.168.11.105.8291 > 192.168.11.156.49786: Flags [P.], seq 52:86, ack 76, win 4068, options [nop,nop,TS val 3584758436 ecr 2736750682], length 34
09:18:53.204123 IP 192.168.11.156.49786 > 192.168.11.105.8291: Flags [P.], seq 76:192, ack 86, win 251, options [nop,nop,TS val 2736750705 ecr 3584758436], length 116
09:18:53.204420 IP 192.168.11.105.8291 > 192.168.11.156.49786: Flags [.], ack 192, win 4061, options [nop,nop,TS val 3584758436 ecr 2736750705], length 0
09:18:53.206168 IP 192.168.11.105.8291 > 192.168.11.156.49786: Flags [P.], seq 86:460, ack 192, win 4061, options [nop,nop,TS val 3584758438 ecr 2736750705], length 374
09:18:53.206276 IP 192.168.11.156.49786 > 192.168.11.105.8291: Flags [P.], seq 192:308, ack 460, win 249, options [nop,nop,TS val 2736750707 ecr 3584758438], length 116
09:18:53.206534 IP 192.168.11.105.8291 > 192.168.11.156.49786: Flags [.], ack 308, win 4054, options [nop,nop,TS val 3584758438 ecr 2736750707], length 0
09:18:53.207344 IP 192.168.11.105.8291 > 192.168.11.156.49786: Flags [P.], seq 460:592, ack 308, win 4054, options [nop,nop,TS val 3584758439 ecr 2736750707], length 132
09:18:53.208311 IP 192.168.11.156.49786 > 192.168.11.105.8291: Flags [P.], seq 308:440, ack 592, win 249, options [nop,nop,TS val 2736750709 ecr 3584758439], length 132
09:18:53.208568 IP 192.168.11.105.8291 > 192.168.11.156.49786: Flags [.], ack 440, win 4046, options [nop,nop,TS val 3584758440 ecr 2736750709], length 0
09:18:53.209473 IP 192.168.11.105.8291 > 192.168.11.156.49786: Flags [P.], seq 592:1740, ack 440, win 4046, options [nop,nop,TS val 3584758441 ecr 2736750709], length 1148
09:18:53.210023 IP 192.168.11.156.49786 > 192.168.11.105.8291: Flags [P.], seq 440:572, ack 1740, win 249, options [nop,nop,TS val 2736750711 ecr 3584758441], length 132
09:18:53.210258 IP 192.168.11.105.8291 > 192.168.11.156.49786: Flags [.], ack 572, win 4038, options [nop,nop,TS val 3584758442 ecr 2736750711], length 0
09:18:53.211145 IP 192.168.11.105.8291 > 192.168.11.156.49786: Flags [P.], seq 1740:1888, ack 572, win 4038, options [nop,nop,TS val 3584758443 ecr 2736750711], length 148
09:18:53.252913 IP 192.168.11.156.49786 > 192.168.11.105.8291: Flags [.], ack 1888, win 249, options [nop,nop,TS val 2736750754 ecr 3584758443], length 0

and this is ~35 seconds later

09:19:28.429673 IP 192.168.11.156.50344 > 192.168.11.105.8291: Flags [S], seq 2116529504, win 32120, options [mss 1460,sackOK,TS val 2736785930 ecr 0,nop,wscale 7], length 0
09:19:28.430054 IP 192.168.11.105.8291 > 192.168.11.156.50344: Flags [S.], seq 3680094689, ack 2116529505, win 65160, options [mss 1460,sackOK,TS val 3584793661 ecr 2736785930,nop,wscale 4], length 0
09:19:28.430067 IP 192.168.11.156.50344 > 192.168.11.105.8291: Flags [.], ack 1, win 251, options [nop,nop,TS val 2736785931 ecr 3584793661], length 0
09:19:28.441530 IP 192.168.11.156.50344 > 192.168.11.105.8291: Flags [P.], seq 1:42, ack 1, win 251, options [nop,nop,TS val 2736785942 ecr 3584793661], length 41
09:19:28.441875 IP 192.168.11.105.8291 > 192.168.11.156.50344: Flags [.], ack 42, win 4070, options [nop,nop,TS val 3584793673 ecr 2736785942], length 0
09:19:28.460981 IP 192.168.11.105.8291 > 192.168.11.156.50344: Flags [P.], seq 1:52, ack 42, win 4070, options [nop,nop,TS val 3584793692 ecr 2736785942], length 51
09:19:28.460989 IP 192.168.11.156.50344 > 192.168.11.105.8291: Flags [.], ack 52, win 251, options [nop,nop,TS val 2736785962 ecr 3584793692], length 0
09:19:28.461867 IP 192.168.11.156.50344 > 192.168.11.105.8291: Flags [P.], seq 42:76, ack 52, win 251, options [nop,nop,TS val 2736785963 ecr 3584793692], length 34
09:19:28.462033 IP 192.168.11.105.8291 > 192.168.11.156.50344: Flags [.], ack 76, win 4068, options [nop,nop,TS val 3584793693 ecr 2736785963], length 0
09:19:28.489387 IP 192.168.11.105.8291 > 192.168.11.156.50344: Flags [P.], seq 52:86, ack 76, win 4068, options [nop,nop,TS val 3584793721 ecr 2736785963], length 34
09:19:28.489605 IP 192.168.11.156.50344 > 192.168.11.105.8291: Flags [P.], seq 76:192, ack 86, win 251, options [nop,nop,TS val 2736785990 ecr 3584793721], length 116
09:19:28.489920 IP 192.168.11.105.8291 > 192.168.11.156.50344: Flags [.], ack 192, win 4061, options [nop,nop,TS val 3584793721 ecr 2736785990], length 0
09:19:28.492581 IP 192.168.11.105.8291 > 192.168.11.156.50344: Flags [P.], seq 86:460, ack 192, win 4061, options [nop,nop,TS val 3584793724 ecr 2736785990], length 374
09:19:28.492724 IP 192.168.11.156.50344 > 192.168.11.105.8291: Flags [P.], seq 192:308, ack 460, win 249, options [nop,nop,TS val 2736785994 ecr 3584793724], length 116
09:19:28.493013 IP 192.168.11.105.8291 > 192.168.11.156.50344: Flags [.], ack 308, win 4054, options [nop,nop,TS val 3584793724 ecr 2736785994], length 0
09:19:28.494076 IP 192.168.11.105.8291 > 192.168.11.156.50344: Flags [P.], seq 460:592, ack 308, win 4054, options [nop,nop,TS val 3584793725 ecr 2736785994], length 132
09:19:28.496609 IP 192.168.11.156.50344 > 192.168.11.105.8291: Flags [P.], seq 308:440, ack 592, win 249, options [nop,nop,TS val 2736785997 ecr 3584793725], length 132
09:19:28.496945 IP 192.168.11.105.8291 > 192.168.11.156.50344: Flags [.], ack 440, win 4046, options [nop,nop,TS val 3584793728 ecr 2736785997], length 0
09:19:28.498084 IP 192.168.11.105.8291 > 192.168.11.156.50344: Flags [P.], seq 592:1740, ack 440, win 4046, options [nop,nop,TS val 3584793729 ecr 2736785997], length 1148
09:19:28.498810 IP 192.168.11.156.50344 > 192.168.11.105.8291: Flags [P.], seq 440:572, ack 1740, win 249, options [nop,nop,TS val 2736786000 ecr 3584793729], length 132
09:19:28.499088 IP 192.168.11.105.8291 > 192.168.11.156.50344: Flags [.], ack 572, win 4038, options [nop,nop,TS val 3584793730 ecr 2736786000], length 0
09:19:28.500265 IP 192.168.11.105.8291 > 192.168.11.156.50344: Flags [P.], seq 1740:1888, ack 572, win 4038, options [nop,nop,TS val 3584793732 ecr 2736786000], length 148
09:19:28.534424 IP 192.168.11.156.50344 > 192.168.11.105.8291: Flags [P.], seq 572:672, ack 1888, win 249, options [nop,nop,TS val 2736786035 ecr 3584793732], length 100
09:19:28.534789 IP 192.168.11.105.8291 > 192.168.11.156.50344: Flags [.], ack 672, win 4032, options [nop,nop,TS val 3584793766 ecr 2736786035], length 0
09:19:28.536356 IP 192.168.11.105.8291 > 192.168.11.156.50344: Flags [P.], seq 1888:2004, ack 672, win 4032, options [nop,nop,TS val 3584793768 ecr 2736786035], length 116
09:19:28.579582 IP 192.168.11.156.50344 > 192.168.11.105.8291: Flags [.], ack 2004, win 249, options [nop,nop,TS val 2736786080 ecr 3584793768], length 0
09:19:28.602815 IP 192.168.11.156.50344 > 192.168.11.105.8291: Flags [P.], seq 672:788, ack 2004, win 249, options [nop,nop,TS val 2736786104 ecr 3584793768], length 116
09:19:28.624811 IP 192.168.11.156.50344 > 192.168.11.105.8291: Flags [.], seq 788:2236, ack 2004, win 249, options [nop,nop,TS val 2736786126 ecr 3584793768], length 1448
09:19:28.625489 IP 192.168.11.105.8291 > 192.168.11.156.50344: Flags [.], ack 2236, win 4005, options [nop,nop,TS val 3584793857 ecr 2736786104], length 0
09:19:28.625503 IP 192.168.11.156.50344 > 192.168.11.105.8291: Flags [P.], seq 2236:2308, ack 2004, win 249, options [nop,nop,TS val 2736786126 ecr 3584793857], length 72
09:19:28.627110 IP 192.168.11.156.50344 > 192.168.11.105.8291: Flags [.], seq 2308:3756, ack 2004, win 249, options [nop,nop,TS val 2736786128 ecr 3584793857], length 1448
09:19:28.627676 IP 192.168.11.105.8291 > 192.168.11.156.50344: Flags [.], ack 3756, win 4005, options [nop,nop,TS val 3584793859 ecr 2736786126], length 0
09:19:28.627678 IP 192.168.11.156.50344 > 192.168.11.105.8291: Flags [P.], seq 3756:4340, ack 2004, win 249, options [nop,nop,TS val 2736786128 ecr 3584793859], length 584
09:19:28.631744 IP 192.168.11.105.8291 > 192.168.11.156.50344: Flags [P.], seq 2004:2120, ack 4340, win 4005, options [nop,nop,TS val 3584793863 ecr 2736786128], length 116
09:19:28.631748 IP 192.168.11.156.50344 > 192.168.11.105.8291: Flags [P.], seq 4340:5396, ack 2120, win 249, options [nop,nop,TS val 2736786133 ecr 3584793863], length 1056
09:19:28.643868 IP 192.168.11.105.8291 > 192.168.11.156.50344: Flags [.], seq 2120:3568, ack 5396, win 4005, options [nop,nop,TS val 3584793875 ecr 2736786133], length 1448
09:19:28.643941 IP 192.168.11.105.8291 > 192.168.11.156.50344: Flags [P.], seq 3568:5016, ack 5396, win 4005, options [nop,nop,TS val 3584793875 ecr 2736786133], length 1448
09:19:28.643947 IP 192.168.11.156.50344 > 192.168.11.105.8291: Flags [.], ack 5016, win 249, options [nop,nop,TS val 2736786145 ecr 3584793875], length 0
09:19:28.644030 IP 192.168.11.156.50344 > 192.168.11.105.8291: Flags [P.], seq 5396:5512, ack 5016, win 249, options [nop,nop,TS val 2736786145 ecr 3584793875], length 116
09:19:28.644079 IP 192.168.11.105.8291 > 192.168.11.156.50344: Flags [.], seq 5016:6464, ack 5396, win 4005, options [nop,nop,TS val 3584793875 ecr 2736786133], length 1448
09:19:28.644181 IP 192.168.11.105.8291 > 192.168.11.156.50344: Flags [P.], seq 6464:7912, ack 5396, win 4005, options [nop,nop,TS val 3584793875 ecr 2736786133], length 1448
....

So, "...let's solve it together...", please.

pe1chl · Tue Dec 12, 2023 5:15 pm

It would also be nice when there would be a possibility to connect to a router in the Addresses table without having to specify username and password.
So when you start "winbox routername" it would connect.
Now, that only works for "winbox routername username password", when used without the username and password it does correctly select the entry from the Addresses table, but it does not connect.

sinisa · Wed Dec 13, 2023 11:50 am

We have same situation on our local setups, will see if this can be fixed in upcoming releases, thanks for report.

Thank you!

I am always ready to test alpha/beta/rc versions if you need me to...

stewartpe · Thu Dec 14, 2023 9:26 am

There seems to be a scaling bug in flood-ping in WinBox that goes back to at least v3.18.

The timeout value is in 10s of milliseconds. Min, Avg, and Max RTT are all in milliseconds.

With the default value of 1000, you'll be waiting 10 full seconds to continue from a missed ping. Just cut the value to 10 if you're expecting ping times below 100 ms.

jasweb · Mon Jan 08, 2024 8:04 am

Ok, for those getting the Upgrade Error "currupt download" on OSX (Wine), open the Winbox-mac.app package contents and just replace the winbox64.exe under Resources folder.

And "Bob's your Uncle".

sterod · Mon Jan 08, 2024 3:06 pm

I have an problem with WinBox. When I use the "System / Reboot" command from the GUI, I am prompted to confirm, and I select Yes, however after the Winbox window automatically closes, I log back into the device and I see that it has not rebooted. The only way I can reboot a device using WinBox is to run the /system reboot command from a terminal window. I can reproduce this problem to show evidence it is occurring. Please advise how I can get this resolved through official support. Thank You

Mon Jan 08, 2024 4:17 pm

Please advise how I can get this resolved through official support.

By contacting the "official support" first, I guess.
https://help.mikrotik.com/servicedesk/servicedesk or support@mikrotik.com

nmt1900 · Thu Jan 11, 2024 2:32 pm

Actually I'm also using CrossOver wine fork on Mac (Gcenx build), maybe with official wine it's different. Wine is supporting Windows API WinVerifyTrust, if this API is used in Winbox to verify PE certificate.

Winbox with Gcenx built wine has one big problem on Mac which screws up all field entries containing commas and periods

It is in attachment

Mikrotik support states that this is "not their problem". So much about great interoperability...

rextended · Thu Jan 11, 2024 2:53 pm

It is not MikroTik's responsibility to operate third-party software.
Did you ask Gcenx and Apple instead?
Only they at most can say something about it, not just any person passing through the forum...

It's called WinBox, not MacBox or... er... WineBox...
so if you want to run it on another platform that's your business.

Thu Jan 11, 2024 2:58 pm

Don't use pre-pacaged Winbox software from 3rd party sources.
wine-8 and winbox64 works perfectly with all functionality and can self-upgrade

nmt1900 · Thu Jan 11, 2024 3:02 pm

So much I can tell that problem is not present with older Wine versions (and does not seem to depend on Winbox version). It would be good to get to the root of this problem though...

rextended · Thu Jan 11, 2024 3:07 pm

So, more than obviously at this point, given what you write, you need to contact those who develop Wine...

nmt1900 · Thu Jan 11, 2024 3:08 pm

Interesting thing here is that Dude does not have this problem with newest Wine engine - but Btest app does. There should be some common denominator explaining this...

nmt1900 · Thu Jan 11, 2024 3:18 pm

Don't use pre-pacaged Winbox software from 3rd party sources.
wine-8 and winbox64 works perfectly with all functionality and can self-upgrade

This not pre-packaged Winbox (like Winbox4mac or something like that). It is Wine instance created from scratch.

jbl42 · Thu Jan 11, 2024 3:39 pm

Winbox with Gcenx built wine has one big problem on Mac which screws up all field entries containing commas and periods

On my Mac (M2Pro, Sonoma), winbox 3.40 runs without issues using Gcenx wine builds available at
https://github.com/Gcenx/macOS_Wine_builds
Even winbox self update works.

optio · Thu Jan 11, 2024 4:29 pm

On my Mac (M2Pro, Sonoma), winbox 3.40 runs without issues using Gcenx wine builds ...

Except it crashes on some cases viewtopic.php?t=203174#p1047711, not sure if is related to that wine build or is generally Winbox issue.

nmt1900 · Thu Jan 11, 2024 4:44 pm

Winbox with Gcenx built wine has one big problem on Mac which screws up all field entries containing commas and periods
On my Mac (M2Pro, Sonoma), winbox 3.40 runs without issues using Gcenx wine builds available at
https://github.com/Gcenx/macOS_Wine_builds
Even winbox self update works.

Problem is not present with 21.2.0-1 but any newer engine exposes the problem. Who knows maybe it can be related to macOS version differences (it is possible that behaviour can be different on macOS 12 on Intel machine than on newer Apple Silicon machines)...

jbl42 · Thu Jan 11, 2024 11:07 pm

I'm using wine-8.21-staging on macOS 14.2.1
Of course different macOS and wine versions might have different problems.

PS
I'm not sure what those version numbers in your screenshot are referring to. Current wine version is 8.x (9.0 is in RC state)

nmt1900 · Thu Jan 11, 2024 11:28 pm

CX21.2.0 - Wine 6.0.2
CX22.1.1 - Wine 7.7
CX23 - Wine 8.0.1

imatmtf · Mon Jan 22, 2024 10:33 am

It would be helpful to rewrite winbox in Java, to run it everywhere (BSD unix and Linux) with no need for a Windows virtual machine or emulator.

Mon Jan 22, 2024 10:38 am

Why Java. There are better options

Mon Jan 22, 2024 10:39 am

Screenshot 2024-01-22 at 10.39.46.jpg

infabo · Mon Jan 22, 2024 10:44 am

OMG - thanks for the teaser!

rextended · Mon Jan 22, 2024 11:05 am

@normis, when? :))

pe1chl · Mon Jan 22, 2024 11:13 am

What do you mean "teaser"? That is just a wine install, that has been possible for a long time.

rextended · Mon Jan 22, 2024 11:18 am

What do you mean "teaser"? That is just a wine install, that has been possible for a long time.

The Winbox icon...? (not the winbox64.exe)

Is just a wine link with custom icon?

massinia · Mon Jan 22, 2024 11:46 am

What do you mean "teaser"? That is just a wine install, that has been possible for a long time.

winbox macOS.jpg

Look better 😛

Thanks Normis 🎉

mkx · Mon Jan 22, 2024 12:01 pm

I don't understand these screenshots. They must be in macOSish. Anthing in Linuxish? 😛

Mon Jan 22, 2024 1:32 pm

You want too much from a teaser. Teaser makes you think. Try it.

anav · Mon Jan 22, 2024 1:51 pm

rextended you see more with one eye, than most with two eyes............

Mon Jan 22, 2024 2:16 pm

rextended you see more with one eye, than most with two eyes............

He will change the avatar again soon, and then nobody understands your message anymore.

rextended · Mon Jan 22, 2024 2:37 pm

For historical purposes only...

felice.png

Amm0 · Mon Jan 22, 2024 3:23 pm

What do you mean "teaser"? That is just a wine install, that has been possible for a long time.
Is just a wine link with custom icon?

Doubt it. Already 3rd parties that package wine+winbox into an Mac app to get an icon... but given @normis always note this about them it be pretty ironic:

Don't use pre-pacaged Winbox software from 3rd party sources.

In some older threads, there were teasers about upcoming "multiplatform client". So seemingly were at they picked an icon for it stage. ;). And, apparently it's not Java-based.

infabo · Mon Jan 22, 2024 3:50 pm

It's still called Winbox. What does the name stand for? "Box of windows?" - would at least describe the look of the application. ROFLMA

pe1chl · Mon Jan 22, 2024 3:59 pm

Actually I would prefer when changes like what I mentioned Tue Dec 12, 2023 4:15 pm are implemented (to allow connection to some device directly from a desktop icon).
And also to change the .viw files to a readable/editable format (e.g. .json)...

optio · Mon Jan 22, 2024 5:37 pm

"Teaser" - lol

wb_mac.png

under that...

wb_contents.png

Amm0 · Mon Jan 22, 2024 5:47 pm

It's still called Winbox.

Well, Xbox was taken.

FWIW, viewtopic.php?p=1031799&hilit=multi+platform#p1031799 from Dec 2021:

We do have plans for true multi platform Winbox. Finally. Let this be a teaser for 2022 :) No ETA and no promises though.

infabo · Mon Jan 22, 2024 5:57 pm

no promises though.

Indeed.

Cha0s · Mon Jan 22, 2024 7:58 pm

It would be helpful to rewrite winbox in Java, to run it everywhere (BSD unix and Linux) with no need for a Windows virtual machine or emulator.

That would be truly awful.
For us using WinBox everyday, all day, it's a tool that's being opened/closed tens or even hundreds of times within the day.
The amount of computer resources and time that will be wasted waiting for java to load every time would be indescribably stupid.

optio · Mon Jan 22, 2024 8:10 pm

It "just" needs rewrite to use some cross-platform GUI library like Qt or GTK.

Amm0 · Mon Jan 22, 2024 8:21 pm

It "just" needs rewrite to use some cross-platform GUI library like Qt or GTK.

I've never understood this push to re-write winbox... This Mac user is quite happy with @optio approach — which gets an icon — and worked for years.

Guess we're closer to see where this "teaser" goes... No promises.

Cha0s · Mon Jan 22, 2024 9:57 pm

It "just" needs rewrite to use some cross-platform GUI library like Qt or GTK.

Even so, it would not be the same UI anymore.
What I love about WinBox is the no bullshit approach to the UI. No stupid margins (ie wasted space), no useless kindergarten icons and colors everywhere, no stupid material design (or whatever the hell is google and apple push for these days), no touchscreen bs (which ruin the desktop UX).

It's a plain windows 95 era UI that's efficient, fast and to the point. No more no less.

Rewriting it using Qt or GTK, there's no way it will ever look the same again and I am fairly confident that the performance and resources requirements will be worse to achieve the same tasks...

optio · Mon Jan 22, 2024 10:04 pm

I worked with Qt, it can be styled to have similar current look, https://doc.qt.io/qt-6/gallery.html. Regarding performance impact I doubt it will noticeable if developed using native Qt Widgets (unless someone is executing on 486/Pentium I machines), using QML/JS framework is different thing and it should be avoided for distribution on low performance devices. Here is comparison between both Qt frameworks. At the end KDE is built on Qt and running 27 years from now on Linux when devices wasn't that fast.
I did not work with GTK, not sure if styling can be done to look as current native windows app, but regarding performance, similar to Qt, it's native library and it's performing on Linux for 25 years.
But I can bet it's a lot of effort for MT to rewrite Winbox, so we can stick to "No promises" as stated above.

Cha0s · Mon Jan 22, 2024 11:21 pm

I worked with Qt, it can be styled to have similar current look, https://doc.qt.io/qt-6/gallery.html.

Similar, but never the same.
It will be those pesky little details that they won't be able (or not willing to put in the effort) to port the same to Qt and will ruin the everyday use and feel for us that use WinBox professionally everyday. Efficiency and muscle memory matter when using tools to perform critical tasks.

Even during WinBox 2.x to WinBox 3.x there were subtle differences that were very annoying and never got fixed/re-implemented.
Let alone writing the whole WinBox from scratch. Nothing will work ok for the better part of a decade until it's even close to what we have now.

Regarding performance impact I doubt it will noticeable if developed using native Qt Widgets (unless is someone is executing on 486/Pentium I machines), using QML/JS framework is different thing and it should be avoided for distribution on low performance devices. Here is comparison between both Qt frameworks. At the end KDE is built on Qt and running 27 years from now on Linux when devices wasn't that fast.

The fact remains that it will be heavier/slower, regardless of how fast it will look/feel.
KDE did not use the same Qt that did 27 years ago. That's not an apt comparison. Would office 365 run on a Pentium as Office 1997 did?
KDE especially is a bad example. I remember the days when Plasma was released, it was a resource hog and took many many years for hardware to catch up and software to be optimized enough to run smoothly.
KDE 3.5 on the other hand was a joy to use. I miss those days when UIs were just perfect and developers didn't mess everything up on each release just for the sake of it.

But I can bet it's a lot of effort for MT to rewrite Winbox, so we can stick to "No promises" as stated above.

Fingers crossed, they will not do anything and keep it just the (perfect) way it currently is.

optio · Mon Jan 22, 2024 11:26 pm

Well you can always develop on older version library which has better performance. :)

Fingers crossed, they will not do anything and keep it just the (perfect) way it currently is.

For windows users yes, over wine is even bigger performance impact. On my Mac (M1) Winbox startup is approx. 5s (On Intel is some faster because it's not emulated) :) I'm running very heavy apps, none has that much startup time, eg. Eclipse starts much faster. Wine starts multiple processes just to run single app.
Other solution for cross-platform native app can be that Windows GUI codebase remains same but for other platforms is using some cross-platform library for GUI rendering. That can be splitted in build time dependent for which platform build is performing, still a lot of effort to do that, I doubt we will see that.

phascogale · Mon Jan 22, 2024 11:34 pm

It's still called Winbox.
Well, Xbox was taken.

Tikbox

anav · Tue Jan 23, 2024 2:42 am

Rhyme Disease '=)

Tue Jan 23, 2024 7:39 am

Even if we make a winbox that is not the same as the good old Windows 95 inspired version, you can always just keep using the old one

rextended · Tue Jan 23, 2024 10:14 am

you can always just keep using the old one :)

This is fundamental

pe1chl · Tue Jan 23, 2024 10:54 am

Even if we make a winbox that is not the same as the good old Windows 95 inspired version, you can always just keep using the old one :)

Of course until at some point the authentication or some other fundamental protocol detail is changed in some newer RouterOS version, as has happened before...

optio · Tue Jan 23, 2024 11:00 am

Like The Dude, while it works you can use it :)

Cha0s · Tue Jan 23, 2024 2:29 pm

Even if we make a winbox that is not the same as the good old Windows 95 inspired version, you can always just keep using the old one :)
Of course until at some point the authentication or some other fundamental protocol detail is changed in some newer RouterOS version, as has happened before...

Exactly!

hmatmtf · Fri Feb 02, 2024 7:53 am

From the standpoint of the user, Winbox is a login manager, and everything shown after login comes from the device itself.

rushlife · Sun Feb 04, 2024 9:39 am

It would be helpful to rewrite winbox in Java,...

anything, literally everything what came from Java is useless piece of shit

I glad to hear winbox is not using this "language"...

pe1chl · Sun Feb 04, 2024 12:14 pm

+1000

avacha · Sun Feb 04, 2024 6:57 pm

Java? Crossplatform? Really? Well, goodbye good old winbox, this will be a useless piece of bloatware crap .

Oh, I think we just need some tolerance...How about Electorn-based software? Also you need to integrate a lot of telemetry, shitty touchscreen icons, some pictures, a good donate games (i prefer one or two, but who know), Siri and Google Assistant, ChatGPT...

...And subscriptions. "You can configure routing only for 99 Eur/mo.!"

infabo · Mon Feb 05, 2024 6:48 pm

Mikrotik, can you please take care of the following skin bug. MPLS is disabled but still shown.

{
    "Mesh": 0,
    "MPLS": 0,
    "Dot1X": 0,
    "RADIUS": 0,
    "CAPsMAN": 0,
    "Wireless": {
        "W60G Station": 0,
        "Nstreme Dual": 0,
        "Channels": 0,
        "Interworking Profiles": 0
    },
    "PPP": {
        "L2TP Ethernet": 0,
        "PPP Scanner": 0,
        "PPTP Server": 0,
        "SSTP Server": 0,
        "OVPN Server": 0,
        "Import .ovpn": 0,
        "PPPoE Scan": 0,
        "PPPoE Servers": 0,
        "Secrets": 0,
        "Profiles": 0,
        "L2TP Secrets": 0
    },
    "Partition": 0,
    "Make Supout.rif": 0,
    "WinBox": 0,
    "License": 0,
    "Interfaces": {
        "EoIP Tunnel": 0,
        "IP Tunnel": 0,
        "GRE Tunnel": 0,
        "VXLAN": 0,
        "VRRP": 0,
        "VETH": 0,
        "MACsec": 0,
        "Bonding": 0,
        "MACVLAN": 0
    },
    "System": {
        "Auto Upgrade": 0,
        "Disks": 0,
        "Health": 0,
        "License": 0,
        "NTP Client": 0,
        "NTP Server": 0,
        "Packages": 0,
        "Ports": 0,
        "Reset Configuration": 0,
        "Special Login": 0
    },
    "Tools": {
        "BTest Server": 0,
        "Bandwidth Test": 0,
        "Email": 0,
        "RoMON": 0
    }
}

But Winbox menu looks like this:

2024-02-05_17-47.png

ckonsultor · Mon Feb 19, 2024 9:48 pm

Two things:

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

Download button on that page has the same URL linked, so clicking there returns to same page. No way to download Winbox.

How does a user identify which version of Winbox is in use? Can't find that info in Winbox itself or in Wine when executing the .exe file.
Thanks.

ckonsultor · Mon Feb 19, 2024 9:52 pm

Forget the question about the winbox version. I see it in a newly opened Winbox title bar before connecting to a router (when it shows the ROS version). I was on 3.37, downloaded the Oct '23 ver from another site which shows 3.40.

optio · Mon Feb 19, 2024 10:22 pm

Download button on that page has the same URL linked, so clicking there returns to same page. No way to download Winbox.

From WinBox menu on download page: https://mt.lv/winbox64 vs https://mt.lv/winbox - how is this same URL?

How does a user identify which version of Winbox is in use? Can't find that info in Winbox itself or in Wine when executing the .exe file.

wb-ver.png

You cannot see that? Like on screenshot from your post

optio · Mon Feb 19, 2024 10:30 pm

downloaded the Oct '23 ver from another site which shows 3.40.

That's brave (or...?), running router admin software downloaded from non official site

ckonsultor · Thu Feb 22, 2024 4:50 am

Got a fresh download from the official site: Winbox64.

cobusv · Sun Mar 24, 2024 12:01 pm

anyone have an issue with version 3.40 of winbox and routeros 7 when logging in the session just disconnects? this only started when I upgraded to winbox 3.4

Sun Mar 24, 2024 12:33 pm

Which version of routeros ?
There have been versions (beta/rc) where this was an issue so best to make at least sure you're at the latest stable version.

If it would be a generic problem, this place would be swamped with reports which AFAIK is not the case (yet).

kko · Tue Apr 09, 2024 8:46 am

I see native WinBox on Linux in my dream when i sleep )))

robmaltsystems · Tue Apr 09, 2024 11:20 am

I see native WinBox on Linux in my dream when i sleep )))

Which is why IMO effort should be directed at web applications, not native apps. Having written both, I completely appreciate that writing web apps is harder although considering the last one I wrote was 10+ years ago, I would imagine the frameworks have improved massively in that time. A web interface and controller approach would solve many problems and improve sales. Sure, it would introduce some new ones but I'm not in the mood for blockers ;-)

infabo · Tue Apr 09, 2024 11:47 am

There is already a dedicated topic for controller software: viewtopic.php?p=936086

I completely appreciate that writing web apps is harder

It is not. That's why so many (including the big ones like Microsoft) used to develop Electron "desktop software". In classic software development it is "hard" to separate user interface development. In web applications you easily throw the UI part to any army of FE developers, just hand over a backend interface API documentation and you're pretty ready to go.

robmaltsystems · Tue Apr 09, 2024 12:38 pm

As I said, it is 10 years since I did any web app development and I still read CodeProject with envy as to how powerful the modern frameworks look these days. I want Mikrotik to thrive. I love the power of RouterOS but I do lose some customers to Unifi for simplicity of their cloud controller.

I'm already subscribed to that topic and the low down is AFAIK, the controller is dead. IMO management and controller are the same thing.

mkx · Tue Apr 09, 2024 3:46 pm

I see native WinBox on Linux in my dream when i sleep )))
Which is why IMO effort should be directed at web applications, not native apps.

There's already WebFig ... functionality-wise it's on par with WinBox, so no need to re-invent the wheel.

But there's a very important difference, which can not be fixed by web app at all: WinBox can connect via MAC. And many users use WinBox because this function was a deciding point (when using it for one reason, one can use it always).
And this difference alone is the key selling point of WinBox (and also key differentiator from other vendors' management tools, not many support in-band connectivity which doesn't depend on at least half decently configured IP stack on network gadget).

robmaltsystems · Tue Apr 09, 2024 3:56 pm

>There's already WebFig ... functionality-wise it's on par with WinBox, so no need to re-invent the wheel.

There is yes but you can't access it remotely unless you set-up port forwarding or VPN. Complexity again... also, it's a per device interface, not a controller for the entire network. I'm not trying to diss it (too much) but defending the existing isn't too helpful when you're trying to think outside the existing box.

>WinBox can connect via MAC.

I agree that this is occasionally a very useful feature but could a much simpler native application act as an interface between a web app and the device? The only reason why an application running in a browser can't do the same as WinBox is because the same API isn't available. This was a generic problem with all web apps which is why Progressive Web Apps came into existence.

Tue Apr 09, 2024 4:04 pm

>There's already WebFig ... functionality-wise it's on par with WinBox, so no need to re-invent the wheel.

There is yes but you can't access it remotely unless you set-up port forwarding or VPN. Complexity again.

Same with Winbox.
And please don't respond you can open a port directly on your router for Winbox access. That's, how shall I say ... not smart.

mkx · Tue Apr 09, 2024 4:22 pm

I'm not trying to diss it (too much) but defending the existing isn't too helpful when you're trying to think outside the existing box.

It would really help if you stated what are your wishes/requirements from the new web app. Because there are many things that can already be done, but using a few different tools. There's WebFig if you want to configure one device using Web browser (most home users need this). There's WinBox if you want to configure one device but have connectivity issues/requirements. There's RoMoN if you want to configure a fleet of ROS devices which can access each other (but aren't necessary accessible directly from management station). There's API which should in principle offer all management possibilities and one can build their own solution. Etc.

And your response to statement by @kko was very vague, but if one keeps it in context with original statement one can assume that you were talking about app which would run in linux ("natively" ... web app is not native anywhere, winbox can decently run in wine environment).

The only reason why an application running in a browser can't do the same as WinBox is because the same API isn't available. This was a generic problem with all web apps which is why Progressive Web Apps came into existence.

Well, normal L6 applications (e.g. web browsers) are not made to play with L2/L3 stuff. And all OSes provide such API (IP stack, ethernet sockets). There are libraries which expose that to application ... e.g. npcap, which is installed with windows wireshark and provide wireshark access to L2 of network interfaces. Turning such library into API ... IMO that's insanity (a huge can of worms in shape of security issues etc.). And I don't see browsers incorporate such library either. So you can simply forget the idea of seeing web app connect via MAC to your ROS device.

robmaltsystems · Tue Apr 09, 2024 4:29 pm

>So you can simply forget the idea of seeing web app connect via MAC to your ROS device.

Much the same was said about accessing cameras from web applications... never say never.

robmaltsystems · Tue Apr 09, 2024 4:32 pm

>It would really help if you stated what are your wishes/requirements from the new web app.

Unifi controller for RouterOS basically.

pe1chl · Tue Apr 09, 2024 7:32 pm

Which is why IMO effort should be directed at web applications, not native apps.

There's already WebFig ... functionality-wise it's on par with WinBox, so no need to re-invent the wheel.

No it is NOT! Work is required to bring it on par. There should be multiple windows, tabs in the windows, saved settings, etc.

But there's a very important difference, which can not be fixed by web app at all: WinBox can connect via MAC. And many users use WinBox because this function was a deciding point (when using it for one reason, one can use it always).

There should be a simple small portable MikroTik app (program) that you can run to:
- netinstall devices
- put config in new devices
- and: listen on a TCP port and translate actions to the MAC protocol.

Then you can connect via MAC also from a browser.
Preferably it would be open source so it can be installed on any device/OS the user may have.

robmaltsystems · Wed Apr 10, 2024 2:04 am

Happened to be catching up on YouTube and came across this video by a staunch Mikrotik supporter with 222 videos mainly about Mikrotik - so you can hardly call him a hater but he felt compelled to release this video entitled "Things I don't like about MikroTik..."

https://www.youtube.com/watch?v=Z2HeQ7znKBs

He covers the subject touched on above at the very end about lack of overall management.

pe1chl · Wed Apr 10, 2024 11:24 am

Central (overall) management is the topic of another thread.
You know, one of those "we are considering, we want your input" and then you never hear from the product again.

infabo · Wed Apr 10, 2024 11:32 am

Of course. As soon they realize (after reading community input) it's gonna be a ton of work and a lot of expectations to meet. "Nah, better not".

robmaltsystems · Wed Apr 10, 2024 12:29 pm

I sometimes wonder, considering the philosophy of Mikrotik esp. around licensing, whether an open source approach to developing web based management tools would work? I'm semi-retiring now and I'm interested in a project although that might be something completely different like a model railway. Mikrotik control the hardware (obviously) and maybe the API on the board and an enthused team develop the rest. Just an idea. If you ever met me, you'd know I'm always looking for solutions to problems and don't like blockers.

PS. Total aside but many model railways are networked so *not* that radical a change.

pe1chl · Wed Apr 10, 2024 12:44 pm

Yes, you could certainly write a web management tool that performs all its actions via API. That basically is what winbox is doing as well. The winbox protocol and API probably have a lot in common. I think what winbox has extra is the capability to query the available commands and the corresponding dialog layout, and the icons. These are then stored in the version-dependent directory in the winbox application directory.
Unfortunately it seems that the winbox protocol itself (unlike the API) is not documented...

robmaltsystems · Wed Apr 10, 2024 2:11 pm

>That basically is what winbox is doing as well.

Does WinBox effectively issue CLI commands to get/set changes?

infabo · Wed Apr 10, 2024 2:13 pm

Who knows?

Jotne · Wed Apr 10, 2024 2:21 pm

Does WinBox effectively issue CLI commands to get/set changes?

I would think so. If you look at command history, it looks the same if its run from Winbox or from terminal.

pe1chl · Wed Apr 10, 2024 5:21 pm

Does WinBox effectively issue CLI commands to get/set changes?
I would think so. If you look at command history, it looks the same if its run from Winbox or from terminal.

No, it is more like API calls.

robmaltsystems · Wed Apr 10, 2024 7:14 pm

I would have expected some kind of API as that's more efficient (no need to parse command line) and less prone to breaking changes.

Amm0 · Wed Apr 10, 2024 7:37 pm

I would have expected some kind of API as that's more efficient (no need to parse command line) and less prone to breaking changes.

All the config methods are abstractions over some internal config schema (see /console/inspect). So...I'm just not sure where efficiency comes in — once config change is made it's stored internally in the same manner, regardless of the config method.

So is winbox less efficient? I guess it's easier to have dozens of windows open (that are listen for changes), but like similar in impact as CLI+tmux+ssh with dozens of "print follow" running in background. But compared with continuous CPU needs of WG/IPSec/BGP/etc., configuration changes/monitoring is not very significant.

In terms of "breaking changes", that's the job of crossfig to migrate any config on upgrade to newer attributes. If that doesn't work right, it's a bug. But again how those changes got made, does not affect how they might break later.

Also think this has gone a bit off-topic....

llamajaja · Wed Apr 10, 2024 8:55 pm

Just saying,sweet to be able to have multiple winbox windows open, viewing rules being tripped, logs filling, sniffing ongoing, connections tracking shown etc.........

pe1chl · Thu Apr 11, 2024 11:02 am

I would have expected some kind of API as that's more efficient (no need to parse command line) and less prone to breaking changes.
All the config methods are abstractions over some internal config schema (see /console/inspect). So...I'm just not sure where efficiency comes in — once config change is made it's stored internally in the same manner, regardless of the config method.

Well, as people have noticed, when you use winbox to view some configuration in a panel, you change one or two items and hit OK, it will set ALL the configuration in that panel. Probably the same in webfig.
When using commandline, you would only set the items that you are really changing.

But, that is just a "winbox bug", that could be fixed with some additional code in winbox. After all, it knows which items you have changed.

infabo · Thu Apr 11, 2024 12:31 pm

But, that is just a "winbox bug", that could be fixed with some additional code in winbox. After all, it knows which items you have changed.

As someone who has noticed this behavior and already complained elsewhere: of course it is a bug IMHO. Mikrotik may see it differently.

Amm0 · Thu Apr 11, 2024 3:44 pm

But, that is just a "winbox bug", that could be fixed with some additional code in winbox. After all, it knows which items you have changed.
As someone who has noticed this behavior and already complained elsewhere: of course it is a bug IMHO. Mikrotik may see it differently.

I think winbox has always done this. It just only recent the attributes were logged, so it more visable.

But don't forget that winbox does update attributes if changed elsewhere. So if a dialog box is open, and CLI changes something in it, winbox will reflect the new value within seconds. So chance of saving stale data is minimal.

Now should it log all them? Probably not.

llamajaja · Thu Apr 11, 2024 4:09 pm

Winbox, IMHO is the secret sauce, allowing non CLI trained folks to access and modify their configs and view all kinds of information. I had no RoS or CLI or networking training but do use Terminal from time to time as required and basic scripting as well. So CLI is just a fingertip away in winbox. Its a really decent gui and would leave MT if they took it away and would go back to zyxel or something similar. The ease of which I can view multiple devices and winbox over VPN, is really sweet. By the way, to troubleshoot a config, I read the config file, dont use winbox for that.
I do use winbox to view sniffs, connection tracking, actual routes,. traffic status, pinging of sites, etc.. ( and to see if any config issues are pointed out ( via colour or symbol indications, warnings ).

Amm0 · Thu Apr 11, 2024 4:57 pm

Winbox, IMHO is the secret sauce, allowing non CLI trained folks to access and modify their configs and view all kinds of information.

Agreed. If you BOTH CLI and winbox, or have potentially multiple users making updates, it is really well integrated. e.g. the "live update" of winbox dialogs is actually quite powerful and does avoid stale writes. I use both CLI and winbox, since it often easier to view things in winbox, but make changes in CLI.

It really is just the recent logging of attribute changes that's caused confusion. And tend to agree that it should only update dirty fields and logs only those changes.

Now whether the log is message is even correct about the actual operation, IDK — it may just dump all the attribute in the dialog and the "set *XX" is just a log readability thing, not the actual command & internally only update changed ones. But even if updates all, they should all still be current when saved because of winbox's "live update".

si458 · Tue Apr 16, 2024 1:40 am

@normis any update on a native mac app for winbox?
just seen your new youtube video and saw a NEW winbox icon,
then found this post and realised its been around for 3 months now, surely the has been progress?
ive been using https://github.com/nrlquaker/winbox-mac but the is bugs with the 'Open in a new window' option
and its the same using wine64 native too
NOTE im using Intel mac not ARM (we arent all rich)

Amm0 · Tue Apr 16, 2024 2:35 am

@normis any update on a native mac app for winbox?

Given we're at an icon flashing in task bar: https://youtu.be/sQPlwDSd5LM?t=184 — be a while.

No other proof of life... Like screenshot? Or, at least clue on framework/lang... Can we put rest it's Electron?

tigro11 · Tue Apr 16, 2024 8:22 am

good morning, I noticed that on winbox in the interface section, right click and select detail mode, winbox closes

pe1chl · Tue Apr 16, 2024 11:23 am

It does not always happen, maybe only when you have a certain number (or type) of interfaces.

Who is online