when saving a new entry, using save button, did you add a comment?Screenshot 2024-09-03 at 10.36.49.jpg
@normis: where/how to open that view ?!? i have no comment column to select/show ?
Well, there is no best way to do it - pick one and roll the dice. I vote for flatpak for is multi distro availability and somewhat sandbox, or appimage, at least packages dependencies whit it. You can also still distribute like you do now, if distro used is new it should work fine. I assume you use at least qt5.AppImage and Snap are also mentoned here, but described as bad.
What is the "best way" to distribute linux apps, in your opinion?
Thanks for the explanation and clarification. Not really the norm but at least I understand now. I would have just expected what you are referring to as window grouping or layout to save as default for each connection used.No workspaces is definitely not that. Workspace saves arranged menus. Maybe you want a Wireless workspace, with Wireless Registration table open, the Log window, the Wireless scan window. Call it Wireless Debugging and save as a workspace. Then maybe you need a Terminal workspace with 4 terminals.
As explained in the first post, it is not added yetReally loves the GNU/Linux native version!!!!
I have two things to ask for: ¿Where is the "SAFE MODE" button placed now? I can't find it (my vision is not like in my 20's hehehehe!!!) the other one is that at Debian 12 I can't download files from router to my computer, if I switch to an "oldie" Winbox 3.xx it works!
Good job guys!!!!
The application is the "box". You open/manage sub-windows inside the application workspace. That's why it is a box of windows. WinBox. See now?can't understand why it's still called 'WinBox' on macOS or Linux?
@normis please let me know how fast you can locate the vertical scrollbar positon in the log window.Example about dark mode scrollbar ?
yes, dark mode warnings will be added to list
Because it was a native Windows application until 3.x. Now it is cross-platform and people ask questions. My house has windows too, and it is not built by Microsoft. I don't even get questions regarding how long my house gets Windows updates and/or which version of windows it runs. Because my house has many windows.People are so gotten used to grey XP style interface, but are not used to the name? We call it winbox, because is easy to say and everyone knows what it is
It was only native in Windows 95, all newer Windows used a completey different style of window and theme, and Winbox did not follow that.Because it was a native Windows application until 3.x. Now it is cross-platform and people ask questions. My house has windows too, and it is not built by Microsoft. I don't even get questions regarding how long my house gets Windows updates and/or which version of windows it runs. Because my house has many windows.People are so gotten used to grey XP style interface, but are not used to the name? We call it winbox, because is easy to say and everyone knows what it is
click on the comment column title. This button decides how to show them (see image)What I see and an example application that uses actual Workspaces ...at least comments is displaying even though not showing a selectable option.
ran only on windows is not really definition of "native", but I guess it depends on definitionNative in terms of: compiled to run on Windows OS only. Is that right?
Not exactly true. WinBox 3 uses ClearType, if enabled in system. And doesn't use it when not enabled. WinBox 4 has forced ClearType, regardless of system settings.Winbox3 didn't use any kind of font smoothing and ignored operating system settings.
This is quite a hard one to answer.AppImage and Snap are also mentoned here, but described as bad.
What is the "best way" to distribute linux apps, in your opinion?
And Winbox 4 is following Windows theme?It was only native in Windows 95, all newer Windows used a completey different style of window and theme, and Winbox did not follow that.
;)- Apps are native!
why is this even a ef'ing thing? i do not get itPeople are so gotten used to grey XP style interface, but are not used to the name? We call it winbox, because is easy to say and everyone knows what it is
For me it would be that I can use the installer in Ubuntu, likeAppImage and Snap are also mentoned here, but described as bad.
What is the "best way" to distribute linux apps, in your opinion?
You wrote quite an elaborate comment, but you are coming with the incorrect premise: that it is possible to create statically linked binary on linux.If You are willing to send the libraries and/or the static compiled binary, and are willing to make these many versions, why not make one deb and another rpm, static linked (or with the needed libraries included)? Those would be two packages. Ok, three: one tgz for corner cases.
Because people see the absurd number of Distros, and think we have to make one full version for everyone of them. This is not true. One way to distribute packages (deb and rpm) would be:
1) Compile static, or send the dependencies with it. The packages allow this, and it would run basically everywhere.
Not really. On linux system the prevailing culture is not to do this; it is to package it (one way of another, deb/rpm//flatpak/etc), so unprivileged users can get updates (and do not run them out of their homedir).But, really, for something like this - and the public it caters for - I thing tgz would be the best way, with auto updates on startup. Exactly like You are doing.
Passwords remembered on my machine. Linux client. Maybe you hit an UX trap. You probably need to enter your password and hit "save"-button before you hit "connect"-button.Does anybody else have a problem with winbox not remembering password ? I check remember password but everytime i start winbox password is not saved.
Maybe you expect something to happen, that was never intended to happen? This is what is SUPPOSED to happen. As designed: https://imgur.com/a/RwZRKRH
Well, whatever You can use an standard interface to doesn't have to. Because, You see, Flatpak and whatnot get the same problem.With glibc, this is not possible without breaking its functionality. Quite a chunk of glibc is dynamically loaded (including subsystems like nss);i if you ignore it, you might break things like hostname resolution or user database. This is the reason, why even golang (which otherwise doesn't need glibc) doesn't do statically linked binaries.
So by trying to go with static binary, you are opening a can of worms with bigger problems.
Were You talking about Flatpak, that put them on "~/.local/share/flatpak" for user installations? System wide instalations would be no better than a package - since would need root password for install and update.Not really. On linux system the prevailing culture is not to do this; it is to package it (one way of another, deb/rpm//flatpak/etc), so unprivileged users can get updates (and do not run them out of their homedir).
The detached window feature would make sense if there is only one Winbox instance running at a time. Since mostly several Winbox instances are running, detaching windows would create even more usability issues.
What kind of issues? Like closing main window/instance which kills detached windows as well? Could be solved by modal confirmation dialogs (known from e.g. Microsoft Word): "Hey user, really like to close? There are these other detached windows still open. <list of open windows>". Like a web browser application supports tabs and new-windows (=detached) since like decades. Never read "omg, these detached browsers windows make me going crazyyyy"The detached window feature would make sense if there is only one Winbox instance running at a time. Since mostly several Winbox instances are running, detaching windows would create even more usability issues.
It definitely is not too big. However, 16mb of storage on 2024 routerboards is definitely too small.50MB is too big in 2024?
Interesting... It looks like Winbox 4 works better on old Macbook than on any Windows machine(?)- overall sluggishness - webfig works approximately the same if not faster.
Many users request return of the Tabs to the top bar. One of my colleagues has nice idea - most of the time, you only work with few selected tabs. So what about an icon in the drop-down list, to open a Tab in a new Window, would in fact pin the Tab to the top bar instead?
wishing for such a feature for years !This looks lovely, and I'll check it out. Windows, MacOS, and Linux.
However, one killer bit I'd love to see added to Winbox: public key auth. We have an ongoing war internally about killing off winbox because it means our techs are storing passwords in their laptops. Personally, I use SSH at least 80% of the time, and just don't store creds in winbox. Making Winbox capable of using public key auth like SSH would eliminate the issue. Joe would just have his private key imported to winbox and we'd be done.
You can reliably link musl statically though. musl is also MIT licensed. Assuming the app works well with musl, statically linking against musl is a really nice idea for portability.First, thanks for the Linux and MacOS versions! Very appreciated!
And now, how to improve. Some items are repeating what was already written, but I consider it important enough to justify repeating ;)
Linux:
- (Not going into discussion why flatpak and not deb/rpm/appimage right now. Also not static binaries -- there's no such thing as static binary with glibc, at least not if you want it non-broken. It will certainly not fix brokeness on musl systems, just add a new brokeness on glibc ones).
This only affects Windows users running 60Hz and is a known bug in the "Qt" framework, a fix is in the works. macOS and linux should be fast for most people.overall sluggishness
it is exactly as was in v3
The same on Windows.one small thing on MacOS, Enter key is no more acts as "OK" button, now I need to click mouse instead of just pressing Enter like in v3.
@normis: that was the hint ;-)If anyone else is not seeing Comments column in the Saved routers interface, make sure this Comment setting is on Globally
Screenshot 2024-09-03 at 14.34.09.jpg
Sorry for TLDR, but those things are answered in the first post actually. Shortcuts are all removed, and will return. Window can be closed by ctrl+w like in web browsers, but that's the only shortcut for now.I'm sorry, this thread is so TL;DR :/..
I know it was a lot of work, but..
First rant (apart form things to be addressed in the original post):
- too much graphics, I could live with Winbox3 with darkmode forever; content is getting lost for the cause of fancyness
- windows cannot be closed by 'Esc', comments can't be edited with Ctrl + M, no 'New item' with Insert.. That's really pain in the ass, I suppose more people like to work preferably on keyboard
- I came accross issue, that windows can't be positioned in negative X position. So when you open window in fullscreen, it's big, you make 'Winbox window' smaller, X - close isn't visible and internal window can't be moved to get to it, you have to resize Winbox to a bigger window so you can see it and close internal window (as Esc isn't working)
Well, we have public key authentication with SSH already. This brings me to feature I proposed earlier: Winbox connection via SSH tunnel.However, one killer bit I'd love to see added to Winbox: public key auth. We have an ongoing war internally about killing off winbox because it means our techs are storing passwords in their laptops. Personally, I use SSH at least 80% of the time, and just don't store creds in winbox. Making Winbox capable of using public key auth like SSH would eliminate the issue. Joe would just have his private key imported to winbox and we'd be done.
<pasted from mac terminal>
[XXXX] /system/logging/action> /system logging
[XXXX] /system/logging> set 0 action=remote prefix=:Info
[XXXX] /system/logging> set 1 action=remote prefix=:Error
[XXXX] /system/logging> set 2 action=remote prefix=:Warning
[XXXX] /system/logging> set 3 action=remote prefix=:Critical
[XXXX] /system/logging>
[XXXX] /system/logging> add action=remote disabled=no prefix=:Firewall topics=firewall
[XXXX] /system/logging> add action=remote disabled=no prefix=:Account topics=account
[XXXX] /system/logging> add action=remote disabled=no prefix=:Caps topics=caps
[XXXX] /system/logging> add action=remote disabled=no prefix=:Wireless topics=wireless
<typed manually>
[XXXX] /system/logging> export
# 2024-09-04 08:56:12 by RouterOS 7.16rc4
# software id = PDMF-PR2F
#
# model = cAPGi-5HaxD2HaxD
# serial number = xxx
<snip>
/system logging
set 0 action=remote prefix=:Info
set 1 action=remote prefix=:Error
set 2 action=remote prefix=:Warning
set 3 action=remote prefix=:Critical
add action=elastic topics=critical
add action=elastic topics=error
add action=elastic topics=info
add action=elastic topics=warning
add action=remote prefix=:Firewall topics=firewall
add action=remote prefix=:Account topics=account
add action=remote prefix=:Caps topics=caps
Known issue, as mentioned in the first post.Clipboard01.png
Do you plan to fix the encoding?
@normisWorkspaces save the list and locations of open windows, that you will see when connecting to a router
<own> - the same windows are open, that you saw last time, when connected to this same IP
Sorry - I searched for "encoding" before posting and missed the statement in the first post.Known issue, as mentioned in the first post.Clipboard01.png
Do you plan to fix the encoding?
Currently, new entries show correctly. Only old comments do not show correctly.
works for me. maybe write permissions for the session file folder?I think there is a bug regarding <own> workspace. Windows layout is not being saved.
Checked that and it's got full permissions to write and read (full control), also custom workspace is working only <own> have problem. Tested on win 10 and win 11.works for me. maybe write permissions for the session file folder?I think there is a bug regarding <own> workspace. Windows layout is not being saved.
:facepalm:I'm not sure that any of you know what beta means when developing a GUI application. Please, report bugs that you find while using the app and/or if something doesnt make sense or if you find something to have more sense to be in a certain way.
Its a beta for a reason, any missing features need to be ported to the new GUI before you can use them. Stop reporting missing features...
Also, dont complain about file size. Its no big deal and it needs to be this way if you wanna have the fancy Qt things in it :)
Only report how the current build of new GUI works, crashes, etc etc
Winbox v4 is not feature complete. In fact it is missing basic functionality, so by definition it is not beta, and by that measure it's only logical that everyone is whining about key missing features.Beta, named after the second letter of the Greek alphabet, is the software development phase following alpha. A beta phase generally begins when the software is feature-complete but likely to contain several known or unknown bugs.
Yes, please. It could certainly help with making everyone happy. MikroTik can make defaults pretty according to their preferences, and anyone feeling that it could be prettier or anything (different contrast, etc.) could adjust it for themselves.I would add to my previous suggestion to let the user choose the colors, so it could adapt to our work environment : )
Something like: "custom theme" or "custom color palette" in addition to light and dark mode :)
Same in WindowsMac version - unable to drag multiple items at once. Selected multiple items, drag, but only one was moved.
There is auto reconnect with a countdown and it works.No auto reconnect or open in new window options.
In v4 whenever the device needs to reboot, changing frequency in an AP for example, v4 closes and requires a manual restart. This is wastes time that most field techs don't have. Please re-instate.
Like this (button next to workspace name. icon will be changed, current one is a bug)I have one question - how to delete the workspace in Winbox 4? New ones can be created and saved but there does not seem to be a way to delete them...
As multiple posts say above, currently all shortcut keys are disabled. A known thing. They will returnWonder if the possibility to select all (using ctrl+all) or even a button in the new inbox will be added in the future or even select some elements in the same tab using shift. that was very useful in the old winbox to disable / enable a bunch of firewall rules at once for testing.
Chaos, read your own quote more carefully.A beta phase generally begins when the software is feature-complete but likely to contain several known or unknown bugs.
OK, you are the boss, new software, new experience, got it. But then, strange decision to name it almost as another your software, changing only the number on the end. Or this is temporary name and perhaps there will be TikBox at the end?Winbox4 is a new software, which has not replaced Winbox3.
What's new in v4.0beta4:
*) added undo / redo / safe mode
*) added command line launch parameters ( WinBox <connect-to> <addresess> <password>)
*) fix auth via RADIUS on macOS
*) fix opening http url on Windows (for SwOS)
*) improved several icons
This works for nearly everyone else, so something must be wrong in those computers, where it fails. Make a support ticket please, so we can investigateUpdate to beta4 on Intel Mac did not finish the same way as with last update (had to manually copy app from /Volumes/WinBox to /Applications).
@normis, you didn't say whether this should work out of the box, or if there was some setting to enable it and if there is, where to find it. Please advise.There is auto reconnect with a countdown and it works.No auto reconnect or open in new window options.
In v4 whenever the device needs to reboot, changing frequency in an AP for example, v4 closes and requires a manual restart. This is wastes time that most field techs don't have. Please re-instate.
Yes, like I said, if I make a change that requires the device to reboot (like, oddly enough, changing an AP frequency), once you hit apply WiFi the connection is lost (on reboot) and Winbox simply closes. Doesn't freeze, closes completely. Once the connection is restored, you need to restart Winbox.This works out of the box on all operating systems. Closes the connection how, what do you see then? Winbox disappears? Mayebe it is crashing and closing
*) added undo / redo / safe mode;
*) added command line launch parameters ( WinBox <connect-to> <addresess> <password>);
*) fix auth via RADIUS on macOS;
*) fix opening http url on Windows (for SwOS);
*) improved several icons;
Changing the frequency does not require a reboot. Actually I can't think of any setting, that requires the reboot of a router, except upgrade. So several things are happening incorectly in your case, Make a support ticket pleaase, with more details.Yes, like I said, if I make a change that requires the device to reboot (like, oddly enough, changing an AP frequency), once you hit apply WiFi the connection is lost (on reboot) and Winbox simply closes. Doesn't freeze, closes completely. Once the connection is restored, you need to restart Winbox.This works out of the box on all operating systems. Closes the connection how, what do you see then? Winbox disappears? Mayebe it is crashing and closing
Even though it's convenient to provide a password as a CLI argument, it's not a good idea to do that. Many CLI tools warn you when you still provide passwords via arguments. On Linux, all arguments can be seen in process viewers like ps or htop as long the process is alive. Any other software on the system can look at the process table and read/steal the password. It's safer to start a saved session using a stored password, so the credentials stay private.*) added command line launch parameters ( WinBox <connect-to> <addresess> <password>)
I did that. It is only on Mac where this fails - in-place update works seamlessly on Windows and Ubuntu for me.This works for nearly everyone else, so something must be wrong in those computers, where it fails. Make a support ticket please, so we can investigateUpdate to beta4 on Intel Mac did not finish the same way as with last update (had to manually copy app from /Volumes/WinBox to /Applications).
I agree with this sentiment, except flatpak seems like a much better fit for a desktop application that is regularly being updated.Everyone else is throwing in their wants/desires for the Linux distribution, so here's mine:
You are never going to make everyone happy in how you distribute a linux binary. Creating and maintaining packaging/repositories at this stage is a waste. The way you are distributing it now is fine. I agree with other sentiments here, keep distributing it the way you have and let the users create packages for their desired deployments if they are so inclined. The only thing I would change is distribute it in a tar.gz file instead of zip. Tar files are just more common on linux systems and sometimes environments don't have unzip installed. That is minor all things considered and it won't change my use of this amazing application at all if it never changed.
If you get past beta stage and want a simple single-file download-and-run application, I would focus on appimage. Almost all distributions support the format by default. Please do not remove the ability to download an archive with the stand alone application. As stated before, and goes doubly in the case of people running non-standard distributions like NixOS, appimage or any other distribution method is a waste of time currently and would only hinder our install options when/if put in place later on.
I'm trying out beta4 now and will keep commenting if I see anything breaking, but thank you once again Mikrotik team for all the work you have put into this application and for putting up with all of the feature request complaining from your users.
+1Hi There,
Other issue I found is that tools like ping/traceroute don't allow entering a FQDN like www.google.com. They always expect an IP address. This works in Winbox 3 and it is really useful for me!
Thank you!
already requested and added to TODOThanks a lot for this updated version of Winbox.
A made a quick search on the topic, and I don't think this was reported: it would be nice to have an automatic switch between dark and light themes, following the operating system setting. I use light theme during daylight, and my PC switches to dark mode automatically at sunset. I understand you have a lot to do, and this won't be a priority, but it would nice 😀
BTW, I second most of the other reports regarding contrast and readability.
already requested and added to TODOI love the new app on macOS! But one thing that is really bugging me.... I can non longer hit the ESC key to close windows within the app. Someone times I have a stack open and now have to use mouse to click to close.
I'm sure it was an enormous effort to get it this good for a beta. It did come out great for an early beta!Just don't be too harsh on us yet, first, let's celebrate that it's finally the day!
I actually like the dropdown for the top-level, or at least willing to give it a fair chance.... It uses less screen real estate than tabs. And the new "pop-out" window is great, especially when combined with new "workspace"/session. I think folks need to give it a chance...
- Most people prefer Tabs over Dropdowns
Update from beta3 to beta4 went smooth, Sonoma 14.5 (23F79) x86_64Jeez, just launched beta3 on my Macbook. "Update available" it greeted me. It downloaded beta4 and Winbox closed itself after reaching 100%. But it did not re-launch again. And also my Winbox Icon on Desktop (thats where I dragged it from DMG installer) is gone now. Good job, Mikrotik. Your builtin update turns out to be an un-installer instead. ROFL
must be fun hanging out around you.:facepalm:I'm not sure that any of you know what beta means when developing a GUI application. Please, report bugs that you find while using the app and/or if something doesnt make sense or if you find something to have more sense to be in a certain way.
Its a beta for a reason, any missing features need to be ported to the new GUI before you can use them. Stop reporting missing features...
Also, dont complain about file size. Its no big deal and it needs to be this way if you wanna have the fancy Qt things in it :)
Only report how the current build of new GUI works, crashes, etc etc
Winbox v4 is not feature complete. In fact it is missing basic functionality, so by definition it is not beta, and by that measure it's only logical that everyone is whining about key missing features.Beta, named after the second letter of the Greek alphabet, is the software development phase following alpha. A beta phase generally begins when the software is feature-complete but likely to contain several known or unknown bugs.
Maybe, just maybe they should have brought v4 to feature parity with v3 before releasing a beta version to the public?
on a mac, this works for me:am i missing something, where is?
*) added command line launch parameters ( WinBox <connect-to> <addresess> <password>);
Do you mean that you manually upload the files and manually issue the reboot?i just upgraded to WinBox4.0beta4 for Linux. I believe i found a bug. I noticed that i cannot upgrade the RouterOS of my mikrotiks. i have tried uploading several times (all of which were successful uploads). but after the reboot, the RouterOS version was not upgraded. I defaulted to WinBox 3.41 and was able to upgrade RouterOS with no problems.
Moreover, when I click refresh on WinBox4.0beta4, it takes longer for it to detect recently powered up mikrotiks as compared to WinBox 3.41.
Parrot Security 6.2
1) you can use "on a mac, this works for me:am i missing something, where is?
*) added command line launch parameters ( WinBox <connect-to> <addresess> <password>);
open /Applications/WinBox.app --args <address> <user> <password>
open -a Winbox
/Applications/WinBox.app/Contents/MacOS/WinBox 192.168.99.1 username password
Is that an actual monitor resolution in your case, or just a small sized Winbox window?There's no scrolling in the Settings pane which can result in the inability to see or interact with options for short window heights.
The Settings header could also be moved up to the top across from the close button and perhaps move the descriptive text into forthcoming hover Tooltips
Settings.png
Could not repeat the issue. What operating system are you using, and is this WinBox 4beta4 ?Workspace Pulldown doesn't show full workspace name even if there is plenty of room. Example is "Test Workspace":
workspace.png
Can you clarify what you mean? Or make a support ticket. This type of general complaining does not help anyone, just spams the topic.Big Sur here. Error handling is apparently not the highest of priorities in this beta - it is ok - beta break idc. It would help to have some kind of log file which I could hand over to Mikrotik for inspection. But logging/debugging is apparently no top prio either. And I guess a "I hit the update button" is of no special help for developers. lol
I can understand @maisondasilva where he'd like to have the "pull out" list of items invariant. So perhaps the items, not feasible for a particular connected device could be present on the list but inactive (and displayed, but in a very low contrast) so that it does consume space on the list and thus doesn't affect the place of other, active, items.Some devices simply do not support health monitoring. It's not a winbox bug!
WinBox v4 is great so far for a beta, except when it crashes a router. See my post here: viewtopic.php?t=210639
Then that is where the focus should go first, not to the oldest log entry.new entries are added to the bottom
Saduff, we managed to repeat the issue. It does not crash the router, but there is high load and a delay, when the Workspace tries to load certain non-existing switch related windows. We are fixing it.
Edit: Although it turns out, this is a RouterOS bug, not winbox. I also added it to the list.
Apologies my mistake. I thought this was a new application with opportunities for improvements.Have you seen the RouterOS Log window? Same. New entries at the bottom.
Why is not <own> the solution? It is exactly the same as it was in winbox3On another note, I would like to be able to save devices together with a workspace like it used to be with sessions in v3. So when connecting to a saved device, it would open the saved workspace automatically. Using <own> for this is not a solution.
Why is not <own> the solution? It is exactly the same as it was in winbox3On another note, I would like to be able to save devices together with a workspace like it used to be with sessions in v3. So when connecting to a saved device, it would open the saved workspace automatically. Using <own> for this is not a solution.
Edit: OK so you want winbox to remember which workspace you used last
Select the needed one when connecting, or even change to another one while connected.
This quotes message from me is only to understand with my previous message.Can you clarify what you mean? Or make a support ticket. This type of general complaining does not help anyone, just spams the topic.Big Sur here. Error handling is apparently not the highest of priorities in this beta - it is ok - beta break idc. It would help to have some kind of log file which I could hand over to Mikrotik for inspection. But logging/debugging is apparently no top prio either. And I guess a "I hit the update button" is of no special help for developers. lol
The same issue on MacOS Monterey.I opened Winbox beta3. I see the "Update available" info on right top of window. I click on the Update button. Then the download-progress dialog appears. When download-dialog progress bar reached 100% Winbox closed itself. It did not open again. The icon on the desktop was gone. No Winbox Icon in launcher either. Winbox was just removed from my MacOS system completely.
Saved devices should save the linked workspace!! definitely!Yes. Well, WinBox already remembers the last used workspace globally, but I want it to remember per device.
Infabo, the macOS Apps should be located in the Applications directory, not on your desktop. I guess this is where the issue lies. Desktop is by default in the cloud (on new macs)
I have Winbox 4 beta3 installed on my Macbook running Big Sur. I installed the Winbox app on my desktop (from DMG dragged to desktop). I opened Winbox beta3. I see the "Update available" info on right top of window.
Yes it isMust I open the Finder app and navigate manually to a system app folder and then drag it there? That cant be the way to go.
So basically 24h since release of beta4. My running Winbox instance still does not show update notification on Linux client.How frequently does Winbox check for updates? No notification until now.
On launch! Relaunch it.So basically 24h since release of beta4. My running Winbox instance still does not show update notification on Linux client.How frequently does Winbox check for updates? No notification until now.
When you change sorting of "#"-column in log window from default ascending to descending -> new items are on top. When new items appear, they appear at top. So where is the issue here and why everyone so angry? It is possible already.Have you seen the RouterOS Log window? Same. New entries at the bottom.
Unfortunately it doesn't matter. My Winbox is in "Applications" and it is also deleted when I try to update itthe macOS Apps should be located in the Applications directory, not on your desktop. I guess this is where the issue lies.
Yes most of .dmg packages offer this layout which just have a link to /Applications folder in the dmg window. It would be the simplest way to offer the application as well as updates because it is familiar for user and easier to implement than current automated way that does not always work. DMG in current form just implies that user has to copy-paste the app to /Applications folder manually.But your DMG installer did not offer me a way to add the app to the App directory. Other installers look like a drag-drop window showing the application you want to install, besides a text like "drag to app directory". You drag the icon and it is installed. But the Mikrotik Winbox installer window is just a window with an icon. How to drag it to app directory? Must I open the Finder app and navigate manually to a system app folder and then drag it there? That cant be the way to go.
стандартное 13:53:01.514935+0300 runningboardd Acquiring assertion targeting [app<application.my.example.com.31625066.31625072(501)>:20082] from originator [daemon<com.apple.coreservices.appleevents(55)>:363] with description <RBSAssertionDescriptor| "AE/WinBox" ID:175-363-3295 target:20082 attributes:[
<RBSDomainAttribute| domain:"com.apple.launchservicesd" name:"LSNotification" sourceEnvironment:"(null)">
]>
стандартное 13:53:01.538343+0300 WinBox LSExceptions shared instance invalidated for timeout.
стандартное 13:53:41.346579+0300 kernel hfs: unmount initiated on WinBox on device disk3s1
ошибка 13:53:41.740524+0300 Finder validatedCachedResults: unable to create keyName from: {
"CACHE_DELETE_URGENCY" = 3;
"CACHE_DELETE_VOLUME" = "/Volumes/WinBox";
}
ошибка 13:53:41.740571+0300 Finder Bad volume: /Volumes/WinBox
стандартное 13:53:41.740890+0300 Finder CacheDeleteCopyPurgeableSpaceWithInfo result for unknown!! : {
"CACHE_DELETE_ERROR" = "Bad volume: /Volumes/WinBox";
}
ошибка 13:53:41.843640+0300 Finder validatedCachedResults: unable to create keyName from: {
"CACHE_DELETE_URGENCY" = 3;
"CACHE_DELETE_VOLUME" = "/Volumes/WinBox";
}
ошибка 13:53:41.843741+0300 Finder Bad volume: /Volumes/WinBox
стандартное 13:53:41.844523+0300 Finder CacheDeleteCopyPurgeableSpaceWithInfo result for unknown!! : {
"CACHE_DELETE_ERROR" = "Bad volume: /Volumes/WinBox";
}
ошибка 13:53:42.079893+0300 Finder validatedCachedResults: unable to create keyName from: {
"CACHE_DELETE_URGENCY" = 3;
"CACHE_DELETE_VOLUME" = "/Volumes/WinBox";
}
ошибка 13:53:42.079946+0300 Finder Bad volume: /Volumes/WinBox
стандартное 13:53:42.080288+0300 Finder CacheDeleteCopyPurgeableSpaceWithInfo result for unknown!! : {
"CACHE_DELETE_ERROR" = "Bad volume: /Volumes/WinBox";
}
стандартное 13:53:45.128256+0300 kernel hfs: mounted WinBox on device disk3s1
стандартное 13:53:45.176052+0300 kernel ASP: Security policy would not allow process: 20284, /Applications/WinBox.app/Contents/MacOS/WinBox
стандартное 13:53:45.182738+0300 kernel ASP: Security policy would not allow process: 20285, /Applications/WinBox.app/Contents/MacOS/WinBox
стандартное 13:53:45.189912+0300 kernel ASP: Security policy would not allow process: 20286, /Applications/WinBox.app/Contents/MacOS/WinBox
ошибка 13:53:45.235352+0300 Finder validatedCachedResults: unable to create keyName from: {
"CACHE_DELETE_URGENCY" = 3;
"CACHE_DELETE_VOLUME" = "/Volumes/WinBox";
}
ошибка 13:53:45.235402+0300 Finder Bad volume: /Volumes/WinBox
стандартное 13:53:45.235683+0300 Finder CacheDeleteCopyPurgeableSpaceWithInfo result for unknown!! : {
"CACHE_DELETE_ERROR" = "Bad volume: /Volumes/WinBox";
}
ошибка 13:53:45.236335+0300 Finder validatedCachedResults: unable to create keyName from: {
"CACHE_DELETE_URGENCY" = 3;
"CACHE_DELETE_VOLUME" = "/Volumes/WinBoxUpdateVol";
}
ошибка 13:53:45.236394+0300 Finder Bad volume: /Volumes/WinBoxUpdateVol
стандартное 13:53:45.236505+0300 Finder CacheDeleteCopyPurgeableSpaceWithInfo result for unknown!! : {
"CACHE_DELETE_ERROR" = "Bad volume: /Volumes/WinBoxUpdateVol";
}
стандартное 13:53:45.250180+0300 WinBox OSErr AERemoveEventHandler(AEEventClass, AEEventID, AEEventHandlerUPP, Boolean)(GURL,GURL handler=0x7ff8013562d6 isSys=NO) err=0/noErr
стандартное 13:53:45.257143+0300 WinBox Entering exit handler.
стандартное 13:53:45.257204+0300 WinBox Exiting exit handler.
стандартное 13:53:45.342967+0300 mDNSResponder [R2844] DNSServiceCreateConnection STOP PID[20082](WinBox)
стандартное 13:53:45.439466+0300 loginwindow -[PersistentAppsSupport applicationQuit:] | for app:WinBox, _appTrackingState = 2
стандартное 13:53:45.439516+0300 loginwindow -[PersistentAppsSupport applicationQuit:] | App: WinBox, quit, updating active tracking timer
стандартное 13:53:50.441728+0300 loginwindow -[PersistentAppsSupport saveLogoutPersistentState:finalSnapshot:] | previouslyRunningApps: (
That's exactly right, you understood my complaint perfectly. The list changes the position of the options, even though the RB433 and hAP Lite mini don’t have temperature sensors, the menus are the same for both. I think it’s important to maintain consistency.I can understand @maisondasilva where he'd like to have the "pull out" list of items invariant. So perhaps the items, not feasible for a particular connected device could be present on the list but inactive (and displayed, but in a very low contrast) so that it does consume space on the list and thus doesn't affect the place of other, active, items.Some devices simply do not support health monitoring. It's not a winbox bug!
thanks for the fantastic Job !! . the mikrotik hardware deserves great softwareThis is a big day for us and hopefully for you too.
WinBox 4 is finally here, for Windows, macOS and Linux.
- We have Dark mode!
- Apps are native!
- Most importantly, since it's all built from zero, we have the ability to quickly change and fix things!
You, our beloved forum users, are the first to get it. Don't tell anyone just yet :D Just don't be too harsh on us yet, first, let's celebrate that it's finally the day!
user@MacBook-Air~ % cd /Volumes/
user@MacBook-Air /Volumes % ls
Macintosh HD WinBox WinBoxUpdateVol
+1hope will add this small feature from v3 to v4.
easy to identify the parent and child.
v4
Screenshot 2024-09-06 122834.png
v3
Screenshot 2024-09-06 123304.png
I've not experienced the same thing. Unfortunately, it is terribly slow and clunky once you are connected to a device and the window is maximized. Main menu navigation and functionality seems to be fine. Issues only begin once you connect to a device.
And that is perfectly OK, IMO, if I have many routers connected, as I often do, I don't want to have to reconnect to all of them just because there is a new update. Check on startup (or manually later) is perfectly fine...Hm, but I assume that many professionals have Winbox running without closing for days or even weeks. They won't get notified
just click the "new winbox" button to open a new instance, old ones don't have to close to check for updatesAnd that is perfectly OK, IMO, if I have many routers connected, as I often do, I don't want to have to reconnect to all of them just because there is a new update. Check on startup (or manually later) is perfectly fine...Hm, but I assume that many professionals have Winbox running without closing for days or even weeks. They won't get notified
/system/note
Actually ... it is sorted alphabetically.I found a bug
System - RouterBOARD - Settings, reverse order of CPU frequencies
Снимок экрана 2024-09-06 222410.png
Very minor.. But in LTE firmware upgrade/check sections, the error message appears at bottom. And, the "Starting" part is not cleared upon an error.
Screenshot 2024-09-06 at 11.30.13 AM.png
It seems the new style error/status just below the status (which I like), but the LTE does not follow this:
Screenshot 2024-09-06 at 12.45.38 PM.png
+1This looks lovely, and I'll check it out. Windows, MacOS, and Linux.
However, one killer bit I'd love to see added to Winbox: public key auth. We have an ongoing war internally about killing off winbox because it means our techs are storing passwords in their laptops. Personally, I use SSH at least 80% of the time, and just don't store creds in winbox. Making Winbox capable of using public key auth like SSH would eliminate the issue. Joe would just have his private key imported to winbox and we'd be done.
> Linux distribution users wish for better distribution methods (unclear, many say current way is OK!)Please do not suggest things that are already in this list
Known issues to be addressed (updated Sept 6.) :
- Keyboard shortcuts missing (currently only cmd/ctrl+W works)
- Improve contrast in both light and dark modes for old displays with low contrast ratio
- Most people prefer Tabs over Dropdowns
- Needs list of open windows
- Comment column functionality is confusing for many people
- Many UI buttons need Hover help text
- Needs clear UI to import Winbox3 saved routers, and for saving the database to Cloud Folders
- Some font legibility issues in some Linux installations, also in some cases where Windows OS has non standard DPI or scaling.
- Special characters lost when upgrading from WinBox3, but work fine when entered via WinBox4
- Side menu popup (IP etc) is lost too quickly, when moving mouse diagonally
- Columns can't change order by dragging
- Log, Ping etc. windows don't automatically go to end of entries
- Log colors for severity levels missing
- macOS trackpad does not scroll sideways
- Can't Select All items with keyboard
- Some drag and drop issues with files. Can't drag file to Desktop
- Skins not supported
- Quick Find missing
- Vertical grid requested by several users
- Vertical row height needs to be more compact, as requested by several users
- Linux distribution users wish for better distribution methods (unclear, many say current way is OK!)
- Windows version is sluggish when quickly moving around windows, lags behind mouse. Known bug and will be fixed.
- Needs ability to "select many routers and connect to all" in Loader
- Need auto light-dark mode setting based on OS settings
- Missing tree view of sub-items in tables, like VLANs, Queues, etc.
- LTE Interface graphs are missing
- Can't ping DNS name
- if you connect from the Saved list it will automatically choose "Keep Password"
- should be some vertical split control between the login/password on left and the neighbors
- a few people on macOS can't auto upgrade, winbox closes, no upgrade happens, as file can't be overwritten
- router experiences load and possible crash, when workspace tries to load certain non existing windows (routerOS bug, not winbox)
Maybe we should have a poll on the subject... that way we should know definitively...I am dubious about "many" saying it "is OK!".
That is not even true. If you use a GUI file manager you can simply double click the executable.You have to open the terminal and navigate to the extract location, to run the binary manually - this is definitely "not OK".
There are always users with different proficiency levels... there are those that reply to a long list of known problems by quoting the entire list and then a single item.> Linux distribution users wish for better distribution methods (unclear, many say current way is OK!)
I am dubious about "many" saying it "is OK!".
You have to open the terminal and navigate to the extract location, to run the binary manually - this is definitely "not OK".
It doesn't even contain a desktop icon to potentially copy it manually into "${HOME:?}/.local/share/applications", what to say about it installing itself like it does on the other operating systems.
I think Woobm was a short-lived product that did not meet up to its expectations, it has been discontinued and probably is no longer really supported...I can't login to MikroTik with Woobm USB stick.
UPD: Woobm has always worked terribly
+1 (especially for GROUPING / GROUP - separate to notes) and action menu on the right)!Just a few, i think a few of these may have been commented above.
- Grouping, we use groups to "GROUP" customers together then notes to identify what the routers are. This is the biggest one!
- The actions menu on the right, with detect internet should go someplace else, not good to have lots of blank screen real estate. Or have the ability to collapse it.
- VLANS and VRRP are not sorted. I.e. you can't tell what interface the vlan belongs too. or what interface the vrrp belongs too
- No master/backup on vrrp.
- does not load large routing table. Super slow.
- no more escape to close window?
This you and probably others suggested many times for years in Winbox release topics. It did not find an 👂 as they still opted for their proprietary binary Format. Why should they change now?Suggestions:
- make the state files (settings, addresses, workspaces) human-readable e.g. by using JSON or XML format instead of binary
There are a lot of Linux distro methods, so may not be a high priority. But AFAIK anyone can submit a flatpak/whatever if vendor does not object. In fact in another thread someone made a flatpak for winbox3+wine, which @normis commented:> Linux distribution users wish for better distribution methods (unclear, many say current way is OK!)
[...] Having it on Flathub would definitely simplify things - you could even link the Qt libraries dynamically, to reduce update size but that's not as important.
and @normis is right... a single, statically-linked binary with a icon is a trivial flatpak, compared with all machinations needed for wine.I am not familiar with Flatpak, but it seems it is a distrbution mechanism. Winbox can be distributed in any way you please, if there is no internal modification needed. But I guess it would be smarter to wait until native Linux Winbox and then set it up for this distribution method, it will be much easier, since there will be no wine involved
brew install --cask winbox
There are some implications in using XML (or something alike):This you and probably others suggested many times for years in Winbox release topics. It did not find an 👂 as they still opted for their proprietary binary Format. Why should they change now?
could you explain which are the Apps ?This is a big day for us and hopefully for you too.
WinBox 4 is finally here, for Windows, macOS and Linux.
- Apps are native!
Yes, it is sad. It would be a good moment to change it now and I fail to see what would be a disadvantage of it.This you and probably others suggested many times for years in Winbox release topics. It did not find an 👂 as they still opted for their proprietary binary Format. Why should they change now?Suggestions:
- make the state files (settings, addresses, workspaces) human-readable e.g. by using JSON or XML format instead of binary
Yes, sorry about this. I was sleeping... For some reason mistook it with the export files. :DPaternot, pe1chl is talking about Winbox configuration file. It lives where Winbox is installed, I hope you have these few extra kilobytes free on your Windows/MacOS/Linux device.
+1, especially "as a file in the flash", but not fan of XML (since RouterOS scripting only supports JSON)Suggestions:
- make the state files (settings, addresses, workspaces) human-readable e.g. by using JSON or XML format instead of binary
- make the location of workspace files configurable, including having files sent to the managed router itself (as a file in the flash)
Loving the new WinBox4 Beta with native Linux support! However, I agree that the current distribution method – manually extracting and running the binary – could be more convenient for Linux users.You have to open the terminal and navigate to the extract location, to run the binary manually - this is definitely "not OK".
So, less "change just to be different", and more "don't change it if it works fine", please.
+1 !!!JSON and XML are just examples, I could have named INI format just as well.
The point is that I want to be able to view, diff, repair, store in a version control system, etc etc.
More of "improvement". It is OK to "change" things if it gets better, right? Someone saying anything against? "Just to be different" is - I am 100% sure - not the motivation of Mikrotik. That would be nonsense anyways.So, less "change just to be different", and more "don't change it if it works fine", please.
I get the point. And this VCS thingy is crucial for any serious professional. Imagine having only ROS encrypted binary backup and no readable "export". That would also be nuts.The point is that I want to be able to view, diff, repair, store in a version control system, etc etc.
Hi, please pack the final executable with UPX. Linux version goes down to ~21 MB and there are no drawbacks i think.50MB is too big in 2024?
Ultimate Packer for eXecutables
Copyright (C) 1996 - 2024
UPX 4.2.4 Markus Oberhumer, Laszlo Molnar & John Reiser May 9th 2024
File size Ratio Format Name
-------------------- ------ ----------- -----------
55127824 -> 21697532 39.36% linux/amd64 WinBox
+1. Thank you. Though I'm already set up and therefore won't benefit, maybe many will.Loving the new WinBox4 Beta with native Linux support! However, I agree that the current distribution method – manually extracting and running the binary – could be more convenient for Linux users.
To help streamline the process until Mikrotik releases official packages, I’ve created the WinBox4 Install Helper. This script automates the installation by:
- Downloading and unpacking the WinBox4 archive.
- Creating a symlink for easy terminal access.
- Setting up a desktop entry for quick launching.
- Migrating your saved routers from WinBox3 (if available).
You can find the script here:
https://github.com/edyatl/winbox4-install-helper.git
I hope this makes using WinBox4 on Linux a bit easier for the community!
This is extremely bad idea.Hi, please pack the final executable with UPX. Linux version goes down to ~21 MB and there are no drawbacks i think.50MB is too big in 2024?
You don't want to statically link with musl, though. You get still similar problems like with statically linked glibc (i.e. broken nss; because musl won't load configured nss plugins either), and on top, musl has hosts of its own problems.You can reliably link musl statically though. musl is also MIT licensed. Assuming the app works well with musl, statically linking against musl is a really nice idea for portability.
Not true.Well, whatever You can use an standard interface to doesn't have to. Because, You see, Flatpak and whatnot get the same problem.With glibc, this is not possible without breaking its functionality. Quite a chunk of glibc is dynamically loaded (including subsystems like nss);i if you ignore it, you might break things like hostname resolution or user database. This is the reason, why even golang (which otherwise doesn't need glibc) doesn't do statically linked binaries.
So by trying to go with static binary, you are opening a can of worms with bigger problems.
The difference is, that the flatpak install locations are managed; you don't put random binary into random place. And you have still the default option for system-wide install, with property authenticated update. You are losing this with random binary in random place.Were You talking about Flatpak, that put them on "~/.local/share/flatpak" for user installations? System wide instalations would be no better than a package - since would need root password for install and update.
And good old tgz IS quite common. Installing it on user directory - for something like this - is acceptable too. One need to worry about things like /opt only when installing system wide packages. For something that doesn't use the package system and is just for one user - or portable - there is no need.
I WANT to put the binaries in random places! I don't want a system wide install for Winbox - it would either need root password to update or needed to be copied for each user on the system that used it. Easier to just send a single package - as they are doing it now. This way I put it on my user's home, and problem solved.The difference is, that the flatpak install locations are managed; you don't put random binary into random place. And you have still the default option for system-wide install, with property authenticated update. You are losing this with random binary in random place.
Good old tgz for user apps, with custom updaters with not very common. Who does that except mozilla? And even mozilla has their debian repo and manage their flatpak.
works fine for me?As far as I understand - the current version does not support calling Winbox with parameter passing? For example, now it is impossible to call this version from The Dude - winbox.exe [Device.FirstAddress] [Device.UserName] [Device.Password]
Outside of some fairly edge case dns resolution quirks, musl is generally fine as a drop in replacement for gnu libc. The benefit of statically linking is it gives you complete independence of the host's libc vendor and / or version. It's a tradeoff, but there are reasons people do it and it's not just for containers.You don't want to statically link with musl, though. You get still similar problems like with statically linked glibc (i.e. broken nss; because musl won't load configured nss plugins either), and on top, musl has hosts of its own problems.You can reliably link musl statically though. musl is also MIT licensed. Assuming the app works well with musl, statically linking against musl is a really nice idea for portability.
Musl is fine for containers, where you control the entire environment; but not for an app distributed to users, where all that it gets you is increased support headaches.
+1Need the group feature back badly. This is a show stopper for us as we sort clients that way.
Thought the same till started to use them. A combo of windows that used to be tabs can now be seen at same time . Very powerful if used with workspaces. You need to get past the initial jarring effect of change first. Then all will become clearer. Going back to old ways is not the way forward.Lots to love, fresh, open, cleanish. haaaaaaaate the dropdown replacement for tabs though, much slower / irritating.
Bring back tabs!
+1, agree.A combo of windows that used to be tabs can now be seen at same time . Very powerful if used with workspaces. You need to get past the initial jarring effect of change first. Then all will become clearer. Going back to old ways is not the way forward.
You can enable comments and sort by comment like this+1Need the group feature back badly. This is a show stopper for us as we sort clients that way.
Hi,Groups have been handy everywhere.
viewtopic.php?p=1096425#p1096425Hi,
I have never used groups. Can you give me an example of how you use groups
regards
Can 100% confirm this - Option set for one network popped inadvertently into other network and messed DHCP up for that. Was forced to correct this using Winbox 3.new winbox 4 on linux issue: seems to resurface old 'Option sets' in ip->DHCP Server->Network screen and leases screen for no reason. even after deleting and saving, it still keeps it and does not want to delete it(when checked again). this is causing havoc in my network clients(took a long time to identify problem). have gone back to using old winbox for now where i am able to undo the damage.
This is a beta, and you can give feedback to MT.Going to skip v4. This is a step back. As mentioned before:
1. Colouring makes it hard to read.
2. Menu's are now hidden in dropdown menu's. Too much clicking and repeating.
3. Dropdown menu's are not consistent! Some of them are on top, some of them are formed below in a gray bar. For instance: dropdown menu in Interfaces are different then when you look for the tabs in a simple queue.
4. Take a look in the firewall section to determine what is wrong with V4 of Winbox. Hard to read, cropped, spacing not correct etc.
Or, perhaps just even mouse navigation support in the existing Terminal window... i.e. click/scroll in the terminal window when the CLI "edit" is shown in a winbox4 terminal would be kinda nifty. e.g. In MacOS Terminal running "vi" to edit file, option-click lets you move the cursor to a position & "scroll wheel" let you move up/down when editing.The software engineer in me dreams of a more fully-featured script editing window with line numbers and maybe even syntax highlighting :)
Given the new winbox4 scheme & likely "controversial"... perhaps instead of a popup "alert dialog" for /system/note... follow the same "red headers" used elsewhere for other errors/message e.g. have the "note" appear below the full-width below the title bar of main window (similar style to the "i3-nagbar"), instead of free-floating modal dialog.[...] System/Note doesn't pop at login when that option is selected.