also here, ccr1016, rb2011 and ccr1009 all shows NO log entries, same applies to files content.File window is empty, too.
Many thanks for a super quick response! All my issues are now gone!What's new in v3.27:
*) fixed content drawing of read-only tables (introduced in v3.26);
CCR1009, rb2011 same problem, but CCR1036 - only file list emptyalso here, ccr1016, rb2011 and ccr1009 all shows NO log entries, same applies to files content.File window is empty, too.
Thanks for a VERY rapid and successfully upgrade.What's new in v3.27:
*) fixed content drawing of read-only tables (introduced in v3.26);
Good grief, do you not check for updates at least twice daily??Good grief, I just downloaded 3.25 yesterday..
Anyway with 3.27 (64 bit version), file list and log are working on my RB750Gr3 and RB750r2.
I know you are largely just being funny anav...Good grief, do you not check for updates at least twice daily??Good grief, I just downloaded 3.25 yesterday..
Anyway with 3.27 (64 bit version), file list and log are working on my RB750Gr3 and RB750r2.
I did not try that version at first (because I did not install 3.26) but now I got a message from OskarsK asking if it fixes the column/rule dragging problem, and indeed it seems that this issue is now resolved! (I cannot reproduce it)What's new in v3.27:
*) fixed content drawing of read-only tables (introduced in v3.26);
It hasn't resolved on my end.I did not try that version at first (because I did not install 3.26) but now I got a message from OskarsK asking if it fixes the column/rule dragging problem, and indeed it seems that this issue is now resolved! (I cannot reproduce it)What's new in v3.27:
*) fixed content drawing of read-only tables (introduced in v3.26);
So others can try as well to see if this version works for them.
Thanks Oskars!
Hmm now that I try again after it has been open for some time, the problem indeed is still there!It hasn't resolved on my end.
Both on Windows 7 64bit & Windows 10 64bit.
I was not aware that the Router OS produced a 1/2 line or 1/4 line or 3/4 line? ;-PPAnother issue that I see now I use 3.27 for a while (but I think it has been introduced in 3.22 or later):
When the log window is displayed, and the number of lines in the window is not a whole number, new log lines at the bottom are not readable.
They become readable when the window is scrolled down manually (a line fragment that is blank appears below the last line).
Please make the log window scroll to that position automatically.
I had that also for a long time. On checking I see that it now shows the whole line and a partly blank line under that. So with me this partly showing and scrolling to see the last line, is solved.Another issue that I see now I use 3.27 for a while (but I think it has been introduced in 3.22 or later):
When the log window is displayed, and the number of lines in the window is not a whole number, new log lines at the bottom are not readable.
They become readable when the window is scrolled down manually (a line fragment that is blank appears below the last line).
Please make the log window scroll to that position automatically.
Maybe it has to do with the changed line spacing in the log window causing my existing window size to be no multiple of a line height anymore...This issue (autoscroll hiding the last line) actually exists since forever. If you run ping and resize the window a little bit, you can make it hide the last line, just the way you see it now in the log window.
It all has to do with the correct window size for autoscroll to work properly.
What's new in v3.27:
*) fixed content drawing of read-only tables (introduced in v3.26);
It may worked like this in previous versions, but with 3.27 it opens up nothing.Session > new, opens up a new session, and will not save upon exit if it's not done manually.
osc86 is probably confused what a "session" is and expected that a new session means a new connection (so the same as the New WinBox button).Session > new, opens up a new session, and will not save upon exit if it's not done manually.
No a session is not a connection! A session is the winbox term for a saved set of UI settings (like open windows, selected columns, column width, etc)It should open a new winbox window where you can select a new session.
Press F5 in packet window.You have have to stop the capture for them to fully display all columns of info.
The other day I was using Winbox on a colleague's PC and I noticed that there it didn't exhibit this behavior.Firewall and Bridge Filter rules lists are still misbehaving. As long as a rule detail window is open, the list itself will not let you drag and drop rules properly. When you're dragging a rule, it jumps to the very bottom of the list every second (on each window refresh). It seems to only happen when a rule is opened somewhere, at least for me.
I'm writing "still" because I've read this problem somewhere else already a while ago and it doesn't seem to be new with v3.27.
This behavior is quite dangerous, as some accept rule might "slip" below a drop rule and you lose connection to the router, so that you can't take it back.
I think that is roughly correct. It's definitely load-dependent in some way. My simpler setups don't have this at all. The biggest ones do, as soon as many windows are open with a lot of updates going on and also a rule details window. Then it starts jumping. Still not 100% reliably though.- a table with quite some entries (firewall with > 200 rules, large connection table)
- frequent updates (busy router where counters in the firewall or connection table are updating all the time)
- holding down mouse button long enough so that updates come in that have to be displayed
I used Kazam and I ran into the problem that when trying to demo it with column-width dragging the framerate was too low and most of the jumps were not showing in the captured video...Might make a capture myself in the next days, if I can make time and get some decent software for that.
Thanks for explaining how that happens! It has happened many times to me that winbox crashed when I closed and re-opened a window, but it never occurred to me that the save of the session (which I irregularly do because of the lack of a "save on disconnect" flag) is the thing that triggers it!Bug(?) (3.15 -> current): make any changes to an opened window (just moving it is enough) save session, close that window to which you've made changes. try to open that window again -> winbox session crashes.
0 is not a valid value to be set as VLAN ID for any interface (neither is 4095), it is only valid in 802.1q tag where only priority flags are set. So indeed there should be some easy way to set 802.1q priorities ...Also note that VLAN 0 is still rejected in v7 even though that is a valid value. ....
When VLAN 0 is not going to be implemented there should be some flag that allows you to push an 802.1q tag with the current priority e.g. as an interface- or port setting.
Works on MacOS, for example :)8) make WinBox update work with wine 5.0 or more current;
Yes it does. I just tested both switches and it works. This is from latest winbox v3.27 (unfortunately it does not show the version in the open window)The latest Winbox versions do not save settings such as "Inline comments" and "Hide Passwords".
Please, support higher resolutions than 192dpi. The maximum zoom size is still way too small for some monitors.*) support Ctrl++ & Ctrl+- on keypad for quick access to Zoom In/Zoom Out;
Yeah, just double-click it - it will be opened in separate window :Dam i missing something maybe?
On scripts, I don't remember where, if you hover with the mouse pointer and it will open a box with a yellow background displaying the whole content of that script. That could be implemented also for the log and will trigger if the line is longer than the box displaying it.That will still have one long line, but at least you can drag that window until you see it all. So it's a way, but definitely not good way, just slighly better than nothing. It would be best to optionally support both horizontal scrolling and line wrapping.
I'll second that one !!!Feature request: please save the settings of the Torch window (entry timeout, collect checkmarks, filters) in the saved session so it comes up with previous settings when re-opened.
In Terminal you can also display the log and long lines are then a bit easier to read:I understand that as of a few winbox versions ago , the entries in the log window were truncated to not take up more than a single line (and there were some users requesting this). however im not clear on how this is a better solution than the prior multi line log window entries (where you could always read the full log message).
perhaps a happy medium would be to add a horizontal scroll bar to the log window (and the ability to extend the column for MSG to length=(length of longest log entry))
IE i was on a 1080p display laptop trying to troubleshoot an issue, however i was unable to read this log entry (ie no way to read all of it, as i cant expand the column beyond the window, and i cant expand the window beyond the max res of winbox/monitor):
am i missing something maybe?
thanks
/log print where time~"nov/18 08:53:06"
I just tried it. No success... still not working.Hi!
Any updates regarding native winbox for Macos and M1 (ARM) core?
Thanks.
That is possible, I am still running version 3.21 (anything after that does not work for me due to issues when mouse button is held down) and it works OK in 3.21.This bug has appeared since approximately version 3.25Was Winbox designed to dock the child window to the main window (when maximized)? Or has this behavior changes in recent version?
Perhaps this is not a bug but rather a suggestion or feature request.. better contact support.
Winbox 3.27 there is a modal window issue.
We have a main (modal) window in non-full-screen mode. The window inside it is in maximized mode "Pic1", after which we expand the main (modal) window to fill the entire screen and get "Pic2", when the internal window does not repeat the action of the external one.
Please fix this bug in the latest versions of Winbox.
That is the problem discussed in posting #22 and #24-#26 of this topic, and other release topics since WinBox 3.22 (where this problem was introduced).recently found that on one CCR (latest long-term ROS) with lots of interfaces (meaning thousands) when we try to resize column sizes or re-sort bridge-filters winbox is actig out:
/ip ipsec mode-config set [find name=cfg1] address-prefix-length=19
That is the COPY button that is already there.I'd love to see "duplicate" command for firewall rules, to create similar rule. Especially useful if want to try something by copying old rule and then temporary disable old one. And when create several similar rules.
Oh my God! Thanks. I never tried to look for this button inside the rule window. I thought it must be in context menu, or copy by Ctrl+Move or Alt+Move, or Ctrl+C and Ctrl+V and so on.That is the COPY button that is already there.I'd love to see "duplicate" command for firewall rules, to create similar rule. Especially useful if want to try something by copying old rule and then temporary disable old one. And when create several similar rules.
how do i access that radius server at my home bcoz when i bought a plan from them they were managing through there mobile...They're provisioning everything on their RADIUS server ...
PLEASE GO AWAY HERE!! IT IS NOT APPRECIATED THAT YOU DUMP YOUR UNRELATED QUESTIONS IN OTHER TOPICS!
Yes, I have noticed the same problem too.When I close session with Dude Settings window opened, then IP Settings window is opened after relogin to WinBOX.