📣 WinBox 4 is here 📣

[guywifi]

Where does linux version stores ‘saved routers’? Is there a way to import Winbox Loader Addresses?

Did you get an answer to this?

[Hejsan]

I can’t find it or maybe this feature hasn’t been implemented yet.
In version 3 there was an option to save all connections under a master password. Is this in the new version?

I have exported all connections from WinBox v3.41 (I had a master password there) and imported this file in v4.0… it worked perfectly. I am asked for this master password every time I open WinBox 4.0

[teslasystems]

Just noticed that I can drag files from folder to WinBox, but can’t drag them from WinBox to folder. Also, if a file has zero size, it shows an error. OS Windows.

[belthesar]

@atomicduck

1. what kind of VM are you using, please post some more details, so we can try to replicate the issue
2. a lot of what you mentioned is going to be improved or fixed in the next release, so please give it another chance then

Hello Normis.

I had an issue with starting and running WinBox for Mac on Wine, as well as with an older WB beta. I needed to start working ASAP on a new network. The situation was the same on my Win 11 work machine, so I used an older Win 10 LTSC VM and successfully got the job done. I reported this under SUP-173297, but since it was urgent, I didn’t spend time debugging and just did everything in the VM.

Later (after I finished the work), I installed updates on Sonoma, used Onyx, and installed the latest WB 4 beta. It then started working, but I don’t know what the actual issue was. On my Win 11 machine, I didn’t bother investigating and continued using Win 10 LTSC. Currently, I’m testing and optimizing FT.

For speed testing of the WB beta, you can use any slowish Windows virtual machine. I’m using VMware 17.6.0 on Windows and Fusion 13.6.1 on Mac, and they perform about the same.

If you install a Windows 10 or 11 VM with limited resources (e.g., 2 cores, 4 GB RAM), you’ll easily notice rendering slowness when resizing or moving windows. The more you limit the VM, the more rendering issues (slowness, glitches) you’ll notice. The rendering engine simply isn’t optimal currently. All this testing is being done on a Lenovo T470s with 16 GB RAM that I work with (because it is built like a tank, still sleek with two batteries, and has a full size RJ45 port).

As for the other issues, I really hope it is so. I wrote my comments in good faith, but mind both I and some of my colleagues share the same sentiments, tho they are more silent then I am.

To end in a good spirit: I am impressed how well you optimised the AC and AC XL with Wave 2 drivers and new Capsman on 17.6. On my testing I got roughtly 650mbps DL on with single client, compared with 750 on my XV2-2X that runs AX chipset. - Same room, same distance. Not sure yet how they will behave in industrial/warehouse setting, but I am highly optimistic. The main reason I prefer MT / WB approach to other is that I am able to monitor and optimise entire site easily. That is why I am so concerned with the loss of information density and usability in new WB.

It sounds like your Lenovo is set up as a Hackintosh. Are you aware that there’s a native macOS build for Winbox 4? It might be worthwhile for you to eschew trying the VM route when you can run the native version, without any of the headaches of virtualization. That said, if the VMs are largely there for work vs. personal isolation, I’d make sure that you’ve configured your VM with any GPU acceleration you can. Qt, like other modern GUI frameworks, takes advantage of a GPU to accelerate its rendering, and falling back to software rendering is going to hurt no matter what OS you’re using.

WRT the new need for GPU acceleration, it seems like the target era for acceleration is DirectX 11 support (based on other screenshots in the forum). That came out in 2009, which means that any machine, even with an onboard GPU, has had support for the feature set needed for over a decade. It is indeed a new requirement above and beyond the legacy Winbox codebase, but it’s really not a tall ask. Folks have every right to be grumpy about the new requirements, but it’s unfair to be mad that there’s a much more supportable code base than its predecessors and also be mad that the new codebase comes with new requirements. There’s plenty that still needs love in Winbox 4, but in my opinion, the new app is a huge step in the right direction in multiple dimensions, and while my needs aren’t the same as everyone’s, it’s been more than sufficient for me to maintain my networks.

I kinda robbed this reply to send my thanks to normis and anyone else working on the new Winbox, because I know there’s an awful lot of negative feedback here. Not my place to comment on their feedback, but I know hearing a lot of negative responses can really take the wind out of your sails, so I hope that hearing that there are folks that are thankful for your work helps you continue.

[ksteink]

I just installed the Beta 14 and looks good. Few things that I like to see in future versions:

• A way export current DB of devices registered. I found import but I couldn’t import the .WBX from version 3.41 so I had to input manually my devices. For large deployments it’s not practical

• A quick search to find by Workspace, Group, Comment or IP Address / Hostname. For multiple devices can be cumbersome to find the device.

