*) fixed problem - some item disable did not work;
*) fixed problem - port numbers & related info could not be specified in firewall after tcp protocol was selected;
If you experience version related issues, then please report them to support@mikrotik.com.
If you try to upgrade directly from Winbox loader and version is not available, then you might need to wait for a while until cache in path between your device and our servers is refreshed.
It is not a WinBox and never be. with win box you can do way more stuff in few sec and compare and check in web your view is very limited to one page. ROS have a lot good feature compare to 2.97 since I was started with ROS, just hope one day I see WinBox for Mac and Linux, which is 100% missing it.
I agree having a native version for MacOS would be really nice to have as I am sure if you do a poll to see how many OSX users there are more then you think. Meanwhile the Wine version which is floating around works quite well, most of the time.
You have to remember a lot of us and organisations do not run Winblows operating systems, we either use Linux, MacOS, ChromeOS or something else. I know this comapny I am working for right now only uses Mac’s, Windows is banned.
It is very necessary to have a MacOS and most of Mikrotik staff using MacOS too, most of the networking guys I just now which is a lot they all using Mac.
lets hope they going to change they mind and ask one of the developer to easily develop one for MacOS then Im totally going to wipe my Mac and clean Install the OS without any footprint of Windows.
Noticed this in 3.8 but now I see 3.9 is out and it still occurs.
When quitting winbox wine is left running. (OS X 10.12.2, app built with winebottler 1.8-rc4 - resulting in wine 1.8-rc4)
Steps to reproduce:
launch winbox
connect to a device
click on the session menu and then select exit (or click on the exit button on the left menu)
Expected result: Winbox closes and completely exits.
Observed result: Winbox’s windows closes but the process is still left running. Running killall wine will close any outstanding processes. Right clicking on the icon in the dock and picking quit doesn’t actually quit things. Also using force close to terminate the wine process works.
If you just open winbox and don’t connect to a device and then click either the os x menu close button, or pick the file menu and select exit, winbox closes as expected and wine doesn’t leave any extra processes running.
I realize this is a bit outside normal support (I am attempting to run winbox on a mac) but since it was working in 3.7 it seems there is a regression in 3.8 (and 3.9) to a state where it no longer closes completely.
If any assistance is required testing please feel free to let me know.
When selecting multiple entries in the neighbors tab you can’t connect to all.
On the manage tab you can select multiple devices and the connect button changes to connet to all and functions as expected.
Not sure if this is something new, or if I just never realised which tab I was on when connecting to devices.
So if it isn’t a bug, then consider it a feature request
Hi
All windows 10 insider preview user that is getting winbox crash.
I was thinking about
Maybe we get to work using a weird work around
If we install the the Linux that Windows is offering and inside we run wine?
Maybe it works
both 3.8 and 3.9 do random crashes on win10 x64 home and 100% crash at exiting(instead of correctly closing session). 3.7(and earlier versions) works just fine.
A workaround seems to be click on the session menu and pick disconnect. Then when back at the connect window pick file and then exit. Winbox and wine then close as expected.
I just wish WinBox would use a more standard Window than the one they use - in regular Windows apps you can double-click on a divider between columns and it will expand to the size needed to display the contents of that column - in WinBox we need to click and drag each column divider.
Also, WinBox needs a way to allow the possibility of a template to be used (and modified) so that the same columns are displayed on any MikroTik router that is connected to - especially new ones, so that we don’t have to go through all the column options on each and every router we connect to.
