please apply same zoom level of first window (which ask for ip password of mikrotik device) to second window(router os configuration window).
Feature Request: commandline connection to RoMON to see its RoMON Neighbors
something like
winbox.exe --romon “”
should result in showing the RoMON neighbours of from where further connections could be made.
Very useful as tool in The Dude…
Or maybe something like “RoMON” underneath “new WinBox” to connect to RoMON of the current session if RoMON is enabled?
Thank you.
I’ve been struggling with this too - in the end, I’ve used directory junction to redirect the %APPDATA%\Mikrotik to an encrypted VeraCrypt drive (which is represented by one big file, used also for storing the web browser cache and other potentially sensitive data). So far, seems like the best solution for me - for the machines, where the whole sysdrive is not encrypted by BitLocker or similar
This is normally not an issue because usually on Windows 10 systems the %APPDATA% directory is encrypted by Bitlocker even when the entire system drive is not.
I’ve just noticed that winbox is showing me only the first 68 rows of /ip/firewall/mangle on opening.
As soon as I select some subchain (other than ‘all’) and get back to ‘all’, it shows me all the lines (106 rows).
Yes, I’m using session templates but even of I select a new one (‘own’ new one) it shows me only 68 rows.
Using ‘none’ as session, it shows 69 rows, I’m a little bit confused.
Also switching to other tab (filter, nat) and then getting back to mangle, it seems to fix the rows number issue.
Anyone noticed a similar behaviour or am I just getting mad ?
What RouterOS version are you running?
Is that only for mangle rules? I do not have that many so I cannot quickly test, but I have 246 filter rules (the first tab) and they are all loaded.
(I usually select a chain filter to limit the amount of screen update processing)
Winbox is the latest 3.37, RouterOS is 7.7rc3 .
I’m pretty sure the issue was also present on previous 7.7rcX, but I suspect it was not there on 7.6 but I could be wrong and I need to find a way to check.
I don’t remember seeing that on the filter tab, in mangle it’s consistent every time I open a new connection and I display the mangle tab (first time).
I’ve just did a new check and also the NAT tab suffers the same issue (truncated at line 34 of 50 rows), switching the focus to mangle and back to nat and all rows are displayed.
The filter tab seems to be unaffected.
It’s just a cosmetic thing, but it’s annoying.
I have post about it post number #35 http://forum.mikrotik.com/t/winbox-v3-37-released/159534/1 … yeah it’s annoying
Ok but is it a prerequisite to have RouterOS v7? I manage several routers with very complex firewall setups but they are all running v6.49 (due to broken BGP in v7) and there I see no such issue.
My test routers running v7 have shorter firewalls, but I could experiment with one (load up a long dummy list of rules).
Sure @pe1chl, I’ve plenty of RouterOS v.6 as well and this issue in not present.
In practice, I play around with RouterOS v.7 only in my Lab (just few rare exceptions where I can’t help myself).
Thanks @rumahnetmks for confirming the issue (I see you wrote it was present since winbox 3.35).
@bajodel, I have installed v7.7stable and this bug is not happen anymore. Can you confirm?
I try reboot my router and usually it can reproduce the bug, but it seems not happen anymore.
EDIT :
Somehow the bug happen again. CONFUSE
@rumahnetmks - nope, still happening here
There are some cases where inexplicable Winbox behavior is caused by a corrupt session file.
You can try to make a connection with a new session file and check if it still occurs.
(this is the .viw file in the roaming profile directory)
you’re right, in fact I’ve already tried also with a blank new profile w/o success.
Feature request: make filters work (as much as possible within the limitations of the API) on the router side, rather than on the winbox side.
E.g. when I show IP->Routes with filter “Active is yes”, send the query with “?active=true” to the router, rather than fetching all routes and showing only those that are active.
In my case the issue of not seeing all data from firewall tables (in my case it’s not limited to specific tab), when using Ros v7.x (I’m now on v7.7), is that on sections where there are lot of rows, Winbox does not show the lateral scrolling bar once I open a tab.
But if I switch to another tab and then come back to the other I wanted to see, then scroll bar is there and I can see all lines.
I have it with firewall/raw, but also address-list an so on with firewall menu.
It does not happen to me with /ip/route, even though the list is long enough. It appears more on the /ip/firewall that is multi-tab window and can get long even when opened in full screen.
I don’t think I can reproduce that. But maybe I don’t have enough rows, the correct RouterOS version, and/or I misunderstand the problem.
In any case, when you have such a problem, always try to connect without a session file to see if it can be reproduced with no- or fresh session file.
Ok, I will try later this evening and let you know, as I can always reproduce this problem with firewall tabs.
I have just tried again, but I get the same issue.
So I have connected to the router by setting winbox’s session to “none” (I guess it’s what you have asked to try), but when I open /ip/firewall/raw I don’t see scrolling bars, until when I switch to another tab and come back.
Same behaviour as when I use session.
However if I use session, and I exit winbox by pointing the same menu/tab where scrolling bar disappears, once I reconnect through winbox within the same session, this time when firewall/raw is opened I have scrolling bar and can see all rows.
So as long as I exit winbox leaving the affected menu/tab selected, next time I re-open it, scrolling bars are there, otherwise if I start from another menu sequence, once I re-connect and I go into that menu/tab, no more scrolling bar until when I cycle to another tab and come back to the same menu/tab.
[feature request]
WinBox Keyboard hotkey navigation
http://forum.mikrotik.com/t/feature-requests/41609/1528