+1Why does Winbox v3.0rc12 have such bad MAC discovery of new devices (first boot of device with default configuration) on first screen neighbors?! It was not problem on v3.0rc6 (or9). I can see device in v2.2.18 but in v3.0rc12 I can't see that device.
+1So came to the client and tried to log into the CPE. Well, it didn't 'see' it. Not by mac and not by the IP part of the network the client uses for his network.
So, had to climb on the roof, take the CPE down, drive home, connected to my office network ready to reset the CPE....
But tried to 'see' it with the new winbox loader.... still no change. After 10 minutes still nothing...
So, tried the 'old' v.2.x version of winbox loader, and it sees it inmediately!
"verbatim copy", sorry for my ignorance, I'm not a techno wizz, but what do you mean with that?I wonder what is the problem to do verbatim copy of MAC discovery procedure from WinBox 2 to WinBox3 ?
He means, what is stopping the Winbox developers from just copying the discovery code from Winbox2, and pasting it into Winbox3?"verbatim copy", sorry for my ignorance, I'm not a techno wizz, but what do you mean with that?I wonder what is the problem to do verbatim copy of MAC discovery procedure from WinBox 2 to WinBox3 ?
@Hotz1 @BartoszP; Thanks for the explanation. Credits for that! And I do agree on both, upgrades should be guarded against loss of previous functionality and in case it still happened old versions should still be accessible as easy as the new one."Verbatim copy" means "byte by byte" or "bit by bit".
New discovery version ( this one used by WB3 ) could be default one but the WB2's version could/should be accessible from menu as alternative method to discover devices.
I needs the same!!! Add this future pls!Pleeeeeeeassse, added support portable!!! It's so easy to implement now!How can it know where you want it? Just set the folder once, and Winbox will remember it.i know that. i mean that it should choose by default the path that i am running winbox.exe.
if i have a folder on my flash drive in root ...\winbox everything should be placed there and not in %appdata%
Please check the configuration files in folder winbox.exe.
If found file config in winbox.exe folder then use them.
If not found file config in winbox.exe folder then use %appdata%
It is very necessary and very useful feature!
Sorry for my English. I use Google translate.
I want it back too.A feature I'm constantly missing is a filter/search feature for the logs. Would be a very nice feature to have.
On this moment you can't even select a part or rule of the log! Would be nice (together with a filter/search funcion) to have the ability to at least highlight (by selecting, standard windows behaviour) a word or line of interest. And then copy and paste would be the icing of the cake......I want it back too.A feature I'm constantly missing is a filter/search feature for the logs. Would be a very nice feature to have.
Works fine in my windows10.Just noticed that on windows 10 when you pin winbox 3.0rc12 to the taskbar, the pinned sessions don't work..
Windows 10 introduced a more or less similar bug to PuTTY:
http://www.chiark.greenend.org.uk/~sgta ... lists.html
You can use CTRL-TAB and CTRL-SHIFT-TAB for switching between windows without a tab control.A suggestion I already told to Sergejs and Normunds (I believe) at the MUM: being able to switch between opened windows inside the same winbox session with some kind of key combo, CTRL-Tab already switches between tabs, something like shift-tab, ctrl-shift-tab or anything not too contorted
Just checked on windows and you're right! Now to check why it doesn't work under wine.You can use CTRL-TAB and CTRL-SHIFT-TAB for switching between windows without a tab control.A suggestion I already told to Sergejs and Normunds (I believe) at the MUM: being able to switch between opened windows inside the same winbox session with some kind of key combo, CTRL-Tab already switches between tabs, something like shift-tab, ctrl-shift-tab or anything not too contorted
However, for all child windows, the correct shortcuts are CTRL-F6 (forward) and CTRL-SHIFT-F6 (back).
This is the default behavior for MDI applications.
Not my experience:Missing in ipv6 / firewall / address lists... For any write to an src or dst list theres no timeout available so you have no idea of how long is left.
I think this already happens.Note: <identity of RouterBoard>
Group: leave blank
do not increase font size. If you bought a laptop with a high dpi screen, you should use it at the high dpiHi,
in windows 10 fonts in winbox are blurry. Because i'am using a 10" lcd with full hd resolution in screen settings i have set a text size to 125%. 100% is to small but then fonts in winbox are ok.
I'm not saying that it is definitely a bug in winbox. I remember problems with fonts in Win8. However, this is currently the only application that shows a blurry fonts.
Not my experience:Missing in ipv6 / firewall / address lists... For any write to an src or dst list theres no timeout available so you have no idea of how long is left.
Maybe you just don't have the timeout column enabled in "Show Columns"?
Shouldn't you rather correct your application gui to work correctly with such common feature?do not increase font size. If you bought a laptop with a high dpi screen, you should use it at the high dpiHi,
in windows 10 fonts in winbox are blurry. Because i'am using a 10" lcd with full hd resolution in screen settings i have set a text size to 125%. 100% is to small but then fonts in winbox are ok.
I'm not saying that it is definitely a bug in winbox. I remember problems with fonts in Win8. However, this is currently the only application that shows a blurry fonts.
1000+A feature I'm constantly missing is a filter/search feature for the logs. Would be a very nice feature to have.
Restart Winbox with a new Session (or session <none>)Is it possible to add one button on the left hand main menu; "close all"
At times there are so many windows open you want to start with a new clean empty main window.
Sometimes a remote unit that has issues and poor reachability need to have all windows close to reach. When many windows are open a bigger data stream is needed to show them all and at times of trouble that is just too much and session closes. You can't be fast enough in closing many windows so they keep coming back this way.
One "close all windows" button would save a lot of time and irritation.
Normis, you showed again typical behavior of lazy developer. I met it several times when communicating with Mikrotik's support too. Your customer hints you with a new feature and you offer him a workaround (which he probably already knows or can find himself).Restart Winbox with a new Session (or session <none>)Is it possible to add one button on the left hand main menu; "close all"
At times there are so many windows open you want to start with a new clean empty main window.
Adding new buttons for every feature request will end in disaster. I offer you existing solution without need to clutter the interface even more. Sorry, but even Windows doesn't have "close all windows" button
Normis, you showed again typical behavior of lazy developer.
For one; I didn't make the remark regarding the lazy developer behaviour. I do agree though.Adding new buttons for every feature request will end in disaster. I offer you existing solution without need to clutter the interface even more. Sorry, but even Windows doesn't have "close all windows" button
Normis, you showed again typical behavior of lazy developer.
Open needed windows, place it how you want, and just uncheck "Autosave on close" on Sessions menu, what's the problem?Now I have 2 options;
1. When I finish the work I have to close each window one by one to get a clean state again (and then of need open only these needed for for the desk girl.)
2. I just close the session with all its windows, or it gets closed because some event, and next time I open the session again I have to close all these sub windows one by one.
To be fair, consider the case you proposed, where the connection is so bad that it craters before Winbox can open up all previously shown windows. Opening with a clean session guarantees there will be no attempt to open windows, whereas opening with old session and having to wait for the "close all windows" button to be available just creates a race condition.You offer me a work around, that in real is useless.
Consider the following alternate solution, which is what we use: Set up the sessions simply with few windows, then mark the connections as NOT to be saved on close. Now when you open a router, you get basic information suitable to that router; a technician can add as many windows as he needs for any session without having to sort through someone else's leftover clutter (or even his own). Seriously, we have found that turning "save on close" off as a default has improved our workflow in every case. If we have an unusual situation where we need to use save on close, we just make a temporary duplicate entry in the Winbox directory for that router with a different session, and use that.Normally all winbox sessions are left with 1, 2 or 3 subwindows open and this is saved in such way. So if we need to quickly check some connectivity on clients for instance, we just have to open the session and immediately get these windows presented we want to see. Special for the reception desk girl this is handy...
So sessions are saved by default like they were the last time the session was closed.
But now, when I, as the technician, am troubleshooting or doing any other complicated stuff, at times open loads of windows
hmm, never thought about that option. Its not ideal but yes, I agree, it is a workaround. (I do have to close router and it comes back with old settings. Yes, if that was an empty window, it did work..Open needed windows, place it how you want, and just uncheck "Autosave on close" on Sessions menu, what's the problem?Now I have 2 options;
1. When I finish the work I have to close each window one by one to get a clean state again (and then of need open only these needed for for the desk girl.)
2. I just close the session with all its windows, or it gets closed because some event, and next time I open the session again I have to close all these sub windows one by one.
Exactly, that is what is does! But the main window will open and sometimes (like for whatever reason some telnet sessions were still open and are thus asked to open again.) some sub menus just takes such a long time to open that router actually disconnects after some time. If the menu, that is already openend, would show "close all windows" this command could kill all attempts from ROS to open subwindows that delay the router to open completely.To be fair, consider the case you proposed, where the connection is so bad that it craters before Winbox can open up all previously shown windows. Opening with a clean session guarantees there will be no attempt to open windows, whereas opening with old session and having to wait for the "close all windows" button to be available just creates a race condition.You offer me a work around, that in real is useless.
Consider the following alternate solution, which is what we use: Set up the sessions simply with few windows, then mark the connections as NOT to be saved on close. Now when you open a router, you get basic information suitable to that router; a technician can add as many windows as he needs for any session without having to sort through someone else's leftover clutter (or even his own). Seriously, we have found that turning "save on close" off as a default has improved our workflow in every case. If we have an unusual situation where we need to use save on close, we just make a temporary duplicate entry in the Winbox directory for that router with a different session, and use that.[/quote]hmm, I have to consume this. We could indeed setup some standard router info setting, safe it, close it and open it again and disable the 'safe at exit' option. From then on router always open in a standard setting.... hmmmmNormally all winbox sessions are left with 1, 2 or 3 subwindows open and this is saved in such way. So if we need to quickly check some connectivity on clients for instance, we just have to open the session and immediately get these windows presented we want to see. Special for the reception desk girl this is handy...
So sessions are saved by default like they were the last time the session was closed.
But now, when I, as the technician, am troubleshooting or doing any other complicated stuff, at times open loads of windows
*) allow to specify romon agent via command line;
*) fixed window size when winbox is opened first time;
*) fixed problem where it was not possible to connect to router through RoMON if
Open in New Window was enabled;
I agree, it's not too big of a deal to add a button for this option.I don't understand why such a button 'close all' would be such a big deal to embed it in the menu. There are several buttons that are only used by some in very special setups. If designer would start counting all button usage of all buttons of all MT users I'll bet my requested button gets a lot more usage than some of the other 'obscure to many' buttons presently in the menu.....
It's the same as everywhere else (e.g. web browser), you need brackets: [2c██:█88:1104]Having an issue with Winbox... Can't connect to IPv6 addresses.
the behavior ir correct, except that it should probably remember that you used advanced mode. The fact that Advanced is not the default, is correct.With Tools->Advanced Mode enabled, WinBox 3.0rc13 starts with top part having only three fields displayed (Connect To, Login and Password) as if advanced mode was not enabled. The list below does show all fields correctly. You have to turn advanced mode off and on again, to show all fields in top part. But next time WinBox is started, it's broken again.
yes yes. now we are talking. thank uWinbox 3.0rc16 version is released:
*) fixed problem where it was not possible to connect to router through RoMON if
Open in New Window was enabled.
Example:
XX:XX:XX:XX - RoMON agent address
YY:YY:YY:YY:YY:YY - RoMON neighbour MAC address
username - Login username
password - Login password
winbox.exe --romon xx.xx.xx.xx yy:yy:yy:yy:yy:yy username password
This is a wInbox 3 bug of long standing reported in this thread multiple times by mutliple people. One such discussion begins here. In my opinion, this failure is the single most consequential remaining bug in beta Winbox, has been present since June or so, and is long overdue for a fix. Best avoidance action is to keep a copy of the older "neighbor viewer" tool handy and copy the MAC address into Winbox by hand (since you can't copy and paste from the neighbor viewer tool).I have a problem with WinBox that the MAC-address of the RouterBoard (hAP) doesn't show up in the Neighbor's table. If I use your other tool, called Neighbor, the device shows up and I can manually enter the MAC-address in the "Connect To" field in WinBox and connect without problem.
I have tested with windows 8 and 10 and several versions of WinBox 3 with the same result. The two applications (Neighbor & WinBox) have the same settings in Windows Firewall.
Any tips on how to solve this?
Indeed! A very annoying bug still around!This is a wInbox 3 bug of long standing reported in this thread multiple times by mutliple people. One such discussion begins here. In my opinion, this failure is the single most consequential remaining bug in beta Winbox, has been present since June or so, and is long overdue for a fix. Best avoidance action is to keep a copy of the older "neighbor viewer" tool handy and copy the MAC address into Winbox by hand (since you can't copy and paste from the neighbor viewer tool).I have a problem with WinBox that the MAC-address of the RouterBoard (hAP) doesn't show up in the Neighbor's table. If I use your other tool, called Neighbor, the device shows up and I can manually enter the MAC-address in the "Connect To" field in WinBox and connect without problem.
I have tested with windows 8 and 10 and several versions of WinBox 3 with the same result. The two applications (Neighbor & WinBox) have the same settings in Windows Firewall.
Any tips on how to solve this?
I'm still curious what it is about this discovery protocol that makes boards with the default configuration require any special handling--and why it's so difficult to make the beta Winbox do the same thing. I can't imagine why MT wouldn't want people to be able to discover defaulted boards with Winbox--but considering the delay in restoring such a basic (and highly demanded) function, sometimes that's what it seems like.Indeed! A very annoying bug still around!This is a wInbox 3 bug of long standing reported in this thread multiple times by mutliple people. One such discussion begins here. In my opinion, this failure is the single most consequential remaining bug in beta Winbox, has been present since June or so, and is long overdue for a fix. Best avoidance action is to keep a copy of the older "neighbor viewer" tool handy and copy the MAC address into Winbox by hand (since you can't copy and paste from the neighbor viewer tool).
"Mikrotik, please correct this asap"!!!!
WHAT? You must be joking?Hotz1 - This issue is fixed but it depends also on RouterOS version. Starting from 6.33 (and of 6.33rc of course) it will be fixed.
And that is why I wrote that it will be fixed in 6.33 version not that it is fixed in 6.33 which of course does not exist yet.WHAT? You must be joking?Hotz1 - This issue is fixed but it depends also on RouterOS version. Starting from 6.33 (and of 6.33rc of course) it will be fixed.
The issue is NOT fixed yet in any version that is 'current' or 'stable'. You refer to 6.33 or 6.33rc. Well, the first is not available yet at the moment of writing this post and the second is 'rc' like the work implicates "release candidate"....
BUT, we are already happy the issue is under attention and will be fixed!
That's good news--but you do realize that changing ROS to work with the beta winbox means that this issue is going to plague us until the last RB is upgraded to 6.33 or newer. Keep in mind, that includes every RB currently in existence, new or used.Hotz1 - This issue is fixed but it depends also on RouterOS version. Starting from 6.33 (and of 6.33rc of course) it will be fixed.
Indeed. Your audience here are engineers, whose training stresses that changing products B and C to compensate for a deficiency in product A results in inefficiencies and often results in additional future problems. Perhaps it would be a good investment of your time to explain why the problem, introduced by Winbox, cannot be fixed in Winbox. (After all, Neighbor Viewer still works fine, so the problem is soluble.) The explanation may be convincing enough to persuade us to resign ourselves to the proposed solution... or conversely, maybe one of the engineers here can offer an alternate (and better) solution that you have not yet considered.you do realize that changing ROS to work with the beta winbox means that this issue is going to plague us until the last RB is upgraded to 6.33 or newer. Keep in mind, that includes every RB currently in existence, new or used.
The old ROS versions obviously had a way to be discovered. Call me crazy, but it seems to me the fix should occur in winbox: let the beta winbox discover devices in the same way the earlier winbox does. Until all boards everywhere are upgraded beyond that point, why not include the old discovery protocol as a compatibility mode, rather than make people deal with invisible RouterBoards for the next few years? I hate to imagine how many trouble tickets and forum posts it's going to create in the meantime.
I can only assume there is a practical reason it is so difficult to get the beta winbox to do what the earlier winbox still does routinely; maybe something about its structure (e.g., related to threading) that breaks the old discovery method for defaulted boards. But I think people are going to continue asking for an explanation until one is provided.
It doesn't update itself automatically, there is a "check for updates" menu item that "automatically" performs an update if you choose it.Didn't get any autoupdate
It' not separately upgradable. It's contained in the system package, and is really useful only for when you're working on a MikroTik router, you don't have Winbox on your PC and, you don't have a working connection to the internet to fetch Winbox directly from mikrotik.com. Otherwise, you can just go to mikrotik.com, download the version you prefer, and keep it on your PC.sorry ! I'm a newbie , how I can upgrade the file winbox.exe on the routerbord? whit normal upgrade, routerboard only upgrade code but not winbox.exe ....
thanks.
YES!! Thank you.New Winbox version is released!
What`s new in v3.0rc17:
*) discover older version RouterOS routers and SwOS switches as well;
http://www.mikrotik.com/download
It's not just him; it has been happening on my PC too, going back several 3.0rc releases.As for AVG issue - I have tested it myself with rc16 and rc17 version but have not managed to reproduce it. It sound like something specific is configured on your AVG when Winbox is recognized as virus. Please test if issue persist when you use rc17.
I don't know what AVG version do you use, in my case winbox is not recognized as a threat by AV engine, but by 'Identity Protection' module. Probably due to two reasons: winbox.exe is not digitally signed and when is running some 'strange' network activity occurs.As for AVG issue - I have tested it myself with rc16 and rc17 version but have not managed to reproduce it. It sound like something specific is configured on your AVG when Winbox is recognized as virus. Please test if issue persist when you use rc17.
Can't yet speak to how well this works, but rc17 has introduced an extremely annoying bug:New Winbox version is released!
What`s new in v3.0rc17:
*) discover older version RouterOS routers and SwOS switches as well;
Neither does rc12WinBox RC16 does not see RC17 as available update from "Check for update" menu.
Hm. When I heard it was available, I went into Winbox and used the update feature, and everything worked first time.WinBox RC16 does not see RC17 as available update from "Check for update" menu.
If you are changing something users are used too for long time (like this) you should add a settings which allow to change the behavior to users who want it. I am not very happy with this change for example because I am using neighbor list to connect not only to new devices with empty password. And I will not add the devices I am just testing on my desk to the managed list (I am not using managed list at all - please delete it in next release ). So I (and probably others) prefer if the password is not cleared (but old saved one remains active) when I click on a device in Neighbors list.3) After multiple requests, we decided to use default admin without password if router is selected from Neighbours list. If that should not be used, then router must be saved in Managed tab.
How nice!New Winbox version is released!
What`s new in v3.0rc17:
*) discover older version RouterOS routers and SwOS switches as well;
http://www.mikrotik.com/download
I can only agree on this 1000%. Yesterday thought something was wrong in this version...every time I opened winbox my default adminname with password has gone...... Now I found it is default?If you are changing something users are used too for long time (like this) you should add a settings which allow to change the behavior to users who want it. I am not very happy with this change for example because I am using neighbor list to connect not only to new devices with empty password. And I will not add the devices I am just testing on my desk to the managed list (I am not using managed list at all - please delete it in next release ). So I (and probably others) prefer if the password is not cleared (but old saved one remains active) when I click on a device in Neighbors list.3) After multiple requests, we decided to use default admin without password if router is selected from Neighbours list. If that should not be used, then router must be saved in Managed tab.
Thanks
Yes, please. I would like to say that I got empty password box each time I start the Winbox RC17 - even if previous session was used with manually entered password. (I am using [X] Keep password).We will revert change which set credentials to admin without password.
Yes please. Now its very annoying.We will revert change which set credentials to admin without password.
+1Yes please. Now its very annoying.We will revert change which set credentials to admin without password.
Any change to say something about my other remark? (Closing windows on disconnect...)
hmm strange. After I checked "[x] Open in New Window" the password started to appear when I start winbox again. Even if I unchecked the "[ ] Open in New Window" again...Yes, please. I would like to say that I got empty password box each time I start the Winbox RC17 - even if previous session was used with manually entered password. (I am using [X] Keep password).We will revert change which set credentials to admin without password.
Like temporarily disabling "speed-limit" queueing so the file copy can complete in a reasonable time.[*]Blocking file copy
when a file (new ROS) is being copied to the station using Winbox I cannot access anything on the remote radio. Winbox 2.x allowed this. So I could see some thing I forgot to check before the file transfer was started.
Any idea when this may be available for download? This is still driving me bats on a daily basis.We will revert change which set credentials to admin without password.
I went to the downloads page at mikrotik.com and found the new version. Note that this new version is not being picked up by Check for Updates in the Tool menu of rc17. I get "There are no new updates," and the newest change log shown is for rc17.What's new in v3.0:
*) do not reset username & password when one of the routers is selected in neighbors list;
While in some cases this makes sense we used to achieve that same result (default to admin with no password) with the old Winbox by unticking the "Keep Password" box.
3) After multiple requests, we decided to use default admin without password if router is selected from Neighbours list. If that should not be used, then router must be saved in Managed tab.
Which menus specifically are you missing? Which RouterOS version are you connecting to?v3.0rc17 was supposed to fix the issue with seeing options for older rOS and it doesn't.
I do not remember how to upload an image but my previous post is still an issue.
we use rOS versions 2.x to 6.xWhich menus specifically are you missing? Which RouterOS version are you connecting to?v3.0rc17 was supposed to fix the issue with seeing options for older rOS and it doesn't.
I do not remember how to upload an image but my previous post is still an issue.
I think this is another report of this problem from back in March.we use rOS versions 2.x to 6.xWhich menus specifically are you missing? Which RouterOS version are you connecting to?v3.0rc17 was supposed to fix the issue with seeing options for older rOS and it doesn't.
I do not remember how to upload an image but my previous post is still an issue.
any version below 6.x there are menu options that do not display in Winbox v3.0
if I could add an image I would show you, there are many that are not available.
Example:
IP/Hotspot