Thank you for the suggestion, Amm0. Added to wishlist.
Every window is a separate process on Mac - hence multiple icons in dock. Using "New Winbox" option starts a new process.Not sure if anyone has mention, but with multiple winbox4 windows... they all appear as seperate icon in MacOS's launchbar. Normally multiple windows of an application, still only have one icon in the launchbar with the various window name showing in the context menu. The current "one icon per winbox4 window" means it actually hard to find the same window without clicking on the icon to see what it's connected to.
On MacOS, multiple winbox4 windows should appear as ONE icon, with multiple windows on the context menu.png
on macOS the apps are grouped under a single icon by default, it's different from Windows, because in macOS dock you don't have titles of windows. So separate icons are confusing.
Behaviour should adhere to system settings. I don't use Mac, but on Windows and Linux I prefer not to have apps groupped ... and there's system-wide setting for that both in Windows and KDE (which is what I use on Linux if I can choose). In normal apps, there's a text pop-up tab when one hovers mouse over the app icon on taskbar/launchbar ... this text window should show some meaningful onfo about device to which particular winbox window connects ... that one should help to choose the right winbox without clicking the app button first.
$ ./WinBox
APP,INFO: version: "4.0beta4"
libEGL warning: DRI3: Screen seems not DRI3 capable
libEGL warning: DRI2: failed to authenticate
libEGL warning: DRI3: Screen seems not DRI3 capable
Segmentation fault (core dumped)
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 24.04.1 LTS
Release: 24.04
Codename: noble
What is actually taking up space now are the status "pills" being placed at the top of the windows, and more so, as those visually resemble buttons. Those should have stayed at the bottom of the windows, at the bottom status bars, and visually look just like labels, just like with 3.x Winbox.I just want give a counterpoint the "Most people prefer tabs instead of drop downs", I suspect most of those people haven't really played with workspaces yet. I'm not the first to bring this up but it bears repeating. If implementing tabs means you can't have multiple of the same "group" open at the same time, then I much prefer the way it is currently. Even if you can pop out extra windows like today but with tabs, the tabs are taking up unneeded space for my use case. If tabs get implemented, I really hope they're optional.
tabs - at least as implemented in winbox 3 - means for each window with tabs across the top, only one tab is active at a time. with the v4 implementation, any item in the drop down can be open at the same time as any other item. There is a little icon to the right of each item in the drop down list, and that icon means to open it in a new window instead of replacing the contents of the current window. Combined with the ability to save window arrangements in workspaces, this is a very powerful feature. So using workspaces, you can set up a selection of panels that you might use for a given task, like editing firewall rules, maybe another for managing bridges, etc. For my firewall rules workspace, I have firewall rules open at the same time as nat rules and mangle rules, all in their own section of the screen, instead of having to flip back and forth between each one using tabs.Tabs were much better both visually and practically, because you saw the options right away, and you needed one click, instead of two
that's been covered quite a few times as well, but the hot keys are coming back. for now, cmd / ctrl w closes windows.Esc dosn't close window anymore
And in general hotkeys would be nice to have
Very good summary of things thats not works wellNice to see an update. In the main it seems to work well, but...
1 - <esc> doesn't work any more - closing a whole bunch of panels is now more time consuming and frustrating (the escape key is in the same place on all my keyboards, the shift/control keys aren't).
2 - Comments aren't shown by default - again, more time/frustration in enabling them. Comments are important!
3 - Status tool-tips aren't shown when you hover the mouse over them like they were on Winbox3 (see screenshot) - There doesn't seem to be an easy way to find out what all the letters mean. Screenshot 2024-08-29 083013.png
4 - Removal of the tabs at the top of the panels and using a drop box instead makes navigating the options/contents more time consuming and frustrating - it's no longer easy to see what all the sub-categories are and no longer possible to quickly flip between subcategories.
5 - 'Configuration' takes up a chunk of the right hand side of each panel - it means I have to make the window wider and means more scrolling on smaller screens (like the tiny laptop I use on customer sites) - again, more time required and more frustrating.
6 - <ctrl>+<tab> doesn't work any more - no longer easy to move between panels.
7 - <ctrl>+m doesn't work any more - much more time consuming to add comments (double-click line, click in comment box, type comment and then back to the mouse to click on 'OK')
8 - <Num-> and <Num+> no longer enable/disable rows
9 - <Del> does work (deletes row), but <Ins> doesn't (insert row)
Sorry about the above, it does sound like I'm having a moan, but it does seem that while Winbox3 has its limitations, one thing it was very good at was giving fast access to changes and also seeing required information. Winbox4 seems to have slowed down the workflow not just a bit, but quite a lot. For this to be usable, day to day, I need much more keyboard control - bring back the shortcuts!
I do appreciate that this is a beta release, but please please add in more functionality to speed up the workflow - don't make me frustrated by forcing me to use my mouse when a keyboard shortcut would make an action much faster.
For example, to open NAT rules and add a comment to a row (where "¬" means toggle between keyboard and mouse)...
Winbox 3 - <click><click><click><click>¬<ctrl>+m[type comment]<enter>
Winbox 4 - <click><click><click><click><double-click><click>¬[type comment]¬<click>
All that having been said, Winbox4 certainly looks smarter.
Nicholas.
MT already said somewhere that they will return tabs back instead of dropdown lists. I hope, they will return them in editing windows also instead of these ugly groups, because, as you correctly said, you need to scroll too much up and down to navigate.The UI update is a welcomed update. Yet, I am not convinced by the current iteration. We went from the "ugly" but very functional style and clear to read to the "pretty" but less functional & "harder to find what you need "style. Functionality and ease of use does take priority to it being pretty for me.
Try to add a new firewall rule or look at the interface list for example. What am I even looking at? Just a blob of text with almost no coherence. No indentation no grouping. The gray on gray doesn't have much contrast. The tabs are gone and now you need to scroll twice as much for everything. The graphs are horrific to look at. The more I look at the UI in Winbox 4 the worse it get. Yet I still hope this will improve since it's a beta.
oki doki sorryNo, it's not a good summary, because the very first post in this topic already clearly said, that it is a known issue, that all keyboard shortcuts are turned off.
Do not post again and again the same thing, that is already explained.
Please read the first post before posting!
Please don't! A light touch on a scroll wheel is almost always faster/easier/better than repositioning you mouse on top of the dialog where the tabs are, potentially scrolling through the tabs, and finally clicking on one of them.I hope, they will return them in editing windows also instead of these ugly groups, because, as you correctly said, you need to scroll too much up and down to navigate.
What's new in v4.0beta6:
*) minor UI improvements
What's new in v4.0beta5:
*) return tab based interace, while keeping benefits of dropdowns
*) move action buttons into table toolbar
*) change style for active sub window
*) fix macOS self-update on some systems
*) stability improvements
You could check if the location is writable, and just show a popup (at most) when it is not. You should not attempt to update if it is known to fail in advance.While "read only" is correct, because it is installed globally and Winbox is run with unprivileged user. Still one remark: it is a Linux host and I do not have an "Applications" folder. ;)
2024-09-13_10-49.png
And I improved your changelog:Following to suggestion from user "boingolover", I organized my screens to workspaces now. These tabs look awful on narrow windows.
What's new in v4.0beta5:
*) return tab based interace, while keeping benefits of dropdowns.
[b]*) tabs visibility can be toggled - see checkbox in tabs drop-down menu.[/b]
*) move action buttons into table toolbar
*) change style for active sub window
*) fix macOS self-update on some systems
*) stability improvements
Different windows have different sets of tabs so they can/have to be set separately. Btw Winbox 3 "truncated" tab list from the end in windows too narrow to show all - so it turned into tab list + dropdown combo. Now you have the option to hide unneeded tabs and there might be many of them - especially in "interface" window."Show all".......................Yeah. Very self-explaining. PER WINDOW as well. As if it weren't already tedious enough to arrange the windows. Now you have to click into each window and deactivate the tabs. UX complaints incoming.
*) return tab based interface, while keeping benefits of dropdowns
most people?This is only half done. Most people want these WebFig style dropdowns as tabs too.Code: Select all*) return tab based interface, while keeping benefits of dropdowns
tabs_please.png
this bug is already known and reported multiple times in this threadLeft / right two finger scrolling (swiping) on Macbook Air track pad does not scroll the wide windows left and right. You have to move the mouse down to the bottom of the window and drag the slider left / right.
Yes. Plenty of posts about this already in this thread. I don't think there's a need to dig up every single feedback about this. And if there's really a need then it means that the feedback has been ignored. If tabs are still a no go, then please consider allowing detaching those sections to separate windows.most people?This is only half done. Most people want these WebFig style dropdowns as tabs too.Code: Select all*) return tab based interface, while keeping benefits of dropdowns
tabs_please.png
Do you only see what you want to see? There are also plenty of posts in this thread where people asked to keep the groups as they are.Yes. Plenty of posts about this already in this thread.most people?
That's correct. Too much white space. Even traffic graphs or status section needs scrolling. I wouldn't mind if optionally you can still have the collapsed groups for those who still insist. Just give us the option at least. I don't mind if collapsed groups is the default, but there must be a way to return to the old tabbed windows.+1 for tabs everywhere. I never used webfig because of this, it's unusable unless you work on a 9:21 monitor.
Options are good !It is under consideration as a configurable option. Zebras vs full grid.
Yesssss !Code: Select all*) return tab based interace, while keeping benefits of dropdowns *) move action buttons into table toolbar *) change style for active sub window
I have the same problem.... "reading the index file" and nothing more... WinBox 4.0beta6 (at 4.0 beta 4 was the same). The WinBox 3.41 works OK with that MT server (x86 machine).I have problem logging in with winbox 4.0 b3 on a CHR running 6.49.17. I only get "Reading the index file"
Dont have any problem logging in with winbox 3.x on same computer. Have tried both on Mac and Windows but same problem even rebooted the router but the same message was there. Have made a bug support case of this as SUP-163841
Skärmavbild 2024-08-31 kl. 16.41.42.png
While this a HUGE improvement, unfortunately tabs have only returned in primary windows. Any configuration dialog boxes are still the WebFig style where you need to scroll through all the options.Code: Select all*) return tab based interace, while keeping benefits of dropdowns
Are you sure? I'm just not sure there are that many fan of the "webfig-like dialogs". While the minority, the dropdown did have some "fans", other than me, for the pop-out - which y'all now gracefully solved by using the title bar space more effectively to mimic tabs. But I have not seen "OMG I love the webfig look in dialogs here" here ;).Yes, and that one will stay for now. As seen in the thread, it is a much more divisive topic, than main window Tabs
One idea is that it's "Workspace" has configurable options for stuff like zebras, tabs, etc. There is already a pop-out in Workspace that brings up a dialog, but it just has autosave. Just seems a natural spot to store these things (vs some system-wide setting).Options are good !
One more thing to add. If you set up a custom workspace and you had a section not collapsed and you quit WinBox, it will not get saved. On the next session you need to click and scroll again to see what you want. You are not allowed to see status or graphs and you need to fiddle with it every single time. This divisive topic needs a solution that satisfies both sides.Hopefully y'all are still mulling the webfig-like collapsable selection inside of dialogs (the other place where tabs were lost). Not necessarily saying "bring back tabs", but webfig-like dividers are "less productive" than winbox3 if you actually need to change a settings - way more clicks+scrolling. And even worse when to look at some status section inside a dialog (which is often at the very bottom).
I don't have a problem with them per se, but they do not work with saved workspaces well. They don't save neither expanded/collapsed status, nor scroll position. After restoring the saved workspace, they get back to their default state instead.Yes, and that one will stay for now. As seen in the thread, it is a much more divisive topic, than main window Tabs
Many thanks for these changes. The active window now stands out much better. I love the new border color, especially in dark mode.Code: Select all*) return tab based interace, while keeping benefits of dropdowns *) move action buttons into table toolbar *) change style for active sub window
please fix dhcpoptions nagging issue. (shows up unannounced in dhcp server network and leases page when saved)Code: Select allWhat's new in v4.0beta6: *) minor UI improvements What's new in v4.0beta5: *) return tab based interace, while keeping benefits of dropdowns *) move action buttons into table toolbar *) change style for active sub window *) fix macOS self-update on some systems *) stability improvements
It's a known issue and it'd due zo neglect of properly handling different encoding schemes ... all UIs simply accepted characters as bytecode and didn't interpret them according code page. So it was always a problem if one used different UIs (e.g. winbox3 on windows using whichever windows code page, CLI with UTF-8 translation, etc.)And all Cyrillic comments are unreadable in WinBox 4
True. But PSA there is still only one config that store things... And config just stores the bytes as provided from whatever UI/CLI. So can enter Cyrillic as UTF-8 in winbox4, but then that won't render in winbox3. For example, if you want the € in some comment, what you'd enter at CLI vary depending on the winbox used...It seems that winbox4 uses UTF-8 (finally), just like (probably) your web browser running webfig.And all Cyrillic comments are unreadable in WinBox 4
/interface/ethernet/set ether1 comment="\80 - euro in winbox3"
/interface/ethernet/set ether1 comment="\E2\82\AC - euro in winbox4/webfig"
+1 tabs everywhere!+1 for tabs everywhere. I never used webfig because of this, it's unusable unless you work on a 9:21 monitor.
It depends. Things being static (always in same place) has advantages too, I always know where they are and don't need to look for them. E.g. if I want to see statistics for firewall rule, in WinBox 3 it was just one click on always the same place (the tab). In WinBox 4 it means scrolling, finding the right collapsed section and click to expand it. And the same goes for all now collapsed sections that were previously tabs. How is it better?A light touch on a scroll wheel is almost always faster/easier/better than repositioning you mouse on top of the dialog where the tabs are, potentially scrolling through the tabs, and finally clicking on one of them.
This! Is a pain in the proverbial.when WiFi links change frequency due to DFS...
+1, if possible. Great idea! Way more functional.Just like that:
TabGroup.png
<key>CFBundleIdentifier</key>
<string>my.example.com</string>
These are basically my only major complaints since day one:
In fact that's probably the main problem with whole WinBox 4. Everything in it is HUGE. Sure, there's zoom, so I can make it smaller, but it doesn't really help. Look at it:
winbox4-firewall-rule.png
I'm currently trying to go with 84%, which already has smaller font than WinBox 3 and I'm still seeing much less info in same space.
It's the same problem that almost every new software has. Perhaps it's trying to be touch-friendly, which I'm sure is lovely for people who want it, and I wholeheartedly support them to have it. But that's not good reason to ruin things for everyone else who's not interested in that and would much rather prefer higher information density. So please, can we have optional "compact" version without useless margins and padding? It would help a lot.
Creating a flatpak manifest around a statically compiled binary as it is now is no problem at all.
That would be great I think. So essentially 3 states of those named groups (especially in Firewall rule properties window) would be welcome:*) groups in property dialogues (the expandable panes referred to as "dropdown" in some of the posts above - probably as opposed to "tabs" but to me distinctly different from the combo-boxes that where initially used at the window-level): what would be killer IMO and a huge benefit of v4-style groups vs v3-style tabs if:
-- on opening an existing rule/interface etc, besides the `general` group being fully expanded (keep that), to also (and only) have visible properties that are *set* (from their defaults) in the other groups
-- on expanding the groups making visible all properties in normal order
-- on collapsing the groups, consider to collapse all properties again - whether they are set or not - to also allow users to get things out of the way
I second that. It makes sense to separate configurable properties from statistics.*) groups in property dialogues: I´d probably still like status, statistics etc on a tab or maybe a different (expandable) pane, separate from configurable properties and directly accessible rather than first scrolling down and then having to click to expand the group;
I don't know whether graying out inactive buttons is better than hiding them, but I would make them at least looking in the same style (like the blue (+) icon for "New" button).*) buttons in windows: great to see the `enable`/`disable`/`remove` buttons be placed with the `new` again. But as someone else noted before, I agree it'd be a more consistent experience to always display these and just grey them out instead of having UI elements appearing and disappearing depending selection;
The benefit of having one statically compiled binary is that one can choose to package it as-is as an rpm, deb or flatpak without any further work required by Mikrotik devs.
Agreed, Appreciate the tabs added to Winbox 4.0beta6 however its still a struggle with the collapsable info like IP address, traffic, status etc, it'd be great to have the option of drop down/tab in the same format as IP --> Firewall etc (Much like the old Winbox) as if the window is smaller you have to scroll to find the one you want then expand.This is only half done. Most people want these WebFig style dropdowns as tabs too.Code: Select all*) return tab based interface, while keeping benefits of dropdowns
tabs_please.png
+1This is only half done. Most people want these WebFig style dropdowns as tabs too.Code: Select all*) return tab based interface, while keeping benefits of dropdowns
tabs_please.png
At least Winbox 4.0beta6 QR codes are readable with Android app for me.tldr: Winbox 4beta generates WireGuard QR codes that Android WG app can not read; Winbox 3.41 is fine
[ ... ]
Anyone else have the same?
There's one already waiting in Flathub queue: https://github.com/flathub/flathub/pull/5588I am a strong flatpak supporter, but my vote still is for a solution that is independent from the way of distribution.
Creating a flatpak manifest around a statically compiled binary as it is now is no problem at all. I would even offer myself to do that, I already maintain a flatpak wrapping for another precompiled application.
Edit: Here you go, I created a working flatpak manifest: https://github.com/mkfrey/com.mikrotik.WinBox
read first postHow can I migrate my windows version .WBX file into the new beta6 for macOS ?
MacOS version is in .viw2 -format.
I also noticed you can't just enter the IP and hit enter like in winbox3, now it's a bit more cumbersome to have to then first click start.+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!
read first postHow can I migrate my windows version .WBX file into the new beta6 for macOS ?
MacOS version is in .viw2 -format.
You don't need to export it. Just find the old WinBox3 directory and move the files to the new WinBox4 directory and your saved routers will be shown. Import/Export is not needed in this case, as WinBox4 does not yet have any import button.No, that won't work. The files are in different file types.. I followed the 1st post but it doesn't make sense when it's different filetypes. It won't recognize it....I have exported to wbx and the new one is viw2. ?
read first post
+1 from me... I think that "most people" DO want/prefer tabs to drop-downs.+1 for tabs everywhere. I never used webfig because of this, it's unusable unless you work on a 9:21 monitor.
But it is only the list of routers, not the saved sessions/workspaces, right?You don't need to export it. Just find the old WinBox3 directory and move the files to the new WinBox4 directory and your saved routers will be shown. Import/Export is not needed in this case, as WinBox4 does not yet have any import button.
Yes, there is no other import right now, only saved routers. As I said, it is in the known issues list.But it is only the list of routers, not the saved sessions/workspaces, right?You don't need to export it. Just find the old WinBox3 directory and move the files to the new WinBox4 directory and your saved routers will be shown. Import/Export is not needed in this case, as WinBox4 does not yet have any import button.
EXACTLY THIS.In fact that's probably the main problem with whole WinBox 4. Everything in it is HUGE... I'm still seeing much less info in same space.
It's the same problem that almost every new software has. Perhaps it's trying to be touch-friendly, which I'm sure is lovely for people who want it, and I wholeheartedly support them to have it. But that's not good reason to ruin things for everyone else who's not interested in that and would much rather prefer higher information density.
yes the ENTER key functionality has not arrived yet ... same with applying changesI also noticed you can't just enter the IP and hit enter like in winbox3, now it's a bit more cumbersome to have to then first click start.
+1
It should be in a way that only sections with unset values are collapsed in dropdowns.
One possible way of "compromise" - bring tabs into object windows, but set them to auto-scroll to according section in window i.e. retain all in same window (as it is now), but with tabs that bring the feature back to people obsessed with it. This way people who want to waste time on clicking through tabs, can do so while others can just scroll through all values in same view...
I think everything is becoming bigger, because new devices have 4K and 5K screens and there everything is too small. The biggest downside of this is for older monitors and smaller resolutions, I guess.EXACTLY THIS.In fact that's probably the main problem with whole WinBox 4. Everything in it is HUGE... I'm still seeing much less info in same space.
It's the same problem that almost every new software has. Perhaps it's trying to be touch-friendly, which I'm sure is lovely for people who want it, and I wholeheartedly support them to have it. But that's not good reason to ruin things for everyone else who's not interested in that and would much rather prefer higher information density.
Warning: Ignoring window icon 1048578 exceeds maximum xcb request length 1048575 (:0, )
I got a similar one in beta4. I'm not too concern, since it seems like one-off (as my computer has come back from sleep plenty of times). But if useful I can send the report in ticket. I did use the "Send to Apple" but I'm not sure y'all can see those since it's not in the App Store but dunno.Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000000
Exception Codes: 0x0000000000000001, 0x0000000000000000
Termination Reason: Namespace SIGNAL, Code 11 Segmentation fault: 11
Terminating Process: exc handler [14954]
VM Region Info: 0 is not in any region. Bytes before following region: 4370923520
REGION TYPE START - END [ VSIZE] PRT/MAX SHRMOD REGION DETAIL
UNUSED SPACE AT START
--->
__TEXT 104870000-106e5b000 [ 37.9M] r-x/r-x SM=COW /Applications/WinBox.app/Contents/MacOS/WinBox
People who some call "obsessed" are maybe just "organized"?One possible way of "compromise" - bring tabs into object windows, but set them to auto-scroll to according section in window i.e. retain all in same window (as it is now), but with tabs that bring the feature back to people obsessed with it. This way people who want to waste time on clicking through tabs, can do so while others can just scroll through all values in same view...
On the branding topic...It could be good also for branding, not only for whiners who don't fully appreciate your design choices. ;) Two birds with one stone.
Well tabs inside of any window are good for organizing views by object type - technically these are just filtered views. Inside the object same concept does not work as all inside the object are part of this same object - if you take a firewall policy then all defined settings in it are parts of this same rule and you have to be able to see it all because all these parts do matter in similar way. That's why tabs do not work inside the single object.People who some call "obsessed" are maybe just "organized"?
In your shed, do you keep all the tools and stuff on one big pile and go through it every time you need a hammer or a shovel?
(let the war begin :) )
@normis ,please add this issue to your tracker. cant use winbox4 without worrying about issues it will introduce without a fix.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.
I wouldn't go as far as saying that they don't work. But I have to admit that a lone option set on Advanced or Extra tab is easier to overlook. All options together can solve it, provided that there's some intelligent display, i.e. not as it's now when all sections except first one are always hidden and have to be expanded manually.... if you take a firewall policy then all defined settings in it are parts of this same rule and you have to be able to see it all because all these parts do matter in similar way. That's why tabs do not work inside the single object.
Warning: could not connect to display :0 (:0, )
Warning: From 6.5.0, xcb-cursor0 or libxcb-cursor0 is needed to load the Qt xcb platform plugin. (:0, )
Info: Could not load the Qt platform plugin "xcb" in "" even though it was found. (:0, )
Fatal: This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.
Available platform plugins are: xcb.
(:0, )
Aborted
libxcb-cursor0 installed, libxcb-xinerama also,
adding QT_QPA_PLATFORM_PLUGIN_PATH=/usr/lib/x86_64-linux-gnu/qt5/platform/plugins does not work
ignoring "org.qt-project.Qt.QPA.QPlatformIntegrationFactoryInterface.5.3" since plugins are disabled in static builds
It is automatically checking for updates upon launchingI am Missing Check for Update Button in new Winbox 4
Which desktop environment? I can't reproduce this on Fedora Workstation 40 / Gnome.Using the linux version, when there are overlapping windows on the workspace, and you click on something on the top window, it selects the window on the bottom instead. It makes it very difficult to use.
/ip service print
Flags: X - DISABLED, I - INVALID
Columns: NAME, PORT, ADDRESS, CERTIFICATE, VRF
# NAME PORT ADDRESS CERTIFICATE VRF
6 winbox 8291 main
chain=dstnat action=redirect to-ports=8291 protocol=tcp src-address-list=RLB-RZ-WAN in-interface-list=WAN dst-port=801
Debian 12 / i3Which desktop environment? I can't reproduce this on Fedora Workstation 40 / Gnome.Using the linux version, when there are overlapping windows on the workspace, and you click on something on the top window, it selects the window on the bottom instead. It makes it very difficult to use.
hi guntisspippan Are you using 4.0beta6? Could you please create a support ticket regarding the NAT login issue along with supuout.rif file made after the issue appears and other details - what system is the WinBox running on?
I tried reproducing the issue, but it seems to work as expected. Is the "auth challange failed" error present both for 2FA and static user?
/ip ssh set forwarding-enabled=local
ssh user@remote -D 1080
server = 127.0.0.1
server_type = 5
server_port = 1080
tsocks ./WinBox
Fond small bug with "Hide password" not actually hiding the password
Steps to reproduce:
WiFi -> Configuration -> open existing configuration -> chose existing Security profile -> password will be shown in plain text
plainTextPasswd.png
It is available on the download page, the icon with itemized list next to the download dropdown. Right now it points to https://download.mikrotik.com/routeros/ ... /CHANGELOGPlease post all change logs in the first post, as well.
Unfortunately, no change with 4.0beta6...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):(while at it, please allow for copying error messages)Code: Select allERR: Could not connect, MacConnection syn timeout
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!
We've been solving for this for years with dynamic layouts and scaling. At the end of the day, it isn't perfect, as you have some minimums to represent information in terms of number of pixels (an icon scaled down to 3 pixels to fit on a 30x30 pixel screen isn't usable) but any good windowing library should handle this well if utilized properly.I think everything is becoming bigger, because new devices have 4K and 5K screens and there everything is too small. The biggest downside of this is for older monitors and smaller resolutions, I guess.
EXACTLY THIS.
P.S: of course the UX designers job is to somehow make all users happy, on small resolutions and large resolutions alike. My comment was about the general trend.
I'm also using MacOS with the current winbox4 beta6. Will be sticking with winbox3 for now using Wine.running beta6 on macOS14.6.1 for three days now, getting used to the new look & feel.
1. had a crash when I first saved a workspace.
2. red font in dark mode is nigh unreadable (37" 3440x1400px, no scaling)
3. all fonts appear oversoftened and take a lot more effort to scan across compared to Winbox3 on Wine. dark mode fonts appear crisper.
4. in bright mode, tables need more contrast between lines and clearer borders
will be sticking to Winbox3 for the moment, but am really looking forward to the moment shifting to a native macOS app :)
Yes, I would think so. Ideally there would be the capability of loadable skins like with Firefox.As Winbox 4 is based on Qt... shouldn't it be possible to have more flexibility in theming/appearance compared to old platform?
That´s is like Aple forgetting to add mouse support to newer MacOS and telling users to use keyboard instead. :-)
- Groups are missing for now, until they return, you can use Comment (previously called Note) field to sort similar items
Windows 10 in company, i dont have adm privilages i download the app and unzip in Download folder and launch from there. After click 2 times on icon - nothing as if I didn't clickWhat OS are you using, @Hakens? I assume Windows, as you are referring to taskmanager.
Is it shown on the taskbar? Where is the executable located?
Have you tried removing it and afterwards, download it again (and start it from the Downloads folder)?
I ran into the (different) problem that the window was invisible, and couldn't change it by using WinKey + Arrow up. Turned out that I could make it visible again by right clicking the icon in the taskbar and select maximize.
This is endpoint protection for non-technical users. I think not relevant for network admin domain.In a reasonably configured company environment, running exe files from the download folder is not allowed...
Did you look in System Preferences under Security > Firewall? There are setting to that control "incoming connections", it has to allow it from "downloaded apps". See https://support.apple.com/guide/mac-hel ... 0/mac/13.0I'm running beta 6 on MacOS13.
[...]
Error: "Could not connect. MacConnection syn timeout"
You read post #1 instead of random posting something?I am missing a lot of keyboard functions such as page up/down, ctrl+e etc..
You read post #1 before posting?Please add the Search and Highlight function like in the old winbox version
Missing tree view of sub-items in tables, like VLANs, Queues, etc.
You read post #1 before posting?
😉+1000
Got it... didn't even realise there was a right hand side UI element -> Configuration > Lists.@ilium007
I tested now and you can create new list and add interfaces to it no problem on beta 6.
It be nice if <tab> go through ALL the setting in a dialog box. Specifically <tab> should:- Focus on the first input field when opening a subwindow form
- Select all text when changing fields with Tab
- Add submitting forms with Enter key
Hmm, I dont' see this problem with IPv4 addresses, but I have it in IPv6 windows like IPv6 addresses and IPv6 routes.I have previously reported this bug, but I don't see it in the known issues, so I am reporting it again. Apologies if I am mistaken and it is already known.
I have found a bug in the way IPs are sorted, which only affects RouterOS 7.In RouterOS 7, the order is incorrect and varies from one session to another.
If I disable and enable the rules, their order also changes, and sometimes they are arranged correctly.
Missing tree view of sub-items in tables, like VLANs, Queues, etc.
Ah, but the WinBox4 Terminal is like weird transfer area at an airport ;) Take some UTF-8 stuff in an interface name/comment: If one follows the UTF-8 is the "codepage" for WinBox4, its terminal should also render UTF-8. What I've found is the WinBox4 Terminal uses the hexstring for high-ASCII, same as other terminal/ssh/etc: So - feature request re UNICODE - the WinBox4 Terminal should render UTF-8, not the hexstrings. It seems RouterOS can know it's a WinBox4 terminal & avoid the "hexstring substitution"... But currently even if raw UTF-8 get's in to the Terminal, it does even show that - while SSH does: Perhaps this is solvable by some "/console/settings/set outputUtf8=yes" ... but it would be nice to see UTF-8 so if one did use that in WinBox4, the UTF-8 render in at least that terminal.It seems that winbox4 uses UTF-8 (finally), just like (probably) your web browser running webfig.
[myuser@MikroTik] > /export
# 1970-01-02 00:20:33 by RouterOS 7.16
# software id = VJPT-SQGP
#
# model = C52iG-5HaxD2HaxD
# serial number = HG209NTVAFV
/interface bridge
add name=bridge
/interface list
add comment="allow macwinbox on all" include=all name=macwinbox
/interface wifi security
add authentication-types=wpa2-psk disabled=no name=mywifi
/interface wifi
set [ find default-name=wifi2 ] configuration.mode=station .ssid=mywifi\
disabled=no name=wifi-2ghz security=osmium
set [ find default-name=wifi1 ] configuration.mode=station .ssid=mywifi\
disabled=no name=wifi-5ghz security=osmium
/ip neighbor discovery-settings
set discover-interface-list=!dynamic
/interface list member
add interface=bridge list=macwinbox
/system note
set show-at-login=no
/tool mac-server mac-winbox
set allowed-interface-list=macwinbox
Oh boy, I am getting soooo tired of this. It has been said many times now that MT has taken a global approach in terms of software development by using CTRL-W/CMD-W instead of ESC to close windows. IE: there will be no ESC in v4. Use CTRL-W or CMD-W instead.Still no ESC key to close windows...
I disagree. I quite like the approach MT has taken here. It's easier to find the actions and configuration options at a glance and I can still see all the relevant device information I need, viewing on a 14" laptop screen. Admittedly, I've changed the Winbox interface zoom level to 84% which decreases the font size while at the same time allowing more device information to be seen. It was a win-win for me. I got a smaller font and more of the device info i need.I don't get this right-hand side thing. It is taking away precious space or unnecessary hiding other windows.
What was wrong with having those under the tab-bar?
Oh boy, I am getting soooo tired of this. It has been said many times now that MT has taken a global approach in terms of software development by using CTRL-W/CMD-W instead of ESC to close windows. IE: there will be no ESC in v4. Use CTRL-W or CMD-W instead.Still no ESC key to close windows...
These are the only key shortcuts that have been implemented in v4 so far.
Please read the thread through before posting.
I've just tried logging in using a MAC address with no problem using Winbox 4beta8 on Debian 12 (LMDE6), ROS v.7.15.3. Could be a bug with the 7.16 version?Thanks Mikrotik for building a Linux version of WinBox 4, but I getting the following error. "err: could not connect, Macconnection syn timeout"
This error occurs with mac address logins it does not seem to occur when the router has default config ip address.
Similar to what burnduck posted but I only got the error on Linux not Windows.
Computer Software: (WinBox 4 beta8 Linux version, Fedora 40 workstation)
Router: Mikrotik hAP ac2 RouterOS version 7.16 with wifi-qcom-ac
The error does not occur with WinBox 3.41 64bit on Windows 11. I could not reproduce this error with Windows version of WinBox 4 beta 8.
I've just tried logging in using a MAC address with no problem using Winbox 4beta8 on Debian 12 (LMDE6), ROS v.7.15.3. Could be a bug: V4beta8 vs. Fedora?Thanks Mikrotik for building a Linux version of WinBox 4, but I getting the following error. "err: could not connect, Macconnection syn timeout"
This error occurs with mac address logins it does not seem to occur when the router has default config ip address.
Similar to what burnduck posted but I only got the error on Linux not Windows.
Computer Software: (WinBox 4 beta8 Linux version, Fedora 40 workstation)
Router: Mikrotik hAP ac2 RouterOS version 7.16 with wifi-qcom-ac
The error does not occur with WinBox 3.41 64bit on Windows 11. I could not reproduce this error with Windows version of WinBox 4 beta 8.
Honestly, you made me laugh. I've been around computers for 36 years. And I can't think of a “great many” programs, where windows are closed with the ESC key.For DECADES (more than 40 years), ESC has been the standard for closing/dimissing dialogs in the PC world.
CGGXANNX Sorry what? Which programs close with ESC in Windows? It has been CTRL+W and CMD+W in all software I know. Winbox was the exception.
I have this same issue using the beta Winbox 4 on macOS where it seems unable to determine which adapter to use to make the connection. I can connect to the default route but it will not allow any connections to any other devices other than the default route.Not sure if this is a 7.16 or Winbox 4 Beta 8 issue, since I just got this device today and immediately updated it to 7.16.
That is COMPLETELY different. Cancel is not same as Exit or Close. Winbox has no cancel buttons. It is an application. Try to close Chrome, Notepad or Photoshop! CTRL+WCGGXANNX Sorry what? Which programs close with ESC in Windows? It has been CTRL+W and CMD+W in all software I know. Winbox was the exception.
Almost every dialog in Windows??? Press Win+R to use the Run dialog and ESC close it??? Everything with a Cancel button
That is COMPLETELY different. Cancel is not same as Exit or Close. Winbox has no cancel buttons. It is an application. Try to close Chrome, Notepad or Photoshop! CTRL+W
Almost every dialog in Windows??? Press Win+R to use the Run dialog and ESC close it??? Everything with a Cancel button
Cancel is for prompts, not apps!
That is COMPLETELY different. Cancel is not same as Exit or Close. Winbox has no cancel buttons. It is an application. Try to close Chrome, Notepad or Photoshop! CTRL+W
Almost every dialog in Windows??? Press Win+R to use the Run dialog and ESC close it??? Everything with a Cancel button
Cancel is for prompts, not apps!
Sure, CGGXANNX, we will add escape to cancel prompts, just like in Windows. But not closing tables and other windows. It is your suggestion to follow "Operating System's guidelines". OK?
That is absolutely correct. I was just meaning that Ctrl+D should close the terminal window after disconnecting the session - not that terminal window should always close after session disconnection.NOT if the session is closed from other reason than ctrl+D
@CGGXANNX you are wasting keyboard strokes. They don't care about usability. It's obvious from their stance on not bringing back 20+ year old established winbox functionality.
ESC should work exactly the same as in winbox3.
In fact, all keyboard shortcuts should stay the same as in winbox3.
I don't buy any excuse about terminal or anything else. That how it has been working for years and years and that's how it should stay.
It's like Photoshop changing every single keyboard shortcut, because Adobe decided that 40 years ago they implemented them wrong and now they got it right. It's complete BS. Winbox is a tool. No matter what baggage it brings it must stay usable and facilitate doing things as fast as possible. Changing everything (or removing stuff) for the sake of looks and "change" is stupid.
LOL, I think Mikrotik tries to "copy" behaviour from MacOS a lot (but done sloppily). Ever since using MacOS (starting in 2015 or so) it always made me shaking my head that CTRL+D does not close the "Terminal" window. I am used to how it URXVT does on Linux -> CTRL+D closes the whole terminal window.That is absolutely correct. I was just meaning that Ctrl+D should close the terminal window after disconnecting the session - not that terminal window should always close after session disconnection.NOT if the session is closed from other reason than ctrl+D
Except CTRL+D technically closes the TTY session ... but whether a closed TTY close a window in desktop is up to the window manager "xterm"-like app does. e.g. In MacOS terminal, the window remains after a CTRL+D.CTRL+D closes the whole terminal window.
There is a Terminal option for that...Ever since using MacOS (starting in 2015 or so) it always made me shaking my head that CTRL+D does not close the "Terminal" window. I am used to how it URXVT does on Linux -> CTRL+D closes the whole terminal window.
This PR is in. WinBox 4 is now on Flathub: https://flathub.org/apps/com.mikrotik.WinBoxThere's one already waiting in Flathub queue: https://github.com/flathub/flathub/pull/5588I am a strong flatpak supporter, but my vote still is for a solution that is independent from the way of distribution.
Creating a flatpak manifest around a statically compiled binary as it is now is no problem at all. I would even offer myself to do that, I already maintain a flatpak wrapping for another precompiled application.
Edit: Here you go, I created a working flatpak manifest: https://github.com/mkfrey/com.mikrotik.WinBox
I vote this as well.Can you add the group & note back in select from saved?
It's more user-friendly to sort items when we have too many saved sessions.
2024-09-26_17-01-23.png
It has been like that even before 2015 if my memory serves me right. It forced to get iTerm where you can specifically adjust this behaviour.LOL, I think Mikrotik tries to "copy" behaviour from MacOS a lot (but done sloppily). Ever since using MacOS (starting in 2015 or so) it always made me shaking my head that CTRL+D does not close the "Terminal" window. I am used to how it URXVT does on Linux -> CTRL+D closes the whole terminal window.
That option closes the terminal window, but not the app. iTerm is able to close the app, when there's no open sessions left - Terminal does not have this option.There is a Terminal option for that...Ever since using MacOS (starting in 2015 or so) it always made me shaking my head that CTRL+D does not close the "Terminal" window. I am used to how it URXVT does on Linux -> CTRL+D closes the whole terminal window.
mac-terminal.png
winbox USERNAME reconnected after 1m45s from 192.168.88.2
OS / version give more clues... Did it work in previous beta before?i have an issue with winbox 4vb8... i can not start winbox. I see it in the processes but the windows of winbox is not starting.. any hints/tipps?
No, it has never worked... winbox4 never worked.. 3.xx is working.. .it is windows10, 22H2 Version...OS / version give more clues... Did it work in previous beta before?i have an issue with winbox 4vb8... i can not start winbox. I see it in the processes but the windows of winbox is not starting.. any hints/tipps?
First, thank you for being the only one so far to even attempt to provide this explanation lucidly for MacOS. But I still can't get it to work, even using the exact name provided (I tried both Addresses.cbd and addresses.cbd). "Saved" still shows nothing.To import an existing adresses.cbd on MAC OS you have to put addresses.cbd (or a link to it) here:
/Users/<user>/Library/Application Support/MikroTik/WinBox
EDIT: I was able top make it run (but please support Wayland natively) withbecause QT_QPA_PLATFORM was wayland.Code: Select allQT_QPA_PLATFORM=xcb ./WinBox
env --unset=QT_QPA_PLATFORM ./WinBox
On .desktop file topic for Debian/Ubuntu... some SVG version of the WinBox icon be nice (winbox.svg). That allow `/usr/share/icons/hicolor/scalable/apps` to be used and keep the icon "pretty".That would help to create a versatile desktop file.
I was able to import my addresses from winbox3 to Winbox4 without issue on MacOS. You have to drop your Winbox3 address export file to the /Users/<user>/Library/Application Support/MikroTik/WinBox directory, and overwrite the exisiting Addresses.cdb fileFirst, thank you for being the only one so far to even attempt to provide this explanation lucidly for MacOS. But I still can't get it to work, even using the exact name provided (I tried both Addresses.cbd and addresses.cbd). "Saved" still shows nothing.To import an existing adresses.cbd on MAC OS you have to put addresses.cbd (or a link to it) here:
/Users/<user>/Library/Application Support/MikroTik/WinBox
"Instructions" in pinned comment #1 are not even a command line, just a statement of a directory name in two different syntaxes. It needs to be replaced with a sentence explaining what is required.
What's the first thing you want to do to test out a new Winbox? Suck your current address/password file into it so you can give it a spin. The beta has no such native capacity, and the temporary writearound instructions provided aren't enough to get you running. If I have to beat my head against the wall just to get to step 1, I think I'll wait until the smoke clears to try this beta again.
Nice! Two questions...This PR is in. WinBox 4 is now on Flathub: https://flathub.org/apps/com.mikrotik.WinBox
+1000 from me!Agreed
@CGGXANNX you are wasting keyboard strokes. They don't care about usability. It's obvious from their stance on not bringing back 20+ year old established winbox functionality.
ESC should work exactly the same as in winbox3.
In fact, all keyboard shortcuts should stay the same as in winbox3.
I don't buy any excuse about terminal or anything else. That how it has been working for years and years and that's how it should stay.
It's like Photoshop changing every single keyboard shortcut, because Adobe decided that 40 years ago they implemented them wrong and now they got it right. It's complete BS. Winbox is a tool. No matter what baggage it brings it must stay usable and facilitate doing things as fast as possible. Changing everything (or removing stuff) for the sake of looks and "change" is stupid.
LibreOffice even the latest version can still run on Windows 7. Just an example of large and complex software where this was still possible. Is this really so difficult? I now have Windows 10 on one machine but I don't like it. If there is no other way, will rather migrate the old but still usable machines from Win7 to Debian instead. Please reconsider.Yes, Windows 7 was released in 2009, which is 15 years ago. To run WinBox 4 you need Windows 10.
@Miktrotik, please DO NOT reconsider this: don't waste your efforts to support OSes that reached their EOL. Please use your resources to improve your products.LibreOffice even the latest version can still run on Windows 7. Just an example of large and complex software where this was still possible. Is this really so difficult? I now have Windows 10 on one machine but I don't like it. If there is no other way, will rather migrate the old but still usable machines from Win7 to Debian instead. Please reconsider.Yes, Windows 7 was released in 2009, which is 15 years ago. To run WinBox 4 you need Windows 10.
There are new users, too. If changes are motivated with better compliance with a widely-accepted way-of-doing, then Mikrotik please go ahead with the changes.@CGGXANNX you are wasting keyboard strokes. They don't care about usability. It's obvious from their stance on not bringing back 20+ year old established winbox functionality.
ESC should work exactly the same as in winbox3.
In fact, all keyboard shortcuts should stay the same as in winbox3.
I don't buy any excuse about terminal or anything else. That how it has been working for years and years and that's how it should stay.
It's like Photoshop changing every single keyboard shortcut, because Adobe decided that 40 years ago they implemented them wrong and now they got it right. It's complete BS. Winbox is a tool. No matter what baggage it brings it must stay usable and facilitate doing things as fast as possible. Changing everything (or removing stuff) for the sake of looks and "change" is stupid.
This means that beta releases of Winbox should not be used to manage remote devices/systems. This is not a first case where system settins get inadvertently broken and some of them are even reproducible.Abandoning Winbox 4 for now until a stable is released. I issued a command to delete an address list, that is dynamic, but instead it deleted almost every single address, including statics, in the address-list. Not just the specific "z-blocklist_FireHOL_L1" list, but all of them, even named differently . Crashed my network due to the advanced FW. Good thing the router does automatic daily backups. Oof
Thanks for the work so far, looking great.
ROS6 with large routing tables comes up with an empty route list
Winbox 4
Screenshot_20240913_132856.png
Winbox 3
Screenshot_20240913_133032.png
Kind regards
Add `Ctrl-W` shortcut in winbox3 for consistency.Sure, CGGXANNX, we will add escape to cancel prompts, just like in Windows. But not closing tables and other windows. It is your suggestion to follow "Operating System's guidelines". OK?
This means that beta releases of Winbox should not be used to manage remote devices/systems. This is not a first case where system settins get inadvertently broken and some of them are even reproducible.Abandoning Winbox 4 for now until a stable is released. I issued a command to delete an address list, that is dynamic, but instead it deleted almost every single address, including statics, in the address-list. Not just the specific "z-blocklist_FireHOL_L1" list, but all of them, even named differently . Crashed my network due to the advanced FW. Good thing the router does automatic daily backups. Oof
Hold on. If you enter a command into the Terminal, it's the CLI that deleted those things, not poor WinBox! WinBox4 is just running a terminal session for you. It's the find command that not doing what you expect, and may be a different problem. Winbox3 would do same here, since it's just running same terminal to RouterOS shell.This means that beta releases of Winbox should not be used to manage remote devices/systems.Abandoning Winbox 4 [...] I issued a command to delete an address list, [...] Command:Code: Select all/ip firewall address-list remove [find list=z-blocklist_FireHOL_L1 dynamic=yes]
Feature request - resolve DNS name in ALL fields that require an IP or IPv6 addressGood grief! Who memorizes ip's?