What's new in v3.32:

*) added "Auto Reconnect" feature;
*) added fast selection of column checkboxes in "Columns" window by simply typing column name without spaces;
*) added support for "Tools->Telnet/SSH" extra parameters;
*) alert if there was error executing "Cancel" action;
*) fixed MAC connection in new window;
*) fixed WinBox when started by Windows "runas" tool with different user;
*) fixed crash on "Netwatch" entry "host" field;
*) fixed crash when table window was closed before its "Columns" window;
*) fixed delayed session window open with "Change Password Now" prompt;
*) fixed filter type "contains" for network fields;
*) fixed focus marker in checkboxes;
*) fixed graphs with values higher than 2^31;
*) fixed large text paste in "Terminal" window;
*) fixed some fields with empty IPv6 value;
*) fixed tables with max entry count feature;
*) fixed time value fields in "Scheduler" menu;
*) keep terminal lines intact when resizing "Terminal" window;
*) properly show all fields which depend on other field;
*) release "Safe Mode" with info message, when other user took it;
*) restore "Managed" table when toggling "Advanced" mode;
*) sort "Columns" window alphabetically;
*) use router's time in graphs;
*) use router's time in last link up/down fields;

If you experience version related issues, then please report them to support@mikrotik.com.

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

please fix...

• the date in files-cloud backup it is not shown with correct timezone.

• double click to connect in winbox tab neighbours and romon neighbours

• an option to export or copy to notepad selected rules in winbox windows. eg when in tab firewall-filter right click to copy/export to rsc selected rules.

Many thanks for the update and I am looking forward to past many large scripts into Terminal at normal speed.

Nice!! I have updated mine and works well!!! I use a MacOS and even it works via Wine it will be very nice to get a native MacOS version (also Linux!)

Nice!! I have updated mine and works well!!! I use a MacOS and even it works via Wine it will be very nice to get a native MacOS version (also Linux!)

+1

Half of Mikrotik staff using MacOS and Linux, and yet is there still only Windows version, I don't get it, I don't get it at all...

Half of Mikrotik staff using MacOS and Linux, and yet is there still only Windows version, I don't get it, I don't get it at all...

Because it would require a full re-write, for something that works perfectly fine in WINE, also offering WebFig which is OS independent GUI.
If they ever got to a point where they have more developers than work required on RouterOS then maybe they'd commit some resources to a full winbox rewrite but right now it'd be a waste of time and money.

This seems to fix the Wireguard issue where adding allowed-addresses as ::/0 will disappear if done through Winbox.

Thanks for the update!

Routing-Table Box for IPv6 routes is still missing in Winbox GUI, so route has to be completed or added via console when using different routing table.

This seems to fix the Wireguard issue where adding allowed-addresses as ::/0 will disappear if done through Winbox.

Can confirm this to be working now, too.

Regards @colinardo

maybe they'd commit some resources to a full winbox rewrite but right now it'd be a waste of time and money.

This rewrite is overdue for over 10 years. It did not happen until now - so it wont ever happen.

Thank you for the update. I still have the following problems (7.1 on CHR):

• IPv6 route add - routing table selection not available in Winbox, so this has to be done from the command line

• Packet sniffer - Old packet list not erased when new sniff started

• Packet sniffer - Source and destination addresses and ports not populated

Nicholas.

maybe they'd commit some resources to a full winbox rewrite but right now it'd be a waste of time and money.

This rewrite is overdue for over 10 years. It did not happen until now - so it wont ever happen.

I don't recall MikroTik promised anything or any time frame and for most users the Windows version is perfectly usable as it is even on Linux therefore it doesn't seem to be a priority so how can it be overdue?

Because it has a lot of bugs. Most of them reported long ago. Winbox is either a developer Nightmare or MT is not interested in fixing.

*) added "Auto Reconnect" feature;

That is nice. Even better would be when it could do this without destroying the window, going back to the new connection window, and then setting up a new window for the connection.
E.g. by handling everything using messages in the button bar.

Reason: when using a "desktop pager" under Linux (does that even exist under Windows? I cannot live without it...) the newly created window appears on the desktop that currently has the focus, instead of the desktop where it originally existed.

• IPv6 route add - routing table selection not available in Winbox, so this has to be done from the command line

• Packet sniffer - Old packet list not erased when new sniff started

• Packet sniffer - Source and destination addresses and ports not populated

And to that I'll add:

• Torch doesn't show IPv6 traffic

Nicholas.

Before, the QuickSet page on a wireless link (e.g. LHG) showed the signal strength over time graph when the link is up.
This no longer works.

On Windows_7, Winbox 3.32 still crash on close.

I like the column search by typing the name and the auto reconnect feature as well...

*) added "Auto Reconnect" feature

Thank you for a long-awaited feature, Happy New Year!

Nice!! I have updated mine and works well!!! I use a MacOS and even it works via Wine it will be very nice to get a native MacOS version (also Linux!)

I used to think that, but it be better if they improved the iOS app and allowed it to run on Mac... I'll say it used to be more dicey with wine, but yeah since I've notice MT videos with Macs...wine with winbox has seem to work flawless for past year+.

Even the Tools > Check for Update works just fine on Mac (only found that around v3.2x something), so already on v3.32 - connected to a remote v7.2rc1 device via ZeroTier. I've been shocked that the "Check for Update" works now through few version upgrades with winbox on Mac – great work.

Before, the QuickSet page on a wireless link (e.g. LHG) showed the signal strength over time graph when the link is up.
This no longer works.

Similar issue with the LTE graphs on QuickSet screen:

Groove 52HPn and Groove 52ac set as CPE: Signal Strength Graph on Quick Set is not working when connected.

Hi;

Anyone experiencing problem for connecting the 72.rc1, because I have issue... it is not connecting..!!!!

Hi;

Anyone experiencing problem for connecting the 72.rc1, because I have issue... it is not connecting..!!!!

Yes, i've seen that too.
Go back to 7.1 or 7.1.1 using webfig.

Odd thing: android app works without a problem. Go figure !

Anyone experiencing problem for connecting the 72.rc1, because I have issue... it is not connecting..!!!!

I have a hAP ac2 with 7.2rc1 and I can connect it with WinBox 3.32 without problem (aside from the quickset display bug I reported above)

*) added fast selection of column checkboxes in "Columns" window by simply typing column name without spaces;
anyone can point me out,i can't see it

/ip web proxy access will not update to Deny, it will always revert back to allow, but when doing terminal export it will say Deny.

is this winbox bug?

Rearranging the Column order does not stay when closing and reopening. Normal? Hope not..

-tp

*) added "Auto Reconnect" feature; -- OH WOW!! finally! this is great, ive been hoping for this feature in winbox since 2006! now to test it / see it in action! - thanks MT for adding it!!

*) added fast selection of column checkboxes in "Columns" window by simply typing column name without spaces; -- Very nice!
*) added support for "Tools->Telnet/SSH" extra parameters; - another great addition.

Im very happy to see mikrotik (finally) putting some real effort and development into winbox over the past 12-18 months.

Winbox had unfortunately been neglected for far too long- especially as it is such a critical tool for managing rOS devices (and frankly, critical to mikrotik as a business).
Please keep up the development and focus on winbox. Winbox is such an excellent tool, and your more "power users" do appreciate and notice the recent development efforts on it! thank you!
(love mikrotik!)

EDIT: i saw this post from another user, and very much agree! this would be excellent if MT could improve auto-reconnect in this direction:

That is nice. Even better would be when it could do this without destroying the window, going back to the new connection window, and then setting up a new window for the connection.
E.g. by handling everything using messages in the button bar.

W0lt - the column order seems to stay for me, perhaps the session didn't save? What if you save it manually, are the columns ordered then?

W0lt - the column order seems to stay for me, perhaps the session didn't save? What if you save it manually, are the columns ordered then?

I cleared my cache and did as you asked. Seems to be working now.

Thanks

-tp

W0lt - the column order seems to stay for me, perhaps the session didn't save? What if you save it manually, are the columns ordered then?

I cleared my cache and did as you asked. Seems to be working now.

Thanks

-tp

Update, it appears to be doing it again. So I guess the problem is still there.😟

Loads Very Slow... Have to clear cache everytime to make it respond fast.

Support Team Kindly Note tha same and do the needful

*) added "Auto Reconnect" feature;

That is nice. Even better would be when it could do this without destroying the window, going back to the new connection window, and then setting up a new window for the connection.
E.g. by handling everything using messages in the button bar.

That would involve too much development effort. The reconnect dialog was already there. All they "added" was a way to trigger reconnect automatically.

Well, I think another improvement that could be made is to make the "connection dead" detection and parameters (e.g. timeout value) configurable.
So that a short network outage e.g. for WiFi reconnect or BGP rerouting does not immediately kill the connection.
It looks like it is now like 5 seconds by default, but it should be settable to e.g. 30 or 60 seconds. When winbox does not get an immediate reply it could show some warning but not disconnect until the connection is down for extended time.

agreed, this would be a very useful feature

Agree too... a configurable timeout would be a nice feature...

Agree too... a configurable timeout would be a nice feature...

+1

and native MacOS and Linux version....

Agree too... a configurable timeout would be a nice feature...

All for configurability. But not sure I understand this one: The session should return to where you left off in winbox, so waiting longer for it retry doesn't seem like something you'd want?

It does not return where you left off. Unless that has been fixed as well.
The "Autosave session on close" setting has, for anytime I tested that, not saved the session when it was lost due to an error. Only when you explicitly close it.
So when the session fails due to a timeout, all the work you have done before w.r.t. column configuration, window size setting, filter setting etc is all lost.
That makes me clicking "save" once in a while, but such things should not be necessary.

Also note the comment I made w.r.t. desktop pagers. When the session is lost and re-established, the window is on another desktop and has to be moved again. That would not be a problem when it does not get disconnected in the first place.

It does not return where you left off. Unless that has been fixed as well.

I have no idea if fixed... But I haven't seen it in v3.32. Kinda why I asked – curious if I was just lucky. ;)
I've seen sessions get lost, etc. for variety of reasons in prev. version, so it's an worry... But, v3.32 re-connect has, surprisingly, worked well – including column config. I actually expect my session to get lost, but hasn't :).

I also ask since I have seen the flip side with V7: winbox does not timeout at all(/long time)... e.g. make a bunch of changes that winbox accepts, but they didn't make it the router since connection was lost but since winbox didn't timeout.

And, I do think v3.32 seems to have hair-trigger for timeout now, so can see potentially need for it to timeout to be configuration. More saying it has work for me, so far...

"Lost sessions" seems like a bug...now a configurable timeout being a good to have if it happens.

Also note the comment I made w.r.t. desktop pagers. When the session is lost and re-established, the window is on another desktop and has to be moved again. That would not be a problem when it does not get disconnected in the first place.

Like this one seems like a bug too. I've seen this for long while, but re-connect make it worse I'd imagine. I use wine on Mac, so hard for me attribute winbox vs wine bugs – but it has work WAY better since @normis got a Mac.

Also note the comment I made w.r.t. desktop pagers. When the session is lost and re-established, the window is on another desktop and has to be moved again. That would not be a problem when it does not get disconnected in the first place.

Like this one seems like a bug too. I've seen this for long while, but re-connect make it worse I'd imagine. I use wine on Mac, so hard for me attribute winbox vs wine bugs – but it has work WAY better since @normis got a Mac.

I would not call it "a bug", it is just an unfortunate effect of using a desktop pager in a program that creates new windows. I see it happening in other
software as well. The desktop pager is implemented as part of the window manager, and AFAIK the application has no knowledge of it, certainly not
when it is running in an emulation program like wine. All new windows are always opened on the desktop that has the focus, so the only way an application
can work around this is by not creating new windows without user interaction, but re-using the existing ones (that the user already placed on the correct desktop).

Like this one seems like a bug too. I've seen this for long while, but re-connect make it worse I'd imagine. I use wine on Mac, so hard for me attribute winbox vs wine bugs – but it has work WAY better since @normis got a Mac.

The desktop pager is implemented as part of the window manager, and AFAIK the application has no knowledge of it, certainly not
when it is running in an emulation program like wine.

Been a long time, but apps should get a WM_DISPLAYCHANGE event message from windows (or even wine), so app could know about it. Since the desktop pager (Mac has one too) is mostly like having multiple monitors to apps, so thought it be similar.

Again not a huge issue for me, why I haven't reported/worried especially with wine's involvement... But does seem "modal" like System>Note, or the "New Winbox" button, sometimes use desktop that the winbox started on - even if you moved winbox to another "desktop" (as the pagers in Mac) or screen. I still haven't be able to nail down even what logic it's using to pick the desktop sometimes.

If an app doesn't support multiple desktops/monitors generally I see them stay on the same window. Which is actually Win32 SDK suggests should happen, but may not in all case:

Generally, older applications do not need changes to work on multiple monitor systems. For most, the system will appear to have only one display. System metrics reflect the primary display and fullscreen applications show up on the primary. The system handles minimization, maximization, menus, and dialog boxes.
However, some programs will have problems. Some that could have problems are remote control applications, those that have direct hardware access, and those that have patched the GDI or DISPLAY driver. In these cases, the user may be required to disable any monitor beyond the primary monitor.

Ok I have not studied the matter in Windows, where desktop pagers seem to exist only as an aftermarket addition which we do not have in our corporate environment (which is the only place where I see Windows).
In LInux, having a desktop pager certainly is not the same as having multiple displays. It is another layer. I have multiple displays on my Linux system where one display has a desktop pager and the other (which is actually my TV) has not. And moving windows from one display to the other is a completely different operation from moving them from one desktop to another.

Loads Very Slow... Have to clear cache everytime to make it respond fast.

Support Team Kindly Note tha same and do the needful

I see the same happening with this version.... I only have about 50 saved devices.

Has anyone seen that when running a ping/trace/torch from selecting an interface/ip/mac it starts with the stop button greyed out instead of the other way round. One has to press "start" an then "stop" for it to stop the action.

Has anyone seen that when running a ping/trace/torch from selecting an interface/ip/mac it starts with the stop button greyed out instead of the other way round. One has to press "start" an then "stop" for it to stop the action.

Aha, that's what seemed so odd about it !
Yes, seen that too.

This is not specific to this version od Winbox, also happens with older: with new version of Wine, Winbox cannot connect to router if option "Open In New Window" is checked.
I can't really tell what is "new Wine", because I don't really remember when the problems started, but only today I understood (at least I think so) that the problem is with wine, when I upgraded from Wine 6.0 (opensuse LEAP 15.3) to Wine 7.0rc3 (development) on my work PC. I have had this problem on my laptop (opensuse tumbleweed) for a few months, so it appeared with some Wine update between 6.0.1 and 6.23 - wide range, but that is all from second half of past year.
This is not urgent, but I find option "Open In New Window" very usefull, because I manage 200+ devices and often have to visit more than one from same group, so withou that option I have a few steps more each time I open new device.

MikroTik, pretty please, can next WinBox version fix Ctrl+Ins keyboard shortcut (copy to clipboard) in Terminal?

Current behaviour: Select text in Terminal, press Ctrl+Ins => nothing happens
Desired behaviour: Select text in Terminal, press Ctrl+Ins => text is copied to clipboard

It's standard shortcut that works everywhere in Windows, including other parts of WinBox, so there's no reason why it shouldn't work in Terminal.

Isn't that ctrl-c ?
Never used ctrl- ins in my life...

Ctrl x- cut
Ctrl c- copy
Ctrl v- paste

For as long as I can remember...

But in terminal Ctrl-c is terminate the currently running command. So bad idea to use it for copy.

True... so that's not following the standard either.

BTW ctrl ins is IMHO counter intuitive. Should be to put something, insert.
Not to get or copy ?

Idea: use PowerToys and remap keys as wanted.

But in terminal Ctrl-c is terminate the currently running command. So bad idea to use it for copy.

I beg to differ. Even Microsoft can get that right and keep those separated.

Update: I have to check my bug report on this. And what I remember is that if you past code into Terminal any comments are shown as selected text.

This should be better in this version 3.32 and I just did some coding again and had to press Enter twice sometimes before executing started.

Checking syntax is still a bit slow in 3.32

Isn't that ctrl-c ?
Never used ctrl- ins in my life...

That's blasphemy! Everyone knows that the only true clipboard shortcuts are Ctrl+Ins, Shift+Ins, Shift+Del. :) On serious note, there are two sets, this and probably more common Ctrl+C/V/X, they coexist for ages and work at the same time.

In any OS taking CLI seriously (beginning with ancient mainframes using teletype terminals), CTRL-c was always way to interrupt running command. It's still this way in Linux. When clipboard came around (with X window system), COPY was implicit ... whatever one marked using mouse was available for PASTE using middle mouse button (if mouse had 3 buttons) or both mouse buttons (otherwise). In recent years, some Linux variants invented use of CTRL-SWIFT-c/v while in CLI (where use of CTRL-c to interrupt running command is still sensible) while GUI apps keep using CTRL-c/v (but hey, why would one want to use keyboard shortcuts in GUI?). The original approach (implicit COPY) is used by mobaXterm (windows application which more or less packs cygwin and X server).

From the same period cursor movements were done using h,j,k,l ?
Been there, done that...

On any WINDOWS system I ALWAYS used ctrl c for copy.
Shortcut is normally determined by OS, not by application.
My view...

Terminal in WinBox currently seems to have dual-use Ctrl+C. It interrups e.g. running ping, but also copies selected text to clipboard. If you wonder what happens when you want to copy text from runninning ping, it works fine. If there's any selected text, copying has precedence. If not, it interrupts command. It also happens, if you try to copy same selection twice. Seems like good system to me.

But for fans of the other set of clipboard shorcuts, Ctrl+Ins should be added too (Shift+Ins already works), it doesn't conflict with anything, so it shouldn't be a problem.

Shortcut is normally determined by OS, not by application.

I'm with you on this, and that's exactly the reason, why Ctrl+Ins should work, because it's Windows standard (one of the two) and it works with all standard system controls.

In any OS taking CLI seriously (beginning with ancient mainframes using teletype terminals), CTRL-c was always way to interrupt running command.

The first computers I used with teletype terminals used BREAK to interrupt the running command. BREAK is not a character but a longish toggle of the serial line level.
My first microcomputer, the TRS-80, had a BREAK key as well, although of course it did not use a serial connection as it was all-in-one.
Other early Unix computers I used had the interrupt function tied to Delete (character 127).
The current PC keyboards have BREAK as a second function of the key labeled Pause. Like the other keys in that 3-key cluster, it is rarely used.
It seems that nowadays Ctrl-C is a common key for interrupting the running command, but it certainly has not always been that way.

Terminal in WinBox currently seems to have dual-use Ctrl+C. It interrups e.g. running ping, but also copies selected text to clipboard. If you wonder what happens when you want to copy text from runninning ping, it works fine. If there's any selected text, copying has precedence. If not, it interrupts command. It also happens, if you try to copy same selection twice. Seems like good system to me.

I'm with you on this, and that's exactly the reason, why Ctrl+Ins should work, because it's Windows standard (one of the two) and it works with all standard system controls.
[/quote]


Ahhhh there is this odd behaviour of selected/commented text having precedence coming from.

The problem is that comments are also seen as selected text and so make the CTL-C behave flaky.

I did always use Shift-Ins and Ctrl-Ins until I did get a HP computer without a dedicated ins key.
So now I do use Ctrl-c Ctrl-v
And after starting using Teams I have learned
Shift-Ctrl-V that is paste without format.

Isn't Ctrl+X in Terminal the only way to enable HotMode in v6? Looks like it's broken after WinBox v3.30...

Isn't Ctrl+X in Terminal the only way to enable HotMode in v6? Looks like it's broken after WinBox v3.30...

See https://wiki.mikrotik.com/wiki/Manual:C ... st_of_keys

Ctrl-X is SafeMode. HotMode or "Hotlock" was/is is Ctrl-V. I thought it was removed from V7, but @Chupaka right it's winbox where it doesn't work using Ctrl-V (F7 now). But Hotlock does work when you SSH in using Ctrl-V, so it's just the Winbox terminal where the Ctrl-V isn't taken.

Edited: another thread had this comment from Mikrotik:

HotLock mode hotkey has been changed too. Now it is F7 (Ctrl-V removed). Winbox Terminal still doesn't support Ctrl-V, though. You have to press Shift+Ins to paste. But at least now you won't accidentally activate HotLock mode while trying to paste.

Are those types of changes documented somewhere?

https://help.mikrotik.com/docs/display/ ... ListofKeys

Yeah, sorry, I meant Ctrl+V for Hotlock. The hotkey was changed for v7 only, so it doesn't work in v6 with recent versions of WinBox.

I'm still seeing some issues with saving the column selections. In some cases a newly added column will not "stick" in the saved session.
I can reproduce this e.g. for the "Used Hold Time" column in Routing->BGP->Peers. It is gone every time I open this window and its width is set to the default when I re-add it.

*) sort "Columns" window alphabetically;

Well, sometimes that is an improvement, sometimes it isn't. In long lists, the original unsorted listing tended to group them by function and this is gone now that they are alphabetically listed.
Also, the same name sometimes appears twice (a longstanding bug) but in the old situation one could differentiate e.g. the setting value and the active value by the position in the list. That no longer works.
It would be nice when the sorting can somehow be made optional (either by global setting or a checkmark in the dialog itself).

*) fixed graphs with values higher than 2^31;

Graphings with high values now displays correctly, but when you click on a specific column the current label value is wrong


In this example the label at the right should be around 5000Mb instead of 1750Mb

WinBox v3.33 released:

viewtopic.php?t=183119