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.
BUG? ā drop-drop file(s) fails with error message about disk space
(MacOS 15.0 / WinBox4 beta8)
My test router has a raid1/ volume with 50GBs free, but the root does have limited space. Upload the WinBox4 button, works fine. But when I drag a file from finder to a disk or directory under raid1/ā¦, I get an error message:
IDK the issue, but maybe itās trying to write it to the SAME path? Using that pathā¦would not work since only a starting path of raid1/ would have enough room. BUT⦠I did drop it only a specific directory/disk/area - and thatās what directory should be used āon dropā. Tried a few different places and other files, but all failed similarly.
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.
With an almost empty configuration, a minute or so after I have created an empty bridge on the device, Winbox 4.0beta8 would fail to connect to the device with a āMacConnection syn timeoutā error, though the old winbox continues to work with no issue.
[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.
These are the only key shortcuts that have been implemented in v4 so far.
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.
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.
burnduck posted āWith an almost empty configurationā which is similar my experience after hardware reset of router
What is āglobalā in this approach? For DECADES (more than 40 years), ESC has been the standard for closing/dimissing dialogs in the PC world. MikroTikās excuse that it clashes with the Terminal is BS. Just donāt enable it in terminal windows but keep it for all other dialogs.
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?
Very little down to nothing was done to UI coloring. Darker font in Light mode? Is that even noticeable? Why are comments so light? Almost not readable? Please, if not colors, then letās us set the tone. Still no ability to influence the row zebra coloring or have line row separators.
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.
Almost every dialog in Windows??? Press Win+R to use the Run dialog and ESC close it??? Everything with a Cancel button can be closed/dismissed by pressing ESC for 40 years. WinBox is not an operating system. Its windows and dialogs are not āProgramsā. Can you close the font dialog in Notepad with Ctrl+W??? Can you close the āOpen fileā dialog with Ctrl+W? Ctrl+W has only recently become the shortcut for closing tabs in browsers. In Windows, for decades, dialogs are closed with ESC. And for programs with floating sub-windows (like WinBox), the old term for it is MDI https://en.wikipedia.org/wiki/Multiple-document_interface, the standard shortcut to close the sub-windows (those that are not dialog and are without Cancel Button) has always been Ctrl+F4, not Ctrl+W. Alt+F4 closes the outer program, Ctrl+F4 closes the MDI windows. Even now in Web browsers like Edge or Firefox (I donāt install Chrome) Ctrl+F4 works perfectly as the shortcut to close the tabs. Having used Windows since over three decades, I always close my browser tabs with Ctrl+F4. Ctrl+W was really an imported foreign shortcut for the Windows world!
A well-behave program in the Windows world always supports closing dialog with a āCancelā button present by pressing ESC. And Ctrl+F4 is the standard shortcut for closing MDI sub windows (those that are not dialog (without OK/Cancel buttons)). See the list here please. https://www.winhelponline.com/blog/master-list-keyboard-shortcuts-windows-10/#w10general
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.
edit: updated from Winbox 4 beta 6 to 8 on macOS 15 and it is now working for me.
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
Sorry, but the fact that the label on the button says āCloseā doesnāt make that button behave any different than a āCancelā button on dialogs with āOK/Cancelā buttons or āSave/Cancelā button or āOpen/Cancelā, or āApply/Cancelā, or āConfirm/Dismissā button. There is one button on the dialog which, when pressed saves the changes/performs the action and closes the dialog. That button has ENTER as the standard shortcut. And there is one button which, when clicked, abandons all changes/stops the current action and closes the dialog. That button (like I said, the label can say different things, but itās a Cancel button) always reacts to ESC under Windows.
Like I wrote. The windows and dialogs in WinBox are not individual programs. You donāt close programs when you close them (and BTW the standard shortcut for closing program under Windows is Alt+F4). You close dialogs (those where you can edit the properties and either accept the changes or abandon the changes) with ESC, or you close the window with the tables like the interface table, those are MDI windows. Normally you close them with Ctrl+F4 under WIndows. And guess what, the trusty old WinBox 3 CLOSES THEM WITH CTRL+F4 TOO!!!
It looks like those who programmed WinBox 3 really had the knowledge on how to write a well behave program that adheres to the Operating Systemās guidelines.
Letās look at this brand new interface in Windows 11 to edit the IP settings. Should be similar to when we edit an IP ā Address entry in WinBox, right?
What shortcut do I use if I donāt like the changes and want to close this. Hint itās not Ctrl+W