• The Font of all the text is too small!!! Common my eyes are not as use to be (At least give the chance to adjust it at the taste of the user!)

I will find more stuff for sure but this is my first impressions by trying out the new version!

[SuperMarioSF]

There is a way to crash WinBox 4.0beta14.

In a x86 based system (normal x86, or a x86 CHR), open System/Console, double click the item that should be the local screen console, and it will just crash.

For reference, in Winbox 3, double click that item do nothing at all.

[SuperMarioSF]

Another bug for beta14.
For some reason the timezone droplist in System/Clock duplicated each item one more time, except for “manual” option which only present once.

This bug seems only present when connected to a RouterOS 7.x device.
When connected to a RouterOS 6.x device there is no duplication problem.

[brevilo]

Awesome news!

Now, I tested 4.0beta1 and 4.0beta3 on macOS (Sonoma on M3, against ROS 7.15.3) and it fails to connect with the following (WinBox 3 via Wine still OK):

ERR: Could not connect, MacConnection syn timeout

(while at it, please allow for copying error messages)

If only you’d taken the opportunity to change that meaningless (if not entirely misleading) name, now that its Windoze shackles are finally off

Thanks and keep it up!

Unfortunately, no change with 4.0beta14 (now against ROS 7.16.2)…

[JunoBox]

Version 4 is looking nice and awesome, a small missing in the Log windows is that I can’t still find the Freeze button to quick stop logs stream, that’s a requirement!
Also when opening the log window. I always have to scroll completely first to the newest additions. With WinBox 3 it always jumped directly to the newest entry when opening the log window, regardless how the sorting is defined (newest or oldest on top).

Another point of improvement. Workspaces. Make it switchable to auto-save on/off. Sometimes I made changes temporarily in for example columns and do not want this to be saved to the workspace. I would like to click a save button by my self when I think it is needed.

[BartoszP]

1. Please implement “select all” aka Ctrl+A to mark all entries
2. Please implement selecting with keyboard => Shift+arrows
3. If you carefully selected some entries and by chance you click anywhere outside checkbox area than all selected items get unselected - what an annoying situation.

[NTheZone]

Please bring back in-line comments, no matter the reason. Do not remove functionality; adding is OK or updating is fine, but removing is just BAD.

Running under MacOS, x86

UPDATE: I see that the option is not under the column selections, but under the hamburger menu on the top right. It would however, still be nice to rearrange the column order.

[NTheZone]

Yes, please bring back in-line comments, no matter the reason. Do not remove functionality; adding is OK or updating is fine, but removing is just BAD.

Can we please get something done with this awful waste of space in “non-inline” comments?
We do have inefficient space use everywhere but “non-inline” comments look like worst example of this. This is almost tolerable everywhere else, but these comment lines are the ultimate abomination, which makes this setting unusable while I use it all the time in WinBox 3 - this screenshot should be self-explanatory why it cannot be used in a same way in WinBox 4.

snap 2024-12-09 at 10.34.29.png

[NTheZone]

Also the drop down of side options was nice. Now I have to add another click to get under other options, e.g. IP → Firewall & IP → DHCP Server

Wherever there is an added click, is another means of lost productivity and hassle.

[inazmul]

I just installed the Beta 14 and looks good. But I cant using New Winbox Option, After I click On It then existing winbox will crass, Where I let them the issue

By the way I can’t replay the post the announcements of WinBox 4 Is here any Problem on that ??

[spippan]

…

@inazmul

why are you using my avatar picture?

[inazmul]

Some Time WinBox 4 Take too may times, I feel leggy. I think it’s need more speed

Another problem is drag and drop, I taka my router backup, after that try to drag it my pc can’t. it’s an issue for me

[inazmul]

...

@inazmul

why are you using my avatar picture?

I like you avatar, by the way I just change it.

[nmt1900]

Users without “sensitive” and/or “password” permission can reveal CAPsMAN passphrases and PPP secrets in Winbox 4 beta14 (and probably earlier).

In Winbox 3 “Hide Passsword” field can not be disabled if user does not have “sensitive” permission, but in Winbox 4 this setting is “outside” of user session and can be changed by any user that can login into device.

Be aware of that if you are admitting access to your devices for restricted users as you cannot deny access for Winbox 4 specifically! As of now I see this problem appearing with CAPsMAN wireless configuration passphrases and PPP secrets

[xsherlock]

Is there some limit on the router OS version that is compatible with the new winbox?
I have RB751G-@HnD running 6.42.12 and and new Winbox will not connect to it ?
By mac or IP it is stuck in Authentication.

Maciej

[normis]

The same is true for newer WinBox3. We improved security, so you need to upgrade RouterOS in any case.