That has different cause and Winbox is correct here. It will be fixed when the Mikrotik software server is fixed/updated.New Winbox shows strange changelog in "system -> packages" for stable tree ??!?!?!?
The error comes after "clear cache" only on the first device you connect after downloading descriptors. On other devices the changelog is OK. It stays strange only on the first connected device after performing a "clear cache" .....
Unbenannt.PNG
What if you enforce it to use only one of the two servers under the domain dowload.mikrotik.com? Round Robin behaviour of DNS could be causing that.No sorry....it is every 2nd time you connect
connect rb4011 .... changelog OK ... closing winbox .... connect rb4011 .... changelog NOT OK .... closing winbox .... connect rb4011 .... changelog OK .... and so on
Yes, the same hereHello
With Log window opened, minimize WinBox, then Restore. Log is always reverted to the beginning.
Anyone else seeing this?
Regards
Just tried it on several routers, but only see this behavior on a single device. A differentiating factor appears to be the number of records kept in the log. I see this on a device with 1000 record in the log buffer. And it is the actual number of rows that matter, as I have a CHR instance with the line limit set to 1000 but with only 120 records currently in the buffer, and I do not see this problem there.Yes, the same hereWith Log window opened, minimize WinBox, then Restore. Log is always reverted to the beginning.
Anyone else seeing this?
I tried to set limit to 990 lines, there are 927 lines currently. Nothing changes, log goes to beginning after window restore. BTW, it's RB1100AHx2, RouterOS 6.45.9.Just tried it on several routers, but only see this behavior on a single device. A differentiating factor appears to be the number of records kept in the log. I see this on a device with 1000 record in the log buffer. And it is the actual number of rows that matter, as I have a CHR instance with the line limit set to 1000 but with only 120 records currently in the buffer, and I do not see this problem there.Yes, the same hereWith Log window opened, minimize WinBox, then Restore. Log is always reverted to the beginning.
Anyone else seeing this?
Never experienced this problem, so now I went and tried it myself. Tested against several devices, result- cannot reproduce, everything works as expected for me.open a window like "IP firewall filters" in a router that is in active use, and make sure the hit-counts of firewall rules are being displayed (and changing all the time).
Now, position the mouse over a header separator and keep mouse button pressed to attempt to move the separator to set the column width appropriately.
Result -> column jumps to some default width at the same time the counters are updated. Dragging is ignored.
Similar problem occurs when you keep mouse button pressed over a filter line to drag it to some other place. Line jumps to wrong place, not the place you drag it to.
Sounds plausible. I run Winbox (64-bit) natively on Win10. And (simply out of curiosity) I have just tested 32-bit version, which also works fine for me.I am running winbox (32-bit) under wine on a Debian system.
Maybe it behaves differently on a native Windows system?
It would be interesting to hear if wine users on the Mac experience the same issue, and/or if other Linux users see it as well.Sounds plausible. I run Winbox (64-bit) natively on Win10. And (simply out of curiosity) I have just tested 32-bit version, which also works fine for me.I am running winbox (32-bit) under wine on a Debian system.
Maybe it behaves differently on a native Windows system?
Let me check that on macosIt would be interesting to hear if wine users on the Mac experience the same issue, and/or if other Linux users see it as well.Sounds plausible. I run Winbox (64-bit) natively on Win10. And (simply out of curiosity) I have just tested 32-bit version, which also works fine for me.I am running winbox (32-bit) under wine on a Debian system.
Maybe it behaves differently on a native Windows system?
Under Linux it could maybe depend on the window manager in use? (KDE/GNOME/XFCE etc)
Nope, macos catalina, wine64 (wine-5.7) and WinBox 3.24 - I can resize columns why they're updating all I like.Let me check that on macosIt would be interesting to hear if wine users on the Mac experience the same issue, and/or if other Linux users see it as well.Sounds plausible. I run Winbox (64-bit) natively on Win10. And (simply out of curiosity) I have just tested 32-bit version, which also works fine for me.I am running winbox (32-bit) under wine on a Debian system.
Maybe it behaves differently on a native Windows system?
Under Linux it could maybe depend on the window manager in use? (KDE/GNOME/XFCE etc)
Agree!I run winbox with my system set to a custom scaling of 121 the first time it shows big, then I close and reopen and then it shows small and then again big and again small, what's going on.
Can we please have a tick box to not follow system dpi settings or a parameter with which we can disable dpi scaling or else I'll be stuck to 3.20 which was fine for me
Edit: I noticed now the initial login window for Winbox still has font-cursor misalignment, but once in Winbox it's fine. WTF!?I wiped my .wine config and ended up with the old problem of the cursor and text being misaligned when running winbox on wine in fields of text to be edited, especially as the line grows longer. I had made some forgotten changes ages ago which fixed this but also turn off font smoothing - winbox looked perfectly fine without smoothed fonts and the cursor was always in the right place.
This old registry trick still works and you get to keep your smooth fonts, which is nice!
[HKEY_CURRENT_USER\Software\Wine\X11 Driver]
"ClientSideWithRender"="N"
Create a file test.reg with the key/text above, and on terminal:
regedit test.reg
This works with winbox 3.24, wine-stable 4.0.3~bionic and Linux Mint 19.3.
Yes, the sameYes, the same hereHello
With Log window opened, minimize WinBox, then Restore. Log is always reverted to the beginning.
Anyone else seeing this?
Regards
Ugh I made a typo - it was missing the REGEDIT4 which stopped the key being made in the registry. It should be below. The unsmoothed version of the fonts are displayed but there is now no longer a cursor problem any more.@UpRunTech
Thank you! I've been wondering how to do that.
Yes, true. Very annoying bug: even on any interface resize scale.I run winbox with my system set to a custom scaling of 121 the first time it shows big, then I close and reopen and then it shows small and then again big and again small, what's going on.
Can we please have a tick box to not follow system dpi settings or a parameter with which we can disable dpi scaling or else I'll be stuck to 3.20 which was fine for me
For me its not under tools, but under setting. You should name stuff the same on Windows/Macv3.24 has adjustable font size. in the loader, tools > zooom in
when zoomin...font too big.so uglyv3.24 has adjustable font size. in the loader, tools > zooom in
Screenshot 2020-06-11 at 11.25.32.png
I think it should not disconnect so quickly either... when there is a couple of seconds of network interruption, winbox immediately disconnects. SSH or telnet is alive.Feature Request:
Please add a AUTO-reconnect.
If we connect to IP:PORT then this should still reconnect when he detect that port of WinBox is alive again - this will be life change feature !
Agree, at mREMOTE NG they solve it in very good idea, they give you option what to do :)I think it should not disconnect so quickly either... when there is a couple of seconds of network interruption, winbox immediately disconnects. SSH or telnet is alive.
Winbox should keep connected like 30 or 60 seconds, maybe there should be a config option for it. So you can reboot a router somewhere in the network without losing all winbox sessions to routers further down.
There could be an icon that lights up in RED when it detects that the connection seems dead (no network traffic going for 2 seconds) but it should remain connected until the user decides to close the session or considerable time has elapsed.
Hmm, I thing my sestion are save but I notice long time ago that "red X" not save session. The Exit button save session infromation.So I need to remember to do Session->Save each time I change something. Annoying! It would be so much better when winbox would not close sessions merely because there is a small network hickup. SSH and Telnet don't do that either.
I'm not asking for "auto reconnect", I want "session persistence" until there is unreasonable outage of the network. And I want an "autosave on disconnect" option too.
Hi,Yes, when that "Autosave on Close" option is enabled the session is saved when you use Exit or you hit the X at the top right of the window.
That works fine.
However, when the session is closed because of a network failure OR because the connected router is rebooted (you use System->Reboot or upgrade the router with automatic reboot), the session is NOT saved. No matter how that option is set.
That is why I mention that another option for "Autosave on DIsconnect" would be helpful.
Yes, when that "Autosave on Close" option is enabled the session is saved when you use Exit or you hit the X at the top right of the window.
That works fine.
However, when the session is closed because of a network failure OR because the connected router is rebooted (you use System->Reboot or upgrade the router with automatic reboot), the session is NOT saved. No matter how that option is set.
That is why I mention that another option for "Autosave on DIsconnect" would be helpful.
I confirm the problem on Windows 7 64, using 64bit winbox.The problem with windows that have dynamic updates remains the same, I went back to 3.21 after 10 seconds of test...
Thanks! That saves me from testing on Windows machines. Strange that other people deny that they have a problem, maybe they don't understand what issue I mean?I confirm the problem on Windows 7 64, using 64bit winbox.The problem with windows that have dynamic updates remains the same, I went back to 3.21 after 10 seconds of test...
Probably.Strange that other people deny that they have a problem, maybe they don't understand what issue I mean?
I tried to reproduce the issue as per quote but it just does not occur.To reproduce: open a window like "IP firewall filters" in a router that is in active use, and make sure the hit-counts of firewall rules are being displayed (and changing all the time).
Now, position the mouse over a header separator and keep mouse button pressed to attempt to move the separator to set the column width appropriately.
Result -> column jumps to some default width at the same time the counters are updated. Dragging is ignored.
I am not denying that I have the problem. I really DON'T have the problem. On the other hand, I wouldn't deny that someone else may have the problem. It may not be that widespread as you think.Strange that other people deny that they have a problem
??? All resizing problems are still here. Within winbox and winbox itself...Finally . No more resizing of the windows is nice. Let me try it.
Not for me, all the crazy windows resizing was finally fixed for me in 3.24??? All resizing problems are still here. Within winbox and winbox itself...Finally . No more resizing of the windows is nice. Let me try it.
Problem still hare on 2k displays with interface resizing to 125-170%.Not for me, all the crazy windows resizing was finally fixed for me in 3.24??? All resizing problems are still here. Within winbox and winbox itself...Finally . No more resizing of the windows is nice. Let me try it.
I have 2K resolution with 100% scaling and its ok. So it must be scaling.Problem still hare on 2k displays with interface resizing to 125-170%.
Winbox itself and its inner windows has this problem too.
Hi,I have 2K resolution with 100% scaling and its ok. So it must be scaling.Problem still hare on 2k displays with interface resizing to 125-170%.
Winbox itself and its inner windows has this problem too.
YES! This is the most annoying thing EVER! I can't even use Winbox until I zoom in. There's not even a keyboard shortcut to zoom, so it has to be a bunch of clicks. ARGH. PLEASE FIX IT. You know what? I'm going to make a ticket.ARGGGG!! The default zoom level sucks! Why can't this setting be remembered? Win10 64bit w/ 4k monitor, tried 32 and 64 bit winbox, been like this for a few versions now. Have to manually zoom in twice to be able to read the text. Is there a solution?
A generic problem with winbox is that when you open some screen where there are lots of items and a lot of activity (e.g. a complex firewall rules page with updated counters or a page of active connections or address list items), both the link and the system are loaded with the update data. It would be useful when there would be some kind of "pause" button or a way to configure the update rate of such screens, so this can be managed a bit better.About the memory use, well, of course, if Winbox is displaying something, it will take up memory. I don't suggest use of Winbox for monitoring. It is a configuration tool, use SNMP for monitoring.
Thank you for feedback. Problem with HiRes appears on Microsoft Surface 4,5 with any resolution and any interface resize scale.Yes, zoom state is not saved between sessions, it's a bug, it will be fixed, but any other issues with HiRes displays is hard to reproduce, There is some kind of compatibility between external display and internal display, if different DPI is used. We have no issues on any of the testing computers with HiRes displays.
About the memory use, well, of course, if Winbox is displaying something, it will take up memory. I don't suggest use of Winbox for monitoring. It is a configuration tool, use SNMP for monitoring.
+1It would be useful when there would be some kind of "pause" button or a way to configure the update rate of such screens
Oh cmon.... there is clearly memory leak somewhere in winbox if it starts with 80MB and gets to 700MB in a day. It's understandable that some amount of memory should be consumed by graphs or something else that accumulates data over time, but amount of data required to see what's on the screen is pretty low...About the memory use, well, of course, if Winbox is displaying something, it will take up memory. I don't suggest use of Winbox for monitoring. It is a configuration tool, use SNMP for monitoring.
/ip firewall filter
add chain=in-olc dst-port=53 protocol=tcp src-address=192.168.0.31
add chain=in-olc dst-port=53 protocol=udp src-address=192.168.0.31
Check the Google Chrome memory usage, bet you that was used to monitor Cisco equipment :-)Winbox after a few days continuous connection to CCR2004 (it seems doesn't matter) with ROS 6.47.1. Used memory growed from 10 MB to 695.
winbox_memory.png
About the memory use, well, of course, if Winbox is displaying something, it will take up memory. I don't suggest use of Winbox for monitoring. It is a configuration tool, use SNMP for monitoring.
It is not work on a W10 LTSC En (1809) if Checking Open In New Window and User name in OS's have any symbols like backspace in Name. For any time opened - All resized to smaller. If Logon name like 1 words is Ok. I hope that it shall be fixed.Looks good and no more resizing of the windows on it's own is a big relieve. Running it on a Windows 10 system.