MikroTik

In addition to the neighbor list not populating after running for a while (the "Refresh" button returns an empty list), when you do run Winbox, sometimes when you close a Terminal window within the Winbox session, the entire session closes.

This is with 3.0rc5, running on Win7.

Please add import from the csv file.

a double click in the sides of the title column could resize column to fit content. like in excel.

No title row on the log screen

I have more than 500 connections and manually add the address book is unrealistic.

winbox 3 rc6 difficult to use, stable, always turn off automatically, or rc5 good, very stable, but I did not save, I do not know now where can be downloaded to.

Hello, where is the 'hide password' feature like in old winbox? Does this v3 has such thing?

Hello, where is the 'hide password' feature like in old winbox? Does this v3 has such thing?

yes
it was moved to settings menu

Doh silly me, thanks

Just want to share something that oddly happened to me while using rc5 the other day on a ccr1009. DNS setting suddenly got deleted and DNS resolution timeout was set to 0.

Caused me a lot of panic... Until I realized that the resolution time was 0!

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

Ok so at the moment of accesing tools-profile my winbox sessions instantly closes.. anyone with the same problem?

Ok so now doesn;t matter what i do my session will close instanlty after pressing the connect button.. what the hell

Ok so at the moment of accesing tools-profile my winbox sessions instantly closes.. anyone with the same problem?

Same here

Just want to say, great work guys....salute to MIkrotik staff!

I know it's late in the product cycle, but...

One thing that would make a lot of my work easier is a simple facility (right-click menu option, or whatever) that would do a reverse DNS on a selected IP address.

Hi Guys

Is there a way to speed up winbox, its very sluggish when applying settings or reading firewall rules. It also crashes if the info takes to long to load. It cant be the connection as it does it on all router even it connected directly.

Thanks

I have some problems using Winbox 3.0rc6 with MikroTik 5.26. The MPLS, IPv6 and Routing menus don't show:

I have some problems using Winbox 3.0rc6 with MikroTik 5.26. The MPLS, IPv6 and Routing menus don't show:

Bug has been reported several times -- seems to be tied to router not running ROS v6. Saw it myself today for the first time on newly purchased unit shipped with 5.24 -- wanted to access system routerboard menu to reboot to netinstall, and had to use terminal window to change setting.

Winbox DANGEROUS... Today I was working on a customer and, while the interface page was open tapped the d key. That disabled the highlighted interface. ONE key stroke, no Alt, no Ctl, no other input. In this case it was the wireless interface on a customer CPE and now it is down. I see this a such a fundamental flaw in UI that it is laughable. THIS is Unacceptable.

ONE key stroke, no Alt, no Ctl, no other input.

The "naked key" UI issue (which I believe exists in the production Winbox as well) was fixed (removed) for the Winbox address window in beta 3, but now it sounds like it also exists in other contexts. I was entirely unaware that naked key commands existed in the router window itself. That might explain a number of similar mysterious wireless disablings I have experienced myself (without realizing I may have brushed the keyboard).

RC8 to download:
http://www.mikrotik.com/download/share/winbox.exe

RC8 to download:
http://www.mikrotik.com/download/share/winbox.exe

What happened to RC7? Did I miss something?

Also is there any changelog available for RC8?

Digital Signature

Dear Mikrotik, please sing new Winbox with digital signature, so we can be sure that executable comes from you. It is called Microsoft Authenticode.

Make sure that it is mature signature, not old MD5/SHA1 based. SHA-256 is today's standard for certificates. It is not expensive, especially shouldn't be expensive for you.

You can also do it like Microsoft did: SHA-1 for compatibility with older systems and SHA-256 for newer:



Think also about PGP signature for software relases (download page) - this can be done without any expenses!
Also use mature RSA key length, at least 2048 bits, but 4096 bits would be better (it also doesn't cost you a penny!) and use at least SHA-256.

And the last thing, please attach SHA-256 cheksums for downloads. MD5 is really obsolete for today. Every Linux distribution (and even new Windows, via PowerShell) allows users to calculate such hashes.


Thank you very much for understanding this very important issue.

With the new rc6, keys like E and D do not work, has this been changed ?

Thanks,

http://www.mikrotik.com/download/share/winbox.exe
rc9

With the new rc6, keys like E and D do not work, has this been changed ?

Thanks,

yes, there were bug reports here to disable these keys, since it was too easy to disable and remove interfaces and rules. we will think of a compromise, maybe introduce new shortcuts, like alt+shift+e or something, so that everybody is happy

Good idea. Hope ctrl + c (x, v) will operate normally everywhere within winbox even in telnet window opened from winbox.

I hope it works over RDP ! as the standard D, E were way good and am very much used to them now !

may be introduce something with can change these, depends on what a person likes, ctrl / or direct.

New Winbox beta version has been uploaded to download site:
http://download2.mikrotik.com/routeros/ ... winbox.exe

*) added RoMON support;
*) show default values in CAPSMAN settings;
*) fixed crash when reopening ping or profile window;
*) added advanced mode.

Winbox Rc9 not working here! (windows7 ultimate)

Please try to delete Winbox files.

You can do it by deleting folder: c:/users/xxxx/Application data/Mikrotik

After you delete these files, please try to reconnect.

Remember that if you will delete these files, then sessions and saved addresses also will be deleted. If you need to save them, then export address list to the file and save it into safe place. Also copy out sessions which you will need to use. After you have deleted files and reconnected to router import address list back and put needed sessions back into their folder.

I have the same problem too. But I don't see error it just closes after trying to connect.
I have tried deleting settngs but that doesn't help. Actually mine are here : C:\Users\xxx\AppData\Roaming\Mikrotik.
Also see attached image how it always starts. The size is always that small, it does not remember size when closed even though it remembers being maximised.
P.S. Even though I don't see the error here is what I have in logs :

Faulting application name: winbox.exe, version: 0.0.0.0, time stamp: 0x552d12d0
Faulting module name: ntdll.dll, version: 6.1.7601.18798, time stamp: 0x5507b3e0
Exception code: 0xc0000374
Fault offset: 0x000cea0b
Faulting process id: 0x2a20
Faulting application start time: 0x01d07b613a095c40
Faulting application path: D:\Files\winbox.exe
Faulting module path: C:\Windows\SysWOW64\ntdll.dll
Report Id: 7efb2f5a-e754-11e4-a133-005056c00008

CyberTod - Which version of RouterOS is installed on your router? As for size issue - we will fix it in next rc version.

I have tried on routerboards with v6.28

winbox 3.0rc9 crash in win7 ultimate x64 after clicking "connect"

I have the same problem - Win7 Home Premium.

all my names and groups are lost on the update, how can i get tthem back ? that was a hard work lost !

can we download the rc6 or earlier then 9. i think even 5 was ok.

New Winbox beta version has been uploaded to download site:
http://download2.mikrotik.com/routeros/ ... winbox.exe

*) added RoMON support;

What is "RoMON"

New Winbox beta version has been uploaded to download site:
http://download2.mikrotik.com/routeros/ ... winbox.exe

*) added RoMON support;

What is "RoMON"

http://wiki.mikrotik.com/wiki/Manual:RoMON

What is "RoMON"

Hopefully, someone will describe it in greater detail at the Miami-MUM this week.

New Winbox beta version has been uploaded to download site:
http://download2.mikrotik.com/routeros/ ... winbox.exe

*) added RoMON support;

What is "RoMON"

http://wiki.mikrotik.com/wiki/Manual:RoMON

As usual, the manual offers a thorough description of how the controls work--but not a lot of insight into what the feature does or how it might be useful.

CyberTod, zikachu, kikikaka and Łukasz - Is it possible that winbox has some kind of compatibility configuration enabled or something like that? I have tested at my workplace and at home. All the time Winbox works and connects when used in Windows 7 64 bit.

RoMON stands for "Router Management Overlay Network". This option allows for you to connect to routers after multiple hops in your routed network.

For example, if you have computer 192.168.88.1 and router with address 192.168.88.254 then you always were able to establish direct Winbox connection. Now if you configure RoMON and your router has neighbour which is reachable through address in another subnet, for example 172.16.1.0/24, then now you will be able to connect to this router directly from your computer. All routers in path have to have RoMON enabled and use same secret.

I'm having similar problem to above running under WINE on Ubuntu Linux - window opens small, the 'Autosave', 'Group', 'note' and other fields are missing, and it only shows some columns in the connect database - can re-add them but it doesnt remember them. Sticking to older rc for now as rc9 feels unusable

joegoldman - Go under Tools menu in Winbox loader and switch to Advanced mode. Then all options will be available.

A work around for those experiencing winbox3.0RC9 crash. Check mark "Open in New Window" before click on connect.

A work around for those experiencing winbox3.0RC9 crash. Check mark "Open in New Window" before click on connect.

Thank you. That workaround works. Actually I remember a similar problem with some previous version, but don't remember was it needed to be checked or not.

On the bright side I notice that the initial connect to the router is much faster. Am I the only one with this problem ?

P.S. Another problem - if used from Dude it does not load session settings. If used separately it works fine.

I noticed that on screen shot, which was posted earlier, connection to router is started from Managed tab. We have tried to reproduce this Winbox crash here locally and no luck. Please someone who can not establish connection to router describe what is saved for this specific router in address list (Group, Note, "Keep password", "Secure mode", etc.).

A work around for those experiencing winbox3.0RC9 crash. Check mark "Open in New Window" before click on connect.

For me it works to. Thank You.

@strods
No I don't use any comaptible configuration. I downloaded like a new file, saved as winbox_3.0rc9.exe. I did not use "Check for updates" option in winbox menu.

This new version rc9 is very unstable. Worse than rc6 I tried up to now... Up to an extend I don't even use it anymore... back to old winbox loader (and miss the very useful improvement that ARE made...)

Many times when I want to open a router by its IP it just flash opens to close immediately. Sometimes I have to try several times. Old winbox loader opens without any problems. And if I enable "open winbox in new window" checkbox on a full desktop after a while I have many of these open. Also when you have many sessions running but due some failure connectivity is lost to all they all open a new winbox loader window after reconnecting the closed sessions. I end up with many open winbox loaders on my desktop. Have now to close the ones not in use.

Many times when I click on a setting inside an open winbox session it makes the hole winbox session to close. Open the session again and it works. But this happen so often that is really becomes an irritation.
We have it on several types of routers, on different PC's (all Win8).

One other issue still not solved; When a router disconnects for whatever reason, after a while the 'dead' winbox session also closes. Very inconvenient. Many times when trouble shooting you need to see what the settings in a router were...

Example: When running a wireless scan in a remote (wireless connected) router you can run the scan by running it in the terminal window of the winbox session of that router.
Sometimes links to remote router are very unstable and thus connect regularly or only a 2 or 3 sec scan will make the session survive.
But as long as I can see the result in the terminal I at least can see what the result is.
Now, many times the router closes the session after a second and I loose all the info. It hardly give me enough time to read the outcome. In the old winbox loader this doesn't happen. First is doesn't loose the connection that easy, and when it does at least the window stays open. Move the "winbox session is closed" notification and you can still read all the data.

Now I developed a routine of immediately creating a screendump before the window is lost again. At least I can still read it. And at the end of a day of hard work I have to clean my dropbox screendump archive since its full of screen dumps made that day!
Sorry, but I really can't see the improvement in this......

Another, minor but irritating issue; When you have several winbox sessions open and you are in the process in opening a new one (typing a new IP for instance in the loader) while at that same moment one of the open session is closed, it 'steals' the active window and suddenly you are typing in another loader session than you think you are. But since this is a closed session waiting to be opened again it won't respond you what you typed and you are all getting messed up.
Very irritating behaviour.

This winbox 'tool' is supposed to be a tool to use in troubleshooting networks. Now it seems I am more engaged in troubleshooting the tool itself. ........

tried removing cached files, re-download winbox.exe ...etc... still crash

But the trick "Open in new windows" works.

I remember the 3.0rc2 also crash similarly. It is fixed in rc3 ( or which version... .. i cant remember clearly..)


crash info:

Problem signature:
Problem Event Name: APPCRASH
Application Name: winbox.exe
Application Version: 0.0.0.0
Application Timestamp: 552d12d0
Fault Module Name: StackHash_f821
Fault Module Version: 6.1.7601.18247
Fault Module Timestamp: 521ea8e7
Exception Code: c0000374
Exception Offset: 000ce753
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 1033
Additional Information 1: f821
Additional Information 2: f821734351f2347e1d6446ab1ffd59a2
Additional Information 3: de5b
Additional Information 4: de5ba675ba9b2c213f8e3b947096a688

Debian 7.8
Wine-1.4.1

In RC9 does not remember selected show columns, window size. :/
does not help remove the user/Mikrotik

joegoldman - Go under Tools menu in Winbox loader and switch to Advanced mode. Then all options will be available.

Beautiful, didn't know that option was there with it turned off by default, that has brought back what I needed though.

It now remembers my window size and columns perfectly.

Thanks

joegoldman, noyo - Simple mode uses only few columns so they are hidden/shown by default. If you use Advanced mode, then you can manage columns as you like.

The advanced mode definitely threw me off too, until I found it under the menus.

Also, it would be nice if the RoMON agent fields were toggle-able-- like "show Romon fields?" in the menu or something. I don't know if I will ever use RoMON so it would be nice to hide it.

Using v3.0rc9 on Win7 x64, I also want to confirm that I can't get Winbox to connect to anything unless I check "open in new window." Unless that is checked, upon clicking connect it just closes Winbox. I deleted all of my preferences under my Roaming folder of AppData, so this isn't an issue of it trying to use old preference files or such.

Something else I've noticed with version 3, going back to rc3 (and maybe before): if I am running a traceroute or ping test through the terminal, this is how it should look:
But if I minimize Winbox, and then go back to the window, this is how it looks:
This is very annoying to me as I run a lot of traceroute/ping tests for a long time to troubleshoot connections, and coming back to the window like that is not a game-stopping thing, but it is pretty annoying.

Keyboard shortcuts are not working in RC9.
For example, the key "and" to enable, "d" to disable any rule does not work.

The advanced mode definitely threw me off too, until I found it under the menus.

Also, it would be nice if the RoMON agent fields were toggle-able-- like "show Romon fields?" in the menu or something. I don't know if I will ever use RoMON so it would be nice to hide it.

Same for me. New features are nice but even nicer if we could easily hide it if we don't want it.

joegoldman, noyo - Simple mode uses only few columns so they are hidden/shown by default. If you use Advanced mode, then you can manage columns as you like.

Advanced mode offers more clutter than I need. Simple mode would be what I would use if it would open with the Notes column visible ( that's where our 65 routers friendly names are kept), and it fully remembered the window size. By the way, even Advanced mode won't re-open to full window height. It's more like 75% (Win 7).

Cheers

When router is rebooted and Winbox 3rc9 offers reconnect, it does not work. Looks like logging is performed but no screen is opened.

When router is rebooted and Winbox 3rc9 offers reconnect, it does not work. Looks like logging is performed but no screen is opened.

I have the same problem

after all trying trying trying... im gettin upset and getting tired.... i have to use my energy to solve the network problems but this stupid winbox take all that energy from me...

if you want advise, use old one and not get angry and no suprises. after soon i hope the mikrotik find the right coders for this small winbox program...

There is no option when you use smips.

Missing Features in new Winbox

These features show up in my routers. Is it possible you neglected to load the ppp and wireless RouterOS packages on that router?

Looks like the new Winbox is not showing those menu items on the older versions of the RouterOS. Anyway to make these backwards compatible? I am seeing the options or our devices that have 6.0 and above.

Dear all,

I can't tell if nobody cares, or nobody have noticed (which I don't believe) that Winbox3 RC does not seem to work properly with ROS 5.26.

Maybe I am the only one experiencig this because I am doing something wrong?

I'm thinking most people are in the "I don't really care" camp. I for one have all my routers with 6.x versions. And if I get a new one that happens to have 5.x, I could always upgrade it via WebFig or FTP or SSH.

There is an error on logon addresses window. When sorting by address is used, it moves the addresses with explicitly written port to the end, so they are not sorted according the address number.

Correction should be made to next RC.

Request for change:

If using the small down arrow in the table header to change the displayed columns, everytime when the column item is selected or deselected, the whole menu disappears and it is necessary to click trhu the whole menu path again if someone wants to make more changes. It is really annoying.

Please, make the column marking menu visible and acceptable to set all marks to the columns that should/should not be visible at once and let it be hidden only when user clicks out of the "show columns" menu.

Thank you.

Hi guys!
You can Tinker with the tray icon? Left icon new RC starting at 6, right Winbox version 3.0rc5
Thank you.

Hi guys!
You can Tinker with the tray icon? Left icon new RC starting at 6, right Winbox version 3.0rc5
Thank you.

right click it, and either "pin" or "unpin" from taskbar. see the difference

Please everyone who is having trouble with missing menus on Winbox try to delete Winbox files.

You can do it by deleting folder: c:/users/xxxx/Application data/Mikrotik

After you delete these files, please try to reconnect.

Remember that if you will delete these files, then sessions and saved addresses also will be deleted. If you need to save them, then export address list to the file and save it into safe place. Also copy out sessions which you will need to use. After you have deleted files and reconnected to router import address list back and put needed sessions back into their folder.

Hi guys!
You can Tinker with the tray icon? Left icon new RC starting at 6, right Winbox version 3.0rc5
Thank you.

right click it, and either "pin" or "unpin" from taskbar. see the difference

Hi!
Thank you helped, but still would like by default

Please everyone who is having trouble with missing menus on Winbox try to delete Winbox files.

You can do it by deleting folder: c:/users/xxxx/Application data/Mikrotik

After you delete these files, please try to reconnect.

Remember that if you will delete these files, then sessions and saved addresses also will be deleted. If you need to save them, then export address list to the file and save it into safe place. Also copy out sessions which you will need to use. After you have deleted files and reconnected to router import address list back and put needed sessions back into their folder.

Not necessary to delete whole folder and to loose the address list. It is enough to delete only the version folder that corresponds to the ros version on the device where problem is observed.

The path written by strods is not correct in some cases. See my experience here:
http://forum.mikrotik.com/viewtopic.php ... 50#p478938

Please everyone who is having trouble with missing menus on Winbox try to delete Winbox files.

You can do it by deleting folder: c:/users/xxxx/Application data/Mikrotik

After you delete these files, please try to reconnect.

Remember that if you will delete these files, then sessions and saved addresses also will be deleted. If you need to save them, then export address list to the file and save it into safe place. Also copy out sessions which you will need to use. After you have deleted files and reconnected to router import address list back and put needed sessions back into their folder.

Tried this many time with every rc version of WB3, but still missing "wireless" menu (and maybe others, but wireless is most important for us) when connecting to any device with ROS 5.x

It is bug introduced in "rc" version, with "beta" version it worked OK.

So now I have to use Winbox2 for 5.x devices and Winbox3 for 6.x devices

Hi! clear winbox password or all fields after login or protect with master pasword.
1. open winbox.
2. input Master passwod
3. get your host,password and login to router.
4. close winbox.
5. open winbox (inccorect - host and password are saved and you can connect). correct- all info clear and it you can get via master password.

I think something like WinSCP with Master password when you want to login..

A work around for those experiencing winbox3.0RC9 crash. Check mark "Open in New Window" before click on connect.

same here,

Problem signature:
Problem Event Name: APPCRASH
Application Name: winbox.exe
Application Version: 0.0.0.0
Application Timestamp: 552d12d0
Fault Module Name: StackHash_bca8
Fault Module Version: 6.1.7601.18229
Fault Module Timestamp: 51fb1072
Exception Code: c0000374
Exception Offset: 000ce753
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 1033
Additional Information 1: bca8
Additional Information 2: bca8637902933902a49b2f5a8ca2ab42
Additional Information 3: 0c34
Additional Information 4: 0c3434e3fde815f0c5c32e3baf7bf81c

Error in v3 RC9 - incorrectly reporting vrrp state.

Hi,
what about keyboard shortcuts in latest winbox 3.0 for enable (E) and disable (D) on list itmes (interfaces, firewall rules etc.). It seems that this does not work anymore.

Hi,
what about keyboard shortcuts in latest winbox 3.0 for enable (E) and disable (D) on list itmes (interfaces, firewall rules etc.). It seems that this does not work anymore.

I believe a lot of people have been commenting on this, and that I think they disabled these short cuts because a lot of users were accidentally hitting D when they didn't mean to.

The cost of accidental key presses outweighs the ease of a simple one-key shortcut most likely.

Hi,
what about keyboard shortcuts in latest winbox 3.0 for enable (E) and disable (D) on list itmes (interfaces, firewall rules etc.). It seems that this does not work anymore.

I believe a lot of people have been commenting on this, and that I think they disabled these short cuts because a lot of users were accidentally hitting D when they didn't mean to.

The cost of accidental key presses outweighs the ease of a simple one-key shortcut most likely.

Ok, I understand, however where is notice / announcement / release notes about this ?
I believe some shortcuts still can work like "DEL" to delete the item.
Also, winbox could have its own settings (like it has now) and simple checkbox "enable keyboard shortcuts", i believe this is not so hard to implement.

Ok, I understand, however where is notice / announcement / release notes about this ?
I believe some shortcuts still can work like "DEL" to delete the item.
Also, winbox could have its own settings (like it has now) and simple checkbox "enable keyboard shortcuts", i believe this is not so hard to implement.

I think that is the best way to handle this. Shortcuts were disabled because some people complained how easy it is to delete an item, but some people use these shortcuts and rely on them. Just make it an option.

1)
Old DOS shortcuts aren't work, like
SHIFT+INSERT = CTRL+V
CTRL+INSERT = CTRL+C
SHIFT+DELETE = CTRL + X

2)
R.E.D. shotcuts are not active now, please gray it or disable/remove from RMB
e.g. firewall:


3)
A. DEL. C. - Add, Delete, Comment - please not disable it - there are good positive :).

4)
Why This list isn't a scrolled - it's be a that simple.
Why I cannot Select, select and do next select like on/off on sill open one list. Open this and select by one entry is very.. "not optimal" :) Maybe still pressed CTRL should give me switch on/off?


5)
general filters. Good idea be a safe a few common filters as my favorite like "SIPTrunk connection", "FTP". Now I must create this filters again and again, sometimes I must use 7entry in one filter :(. Simple idea for "HTTPS@LAN":


6)
Maybe it's time to create a way to change a RENAME all entry in AdressList. It's always problematic when I must use few scripts to rename names and rename it again into firewall rules. It's be perfect features.


7)
Connection by MAC address is not stable like via IP. Display address with %? Please change into ":".

help me please

Hi There,

Not sure if I am doing something wrong or if this is a bug:
When I create a new device in my CDB file and I apply it to a group, the group part of the config doesnt seem to apply. It also seems that if I try to change the group of an existing device it simply blanks out the group field.

Things I have tried to resolve:
- Cleared my %appdata%\Mikrotik folder
- Tried multiple PCs (same CDB file)
- Tried a with a fresh CDB file

I am using Winbox v3.0rc9
Any assistance would be greatly appreciated

Cheers,
Dave

Not sure if I am doing something wrong or if this is a bug:
When I create a new device in my CDB file and I apply it to a group, the group part of the config doesnt seem to apply. It also seems that if I try to change the group of an existing device it simply blanks out the group field.

In my opinion works OK. e.g. creation and change name of group1 to group2:

1)
Old DOS shortcuts aren't work, like
SHIFT+INSERT = CTRL+V
CTRL+INSERT = CTRL+C
SHIFT+DELETE = CTRL + X

I already mentioned it, but no luck so far. Those other shortcuts are not "old DOS shortcuts" in the obsolete way how it could sound. Those shortcuts are as standard as the more known Ctrl+V/C/X. They worked in every single program I've ever used, even in older WinBox (up to RouterOS 3.x or 4.x) and current WinBox is the only exception. And as could be expected, it's very annoying. The problem is that MikroTik stopped using standard system edit controls, instead created their own and only added support for Ctrl+V/C/X. So once again, please, please, please fix it!

3)
A. DEL. C. - Add, Delete, Comment - please not disable it - there are good positive .

4)
Why This list isn't a scrolled - it's be a that simple.
Why I cannot Select, select and do next select like on/off on sill open one list. Open this and select by one entry is very.. "not optimal" Maybe still pressed CTRL should give me switch on/off?


5)
general filters. Good idea be a safe a few common filters as my favorite like "SIPTrunk connection", "FTP". Now I must create this filters again and again, sometimes I must use 7entry in one filter . Simple idea for "HTTPS@LAN":


6)
Maybe it's time to create a way to change a RENAME all entry in AdressList. It's always problematic when I must use few scripts to rename names and rename it again into firewall rules. It's be perfect features.


7)
Connection by MAC address is not stable like via IP. Display address with %? Please change into ":".

I fully underwrite these points. Special 4 is a long time irritation on the use of winbox. Almost everytime when opening a session I need to open, select, open again, select again etc etc. to get the columns I want. I rarely want the default ones...

It seems that rc9 doesn't save the address list's settings. Comes up w/ address and user, but I have to add the notes field every time I open it. This is really frustrating.

I found a bad TAB "way/road/direction".


Of course work a BACK way by "SHIFT TAB" - OK
Why TAB not stay on "Managed/Neighbors" tab? I found this can be change by "CTRL + TAB".

When I open WinBox v3 then..
"CTRL + F = Find" is not work. I cannot start WinBox and search a proper MTK to open connection.

Workaround:
1) I must click on bottom section of window, address list and CTRL+F is work.
2) Or without mouse: 2x "SHIFT+TAB".

My opinion: CTRL+F should work from any place where a cursor is blinking/located.

We should have this option in v3 too!. I just have problems with reconnection, break a connection etc. and only clear MikroTik folder was help me.

We have finally managed to reproduce Winbox crash when "Connect" button is pressed.

We will fix it in next release.

In my opinion WinBOX v3 is not stable when I connect to v5.26. I must use a WinBox v2 who is stable and works perfect.

First is open a "Error" and after 20sec I see "Could not connect". After pressing any OK button a winbox is closed and I have not any winbox v3 with reconnection...

Winbox RC1 is available. There are lots of changes since beta 3*
http://download2.mikrotik.com/routeros/ ... winbox.exe

Overall highlights of Winbox 3:

Two extremely needed features that would make winbox more productive and convenient:

1. "taskbar" for windows inside winbox. Now bigger windows cover smaller all the time. All admins I talk to are pissed of because of this.

2. searchable, groupable and selectable logs window for gods sake!!! Now we have option to select storage only (all,disk,memory). We need ability to select facility (say I am looking for ipsec logs, or system, or firewall) that contains particular word in it AND within some time frame. Then we need to be able to select lines for copy'ing.

PLEASE, Mikrotik!

When 'Open in new window' is selected a new session is opened instanly, no delay, no wait.
If it is not and the session is opened in the same window there you can see 'Logging in' for 2-3 seconds.
This is on a very fast connection to the board.
Not that it is much delay, but if it can be instant in a new window can't the same be achieved without it ?

I'm thinking most people are in the "I don't really care" camp. I for one have all my routers with 6.x versions. And if I get a new one that happens to have 5.x, I could always upgrade it via WebFig or FTP or SSH.

I must admit that I am pretty much surprised with that approach. It might work fine for someone who jumped to Mikrotik train yesteday, or for someone playing at home with few devices, but if you have installed basis of hundreds of devices in full production, with no reason whatsoever to touch a running system which works fine - it's another story.

If you add problems with Winbox 3, which I simply can't afford, disgracefull bugs appearing in RouterOS 6.x from one update to another ....

If I had not purchased a bunch of hAP's, I would not even consider Winbox 3, and will sure try to avoid it in the near future. I'm still convinced that MiktoTik did not intentionaly made it not to work with RouterOS 5.x or lower.

I'm still convinced that MiktoTik did not intentionaly made it not to work with RouterOS 5.x or lower.

Sure, I agree. But the question was if anyone noticed, or if they did and didn't cared to report it.

I didn't noticed it, as I'm not affected... But you're right, I only have a few MikroTik devices in total, which I upgrade semi-regularly (read: any time there's a change in something that I do use in the setup), leaving all of my devices with different 6.x, and zero 5.x ones.

For people with hundreds of devices, there's also mechanisms for mass upgrades in place... While I understand doing those is always a great risk, there's always the possibility to first upgrade one device (that is like the others in everything - hardware, software, settings), and then if it goes well, do the mass upgrade then.

I dont understand why some network admin refuse to update at least to some 6.xx ros version but claim updating another tools.

Its simply logic updated tools work with updated rOS, even new units come with rOS 6.xx preinstalled, are you doing downgrade then???

I think its a total carelessness to maintain a network with outdated software.

Some can justify on network stability etc etc, but its a lack of logistic and management not be able to get some good practices to apply updates and maintain the network up to date

1. "taskbar" for windows inside winbox. Now bigger windows cover smaller all the time. All admins I talk to are pissed of because of this.

Or at least 'Windows' menu where we can see all open sub-windows and switch between them.

Is it me, or I have many many problems with all versions of Winbox 3 rc

I have many Microsoft Servers (Windows 2008 R2) with Remote Desktop Services. I use to administer many routers connected via Remote Desktop

Winbox 3 fails connecting routers saying it cant create files, and it doesnt remember anything I saved
It tries to create files in the same folder I execute it, b
Perhaps the reason is:

-Windows Session profile folder is "copied" to c:\Users (Until I log off) (from a Network Server)
So, me, as an Administrator, Winbox tries to open files and folders from

c:\Users\administrator\AppData\Roaming\Mikrotik\

But What happens when the Windows Session profile folder is "used" ? (ex: C:\Users\Administrator is used by a previous hanged Session)
Hanged Remote Desktop Profile Sessions folders are very common: Some times when a User log off, some dlls (like printer ones) still remains in memory so windows isnt capable of destroying the Session profile folder completelly.
When the user logs in again: Windows Server addapts itself and create a Windows Session profile folder with Domain suffix

In my case:
For example:

c:\users\Administrator.corp (with the domain)

The problem starts there: Winboxs tries to load files and read folders from c:\users\Administrator and not from
c:\Users\Administrator.corp (the real profile folder)
So winbox cant connect any router (cause it cant download anything)

When will we be getting our hotkeys back in Winbox?
I am talking about the following:
r - remove
d - disable
e - enable

The following still work:
a - accept
c - comment

Been using Winbox for nearly 10 years now, and this frustrates me. As has been suggested in other posts, why isn't there an option to turn it on or off? This cannot be a difficult thing to fix.
I would roll back to an older version of winbox, but then I would get stuck with "corrupted gzip" and the like.

Mikrotik, please fix this.

yes, i also want and option for shortcut keys. its a pitty you remove them.

I dont understand why some network admin refuse to update at least to some 6.xx ros version but claim updating another tools.

Its simply logic updated tools work with updated rOS, even new units come with rOS 6.xx preinstalled, are you doing downgrade then???

I think its a total carelessness to maintain a network with outdated software.

Some can justify on network stability etc etc, but its a lack of logistic and management not be able to get some good practices to apply updates and maintain the network up to date

Well, let me explain why;

1. New purchased routerboards NEVER come with the latest OS. I just recieved a whole bunch of new SXT's and they are all v.5.22. I have never seen units coming with an version OS closer than 2 or 3 away from the last. And by the rate new version are been issued its impossible for sales channels to get their stocks updated.
But of course you can update them when you receive the units. Standard procedure.

2. Immediately updating your production units to the latest OS even if the units run fine on an older OS is not always a good practise. Very often new OS comes with new bugs and issues and that might just bring your network down while with the older OS was doing fine. This forum is full of stories about people upgrading only to find disaster on there path.

I try to keep my network to the latest OS but only after a new OS is tested on new units, than on local units, then on some remote and then, if it all still went well, we implement them on the rest of the network. Because yes, in the end new OS should bring new performances. (And not seldom just the plainly needed reboot revives a unit that was working poorly.)

I dont understand why some network admin refuse to update at least to some 6.xx ros version but claim updating another tools.

Its simply logic updated tools work with updated rOS, even new units come with rOS 6.xx preinstalled, are you doing downgrade then???

I think its a total carelessness to maintain a network with outdated software.

Some can justify on network stability etc etc, but its a lack of logistic and management not be able to get some good practices to apply updates and maintain the network up to date

Well, let me explain why;

1. New purchased routerboards NEVER come with the latest OS. I just recieved a whole bunch of new SXT's and they are all v.5.22. I have never seen units coming with an version OS closer than 2 or 3 away from the last. And by the rate new version are been issued its impossible for sales channels to get their stocks updated.
But of course you can update them when you receive the units. Standard procedure.

2. Immediately updating your production units to the latest OS even if the units run fine on an older OS is not always a good practise. Very often new OS comes with new bugs and issues and that might just bring your network down while with the older OS was doing fine. This forum is full of stories about people upgrading only to find disaster on there path.

I try to keep my network to the latest OS but only after a new OS is tested on new units, than on local units, then on some remote and then, if it all still went well, we implement them on the rest of the network. Because yes, in the end new OS should bring new performances. (And not seldom just the plainly needed reboot revives a unit that was working poorly.)

ok then take 20 versions to properly test reliability of your actual configurations and putting it on production??

my most outdated implementation has 6.19 (upgrading to 6.28 this week), updating software its not a free duty it requires planning testing and proper rolling back planning, but is not impossible.

If the implementation of a network dont take account of maintenance tasks like updating software and maintaining hardware its a incomplete implementation.

In that kind of incomplete implementations maintenance tasks are seen as a issue and a problem because somebody forget to take it in account.

If you click on Tool / Email, it shows you all the predefined server, port, user, and password values. But when you then click on "Send Email," you get a pane in which none of those are filled in, so you have to type them all by hand. There's really no reason not to fill in the defaults from the Email pane.

This is not a new bug in Winbox 3, but it would be nice if it could be fixed while Winbox 3 was open. Thanks.

Hi,
I decided to post my list of bugs/problems related to Winbox 3.0rc9 which bother us:

Crashes

• when I start winbox and try to connect to a station sometimes winbox windows silently disappears without warning or error message (Winbox probably crashes). Usually the second attempt to connect is OK
• when connected to a radio with old ROS (4.x, 5.x) the Winbox 3 rc9 crashes every time (sooner or later). It is near unusable for radios with old ROS
• by clicking some function (menu item) the winbox sometimes crashes („New terminal“ last time). I think you should/could include an exception report dialog box to collect (automatically from internal exception handling) more informations about these problems

UI discomforts/errors

• CR (Enter) not working properly in initial dialog
  Start Winbox, type IP pres <CR> - nothing happen. It should connect (much faster than using mouse to activate the Connect button). Funny thing is that when connection attempt is cancelled using „Cancel“ button and IP edit box is focused the <CR> starts a new connection attempt
• Non-persistent winbox window
  when Winbox loses connection to remote radio it's window disapears silently. Often I have some information in the window I would like to see (just created spectral scans, information from the box I can (re)use - and they can be totally lost because it could happen I can never see them again - lost connection to the radio when something odd happens)
• 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. I even could inspect cached values when connection was lost and the 'termination confirmation' dialog was shown.
• MAC ping reusing the same window
  Older Winbox allowed to use multiple MAC Ping windows from an AP
• Remembered password problem/confusion
  Winbox 3 doesn't remember the correct password. I use 'Keep password' but often I have to retype the password even if I connect to a radio which has the same password as the one I connected before it. Maybe I didn't understand the sessions or maybe it is not working. The winbox offers often bad (not the last used one) password. Note: We heavily use Winbox started from browser via helper utility which is associated with browser. This way is working (the helper utility sends username and password via command line to winbox). But when winbox is invoked manually it often uses unknown passwords (not the last one used when winbox was started manually last time). Winbox 2.2.18 had no such problem.
• Icons
  allow to disable left menu icons. They are disturbing, non-informative/confusing and space vasting.
• Communication is not send through proper interface
  when you have multiple NICs (even virtual ones) Winbox tends to send the discovery packets (and the communication packets too) through only one interface (often the improper one). I have 2 nics in the PC and some Virtual box related virtual NICs and using the Winbox in this situation is a pain. Even o notebook I have to disable Wifi interface to be able to connect to or discover MT device on ethernet.
  Send the discovery to all interfaces and the communication to proper ones or allow us to select the interface.
• Ethernet Status tab
  This is the one of the most important tabs for ethernet and Winbox3 moved it from the 3rd position in the Interface dialog window to 6th. It looks like it is not problem of Winbox itself but higher ROS versions. If you are not able to create the proper order on the first time then let it be and do not change it in future (when users are used to the order).
• Monitor too small to use winbox
  some config dialogs in some situations are not usable - Ingress vlan translation on 24port CRS for example. There is noway to use Winbox dialog to manage VLANs in this case even on 1920x1200 resolution.
  The solution here could be ranges of interfaces (ether2-ether20 for example). Ranges of interface would simplify CLI settings/reading too.
• ERROR: could not create file
  when connecting to a radio this error appears (rarely). And it is not possible to connect to the radio. Even subsequent attempts fails with the same problem. Give us more information instead of general error message.
• Terminal window problem
  editing commands which don't fit one line tends to cause problems with displaing the line properly.

Wishes

• Get rid of the DLLs downloaded from target box
  replace them by definition files. After it you can create Linux version of Winbox more easily.
• BW test predefined parameters
  IP/test type/tcp connection count/admin/password. It would speed up general connection testing.

Hi,
I decided to post my list of bugs/problems related to Winbox 3.0rc9 which bother us:

Crashes

• when I start winbox and try to connect to a station sometimes winbox windows silently disappears without warning or error message (Winbox probably crashes). Usually the second attempt to connect is OK

I can confirm this.

[*]when connected to a radio with old ROS (4.x, 5.x) the Winbox 3 rc9 crashes every time (sooner or later). It is near unusable for radios with old ROS

Or connected by mac while unit on the desk and in an old version. Meaning new purchased units connect to for 1st time config always disconnect first time. Work around is to inmediately set ip dhcp-cl and use the obtained IP for further login. Otherwise unit keeps quiting....

[*]by clicking some function (menu item) the winbox sometimes crashes („New terminal“ last time). I think you should/could include an exception report dialog box to collect (automatically from internal exception handling) more informations about these problems[/list]

I can confirm this.
Units also disconnect regularly while filetransfer is running. In both mac and ip mode!

UI discomforts/errors

• CR (Enter) not working properly in initial dialog
  Start Winbox, type IP pres <CR> - nothing happen. It should connect (much faster than using mouse to activate the Connect button). Funny thing is that when connection attempt is cancelled using „Cancel“ button and IP edit box is focused the <CR> starts a new connection attempt
• Non-persistent winbox window
  when Winbox loses connection to remote radio it's window disapears silently. Often I have some information in the window I would like to see (just created spectral scans, information from the box I can (re)use - and they can be totally lost because it could happen I can never see them again - lost connection to the radio when something odd happens)

Complained about this some version ago. Very, VERY, inconveniant. Because indeed at times the 'old' window contains still readable info. Now it just got lost.....

[*]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. I even could inspect cached values when connection was lost and the 'termination confirmation' dialog was shown.

Confrimed. And annoying. Now you have to wait untill upload is finished. In the meantime cannot do anything in winbox session. Not even move the windows because in the meantime I want to read some info.. very inconveniant

[*]MAC ping reusing the same window
Older Winbox allowed to use multiple MAC Ping windows from an AP
[*]Remembered password problem/confusion
Winbox 3 doesn't remember the correct password. I use 'Keep password' but often I have to retype the password even if I connect to a radio which has the same password as the one I connected before it. Maybe I didn't understand the sessions or maybe it is not working. The winbox offers often bad (not the last used one) password. Note: We heavily use Winbox started from browser via helper utility which is associated with browser. This way is working (the helper utility sends username and password via command line to winbox). But when winbox is invoked manually it often uses unknown passwords (not the last one used when winbox was started manually last time). Winbox 2.2.18 had no such problem.
[*]Icons
allow to disable left menu icons. They are disturbing, non-informative/confusing and space vasting.

+1

[*]Communication is not send through proper interface
when you have multiple NICs (even virtual ones) Winbox tends to send the discovery packets (and the communication packets too) through only one interface (often the improper one). I have 2 nics in the PC and some Virtual box related virtual NICs and using the Winbox in this situation is a pain. Even o notebook I have to disable Wifi interface to be able to connect to or discover MT device on ethernet.
Send the discovery to all interfaces and the communication to proper ones or allow us to select the interface.
[*]Ethernet Status tab
This is the one of the most important tabs for ethernet and Winbox3 moved it from the 3rd position in the Interface dialog window to 6th. It looks like it is not problem of Winbox itself but higher ROS versions. If you are not able to create the proper order on the first time then let it be and do not change it in future (when users are used to the order).

Fully support this opinion!

[*]Monitor too small to use winbox
some config dialogs in some situations are not usable - Ingress vlan translation on 24port CRS for example. There is noway to use Winbox dialog to manage VLANs in this case even on 1920x1200 resolution.
The solution here could be ranges of interfaces (ether2-ether20 for example). Ranges of interface would simplify CLI settings/reading too.
[*]ERROR: could not create file
when connecting to a radio this error appears (rarely). And it is not possible to connect to the radio. Even subsequent attempts fails with the same problem. Give us more information instead of general error message.
[*]Terminal window problem
editing commands which don't fit one line tends to cause problems with displaing the line properly.[/list]

Indeed

Wishes

• Get rid of the DLLs downloaded from target box
  replace them by definition files. After it you can create Linux version of Winbox more easily.
• BW test predefined parameters
  IP/test type/tcp connection count/admin/password. It would speed up general connection testing.

Allthough the new winbox has some improvements compared to the old versions these are hardly enough to choose it over the old vesion due all the new imperfections introduced compared with lots of 'old' irritations still not been touched.
When a new winbox version is to be made it should do much better and the developments should also go faster. Its now already going for months, longer than most of the software upgrades take to see the light!

dada++
WirelessRudy++

At the moment, even with all the new features and improvements to Winbox 3, it's pretty much useless in production environments.

For home use, where most users will login once every year to their router might be ok.

But for professionals managing tens of Mikrotik installations everyday all the new features are not enough to give up on the perfectly usable and stable Winbox v2.


A true upgrade to v3 would be to keep the workflow intact while introducing new features (and NOT bugs).
Right now it's really annoying to use having to learn new ways to do things (fast).

At the moment, even with all the new features and improvements to Winbox 3, it's pretty much useless in production environments.

Especially when MikroTik keeps advising that we have to upgrade to ROS 6.28 to solve many of the Winbox problems we are reporting. You can't just upgrade a production network like that.

dada +
WirelessRudy +
and more... in my opinion WinBox v3 should be BETA with many, many new release before we can speak about RC. MikroTik, why you lost a numbering like x.y.z, this was a good ideology.

Today little GUI bug:
When we move up and down the WinBox v3 list then last entry is cut. Pressing "v" correct the position but now on the top we have this a entry cut...

Sometimes you are just trying to figure out what happened by digging through the log. But there is so much info and specially when you want a quick look into when and how many times something happened it would be nice if you can just temporarily 'select' parts of the text. Would be even better if we than also could copy and paste it somewhere else for further study.

Last version rc9 crashes on Windows Server 2008 R2 and some desktops on Windows 7

I saw it tries to download plugin and when crashes



And I have to use it with hAP lite... and no way...

Can somebody tell me why appears the new line of products on smips without quality support?!

I mean my post upper.

Because it is the way how mikrotik does things.

Because it is the way how mikrotik does things.

ahahahaaaa!!!

Yeah. Funny enough. The life would be so gray without these easter eggs we are finding each day. I am just trying to handle it somehow, because even it brings those bad things, there is no better option for me.

Make the log a rich text file that can be easily exported for further analysis if one needs.

rc10 fixes crash

rc10 fixes crash

Thank you very much

And another bug. Now, after each connecting to any router creates tmp file in same directory where winbox.exe exists:

viw83DD.tmp
viwD151.tmp

etc...

rc10 fixes crash

Part of the upgraded from listed in the Winbox3.0rc9 was RB no longer see.
# No output list

What's new in v3.0rc10:

*) remember first window size;
*) fixed crash when trying to connect to the router;
*) fixed connecting by mac addresses on Windows with multiple network cards (needs at least RouterOS v6.29 on the router as well);
*) added back keyboard shortcuts for tables (INS for add, DEL for remove and all other with Ctrl prefixes);
*) added support for Shift+Ins, Ctrl+Ins, Shift+Del shortcuts in text entry fields;
*) fixed crash when connecting to v5 routers;
*) fixed problem where group column contents were not shown;

rc9 crash...
Just tested RC10, crash problem is fixed . Seems ok so far.

Hello! I decided to try new WinBox 3 (RC9) few days ago - I like the session feature. But I had some troubles with Safe Mode - is it working correctly? I had turned on Safe Mode, made some changes, lost connection. I reconnected back, but there was the old session in the Active Users list and I was not able to start new Safe Mode.

What's new in v3.0rc10:
*) fixed problem where group column contents were not shown;

It also changed the way the list is sorted by group. Previously, when I sorted by group, it would group the entries by the entire group name (e.g., Central, Central CPE, City-E, City-S, City-W, etc.). Now it groups the entries by first letter only, throwing all the Cs into the same group. I much preferred the previous behavior.

Hello! I decided to try new WinBox 3 (RC9) few days ago - I like the session feature. But I had some troubles with Safe Mode - is it working correctly? I had turned on Safe Mode, made some changes, lost connection. I reconnected back, but there was the old session in the Active Users list and I was not able to start new Safe Mode.

If you lose connection during Safe Mode, manage to reconnect before the Safe Mode times out, and ask for Safe Mode again, you will always be told that someone else owns Safe Mode. This is not new with Winbox 3. You have always had to bring up a Terminal window, request Safe Mode there, and choose whether you want the old Safe Mode changes to be rolled back or not.

If you lose connection during Safe Mode, manage to reconnect before the Safe Mode times out, and ask for Safe Mode again, you will always be told that someone else owns Safe Mode. This is not new with Winbox 3. You have always had to bring up a Terminal window, request Safe Mode there, and choose whether you want the old Safe Mode changes to be rolled back or not.

Thank you for information! I didn't know about this - I barely used Safe mode before...

Bug: If you choose two routers that have the same default session file, and click "Connect to all," one opens up with the proper session windows, and the other opens up to a blank gray window.

Autosave Session and Open in New Window are both checked.

This is true in at least rc9 and rc10.

And again sessions are not used when opened from within Dude.

When I select IP > webproxy > access then winbox closed

winbox 3.0rc10 is now creating a folder instead of a data file of the 1.1.1.1.viw.
I am using Linux with wine.

Same on Windows....no session state saving.

Same on Windows....no session state saving.

Small investigation for Winbox 3.0 rc10 on Windows:
- In the Session folder creates a folder "<ip>%<port>.viw" (Session="own")
- If Menu/Sessions/Autosave on Close is turned on, then when you close the program in Winbox's folder "viw<number>.tmp" file is created. After each run, there is one additional file.

upgraded to ROS 6.29.1 to fix the problem where some CRS could not be reached (introduced in v6.29);

This problem still happens with Winbox RC10 even after I cleared cache and tmp files. Winbox RC9 does not have this problem.

We have reproduced this issue where .tmp files are being created. We will fix it in next release.

The C button no longer works for me to set comments in RC10.

Is this also happening for others?

The C button no longer works for me to set comments in RC10.

Is this also happening for others?

It was announced before somewhere, that single letter shortcuts are removed, because there was a risk of accidentaly removing, disabling, etc. We will add shift or something to these keys

in rc 10 last settings are not save. I have to manually add ip address turn on the advance mode. It was fine in rc9. Running on wine. Connect to field is always empty

It was announced before somewhere, that single letter shortcuts are removed, because there was a risk of accidentaly removing, disabling, etc. We will add shift or something to these keys

Yes, I read that and I understand why that was done for remove/disable etc.

But comment was not mentioned.
Comment is a benign function, and removing the shortcut seriously impacts work-flow.

It was announced before somewhere, that single letter shortcuts are removed, because there was a risk of accidentaly removing, disabling, etc. We will add shift or something to these keys

Yes, I read that and I understand why that was done for remove/disable etc.

But comment was not mentioned.
Comment is a benign function, and removing the shortcut seriously impacts work-flow.

ok, we will figure something out. I guess when the programmers removed the shortcuts, they removed all, and will return all as well.

http://xkcd.com/1172/

Sometimes during the day i connect to romon devices nicely, other times i get the message disconnected from romon. I dont know if its a winbox issue or ros. By the way very nice feature!

shortcuts are already back in rc10:

Thank you for the updates and bug fixes
Are there any plans to make this new version fully compatible with the older ROS versions?
Any version prior to 6.0 has missing menu options.

Yes I know they should be brought up to the current ROS, which we are doing slowly but surely.
The issue is replacing hardware among other things to consider and it would be great to be able to use 1 version of Winbox to access all of our devices.

Thanks

Please preserve the checked boxes in "Torch" from one session to another.

-tp

Delete the Winbox folder if you have missing menu items. It has cached some menu layout there. Clear the foler and relaunch to fix this.

Delete the Winbox folder if you have missing menu items. It has cached some menu layout there. Clear the foler and relaunch to fix this.

This does not resolve the issue, Winbox 3 is not completely compatible with ROS version below 6.0, I am not the only one having this issue.
For trouble shooting purposes I did it again and still the same issue.

The C button no longer works for me to set comments in RC10.

Is this also happening for others?

It was announced before somewhere, that single letter shortcuts are removed, because there was a risk of accidentaly removing, disabling, etc. We will add shift or something to these keys

Not being able to C for comments is driving me insane! I hope this comes back soon.

Maybe just have dual-key shortcuts for dangerous commands like remove/disable/enable

What's new in v3.0rc11:

*) fixed session saving;
*) move cursror to password or login field when host is selected in address list or in neighbors

Accidenatly "Debug window" was enabled.
Simply re-download Winbox.exe from our download page. Problem gone

The C button no longer works for me to set comments in RC10.

Is this also happening for others?

It was announced before somewhere, that single letter shortcuts are removed, because there was a risk of accidentaly removing, disabling, etc. We will add shift or something to these keys

Not being able to C for comments is driving me insane! I hope this comes back soon.

Maybe just have dual-key shortcuts for dangerous commands like remove/disable/enable

Right click in the list window to see the shortcuts, they are already made

However, my mail was not wasted. Have added advanced mode. thanks, a good move

In rc11 still when opened from Dude sessions are not loaded. Working fine with rc6

In rc11 still when opened from Dude sessions are not loaded. Working fine with rc6

make sure to delete the winbox files (viw and others), then try again

In rc11 still when opened from Dude sessions are not loaded. Working fine with rc6

make sure to delete the winbox files (viw and others), then try again

But that will delete all my remembered sessions. They load fine if I just open winbox.exe from explorer, but if I open it like a tool from dude with command : winbox.exe [Device.FirstAddress] [Device.UserName] [Device.Password] - no session is loaded.

RoMON does not work in the RC11 and ROS 6.29.1

Yesterday rc11. Today rc12

What's new in v3.0rc12:
*) added "clear cache" command to Tools menu;

Yesterday rc11. Today rc12

What's new in v3.0rc12:
*) added "clear cache" command to Tools menu;

very good!

Ran 3.0rc12 for the first time, opened a session. Clicked 'X' to close session window and got the error message:

"Unable to create the folder 'sessions\'. The system cannot find the path specified."

Ran 3.0rc12 for the first time, opened a session. Clicked 'X' to close session window and got the error message:

"Unable to create the folder 'sessions\'. The system cannot find the path specified."

Try the new "clear cache" button. Also, do you use Windows and a standard path?

WinBox 3rc12 crashes when trying to create virtual ethernet on hap lite 6.29.1

Problem :
in ipsec Policy cannot be change vale of priority to 0 or 1 (use winbox )
from ver 6.27 to 6.29.1 i tested
in terminal it works fine

On devices with POE-out ports, any chance of getting a new "POE" pane in the window for the POE-in port to allow us to set ether1-poe-in-long-cable from Winbox?

On devices with POE-out ports, any chance of getting a new "POE" pane in the window for the POE-in port to allow us to set ether1-poe-in-long-cable from Winbox?

Yeah! This is the only way I got my RB750up to stop port flapping. I had poe-out port flapping on v6.18/19 a few times a day/week, so thought it was time to update to the latest 6.29.1 , what a mistake, port flapped all night, every 10-15 mins. Much worse, and all my cables are super short. As soon as i set poe-in long cable, stopped immediately. What's more, it used to port flap every time i logged in with webfig and winbox, and i certainly could not leave them running on-screen. Now i can leave them running on-screen all day...

Oh, and here's a screen shot of an interesting session of port flapping, so you can't tell me it's not the device's fault when it's doing it on-the-hour! I've seen similar patterns before. It's software {possibly hardware?} for sure, not something else attached:

[img][/img]

When will we be getting our hotkeys back in Winbox?
I am talking about the following:
r - remove
d - disable
e - enable

The following still work:
a - accept
c - comment

Been using Winbox for nearly 10 years now, and this frustrates me. As has been suggested in other posts, why isn't there an option to turn it on or off? This cannot be a difficult thing to fix.
I would roll back to an older version of winbox, but then I would get stuck with "corrupted gzip" and the like.

Mikrotik, please fix this.

This would be great BUT please, add an function to enable/disable this feature in winbox settings.

I got kids ans cats....

When will we be getting our hotkeys back in Winbox?
I am talking about the following:
r - remove
d - disable
e - enable

The following still work:
a - accept
c - comment

Been using Winbox for nearly 10 years now, and this frustrates me. As has been suggested in other posts, why isn't there an option to turn it on or off? This cannot be a difficult thing to fix.
I would roll back to an older version of winbox, but then I would get stuck with "corrupted gzip" and the like.

Mikrotik, please fix this.

This would be great BUT please, add an function to enable/disable this feature in winbox settings.

I got kids ans cats....

It is already returned, and the key shortcuts are different now - right click the firewall list to see the shortcuts. They are no longer single keys, and are kid/cat-proof

"Unable to create the folder 'sessions\'. The system cannot find the path specified."

Try the new "clear cache" button. Also, do you use Windows and a standard path?

Still get the same error and yes, standard Windows paths.

Just move your session folder to existing location and all will be fixed. Atm you probably somehow deleted in in windows user files, and winbox doesn't have permisions to create anything there.

Just move your session folder to existing location and all will be fixed.

No session folder anywhere in sight. Winbox 3.0rc9 continues to work correctly in this regard.

Atm you probably somehow deleted in in windows user files, and winbox doesn't have permisions to create anything there.

Nope. Not deleted anything.

Yesterday rc11. Today rc12

What's new in v3.0rc12:
*) added "clear cache" command to Tools menu;

I am using Winbox v3.0rc12 and am receiving the following error when attempting to connect to any routerboards I have, versions varied from 5.22 up to 6.28:

The procedure entry point ucrtbase.abort could not be located in the dynamic link library api-ms-win-crt-runtime-l1-1-0.dll

The error comes up 3 times and then Winbox connects, but the connection is flaky and I am having to reconnect.


I have a fresh install of Windows 7 Pro. I have .Net 4.5.2 installed with all available Windows updates. Do you require any other information from me?

--
BBSing is a terminal disease and I have the ANSI strain.

About RoMON.
I've added a gateway host - I can connect to it with plain winbox.
I've enabled RoMON on a switch behind it and on the gateway. I can discover both from eachother. When I click "connect to RoMON" button, it connects, I can discover the switch.
Now here is the problem:
When I'm connected with RoMON, all the Managed list is gone. Ok I've manually added the switch by MAC address to the list after connecting with RoMON. When I click that host from the list and click connect (all when connected through RoMON) the new window opens, flashes briefly and I see the connect window with a message that "*host* has beed disconnected xx:xx:xx: ago".
I click reconnect and it works.

Ok. I see that I can specify a RoMON agent - with a hostname. From an unordered list. And it seems that it does not work. It says wrong password, thou I'm not sure what host exactly and with what credentials I am connecting to RoMON. Or is the password wrong on the RoMON or the target host..

Seriously, You guys have to think things through, plan, and test. More. And document.

It appears that somewhere around RC10 that SwitchOS devices are no longer able to be discovered. They still can be scene with the discovery tool on 2.2.18 but not with 3.0 rc12. The first time I noticed this was with RC10.

Winbox working folder should be the same folder winbox.exe exist so it could be portable. I login to customer routers from different pc and places and i have to make every time new viw files the way i want. Why it is in windows user folder?
In the same folder all ini and viw files even this is a usb stick or desktop folder

Winbox working folder should be the same folder winbox.exe exist so it could be portable. I login to customer routers from different pc and places and i have to make every time new viw files the way i want. Why should it be in windows user folder? In the same folder all ini and viw files !

This is set in preferences. You can choose another folder, even the same one.
Tools -> Move Sessions folder

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%

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%

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%

How can it know where you want it? Just set the folder once, and Winbox will remember it.

I think he is suggesting winbox should store all files in the same folder where the winbox.exe was found, so that when he moves a flash drive from one machine to the next, he doesn't have to guess what drive letter the next machine will assign to it.

he doesn't have to guess what drive letter the next machine will assign to it.

Usually applications store preferences in localsettings folder. I don't know of many tools that have a Folder next to them.
The only way we could solve this, is to have a "Preferences" window for Winbox, and then you could have a checkbox "Store settings next to Winbox" which would grey out the "Move sessions folder" button

Winbox is getting too complicated

I think he is suggesting winbox should store all files in the same folder where the winbox.exe was found,

this is what i am suggesting, so everywhere i go around places i plug my usb run winbox and every setting and viw the lastime i had in my routers should be there.
look in the picture below! this is an example of what i mean
"sessionpath" or "path" file of course is not needed as it will be the current folder of winbox

I think he is suggesting winbox should store all files in the same folder where the winbox.exe was found

this is what i am suggesting, so everywhere i go around places i plug my usb run winbox and every setting and viw the lastime i had in my routers should be there.
look in the picture below! this is an example of what i mean
"sessionpath" or "path" file of course is not needed as it will be the current folder of winbox

I wonder what would happen if you set the folder to "."?

I'd like to +1 the idea for total mobility with Winbox. I've been searching for a way to have my sessions and "managed" routers sync between work desktop, laptop, and home desktop as well.

Couldn't you just move the Addresses.cdb file into the "sessions folder" too? That would solve the problem for me as I'm just using dropbox to sync that folder.



-Joshua
Fourway.NET

I am writing again about a problem, but with some updates :

When using winbox v3.0rc7+ as a tool from Dude sessions are not loaded. Actually it does not read them from the session folder, but expects to find them in C:\. When exiting it saves the session changes to C:\. So it becomes very inconsistent when using winbox both from Dude and separately.
And you may say that the easiest thing to do is just move the session folder to C:\ and all is fine. Yes it is and it will work, but then my root system folder will have hundreds of files and will be a bit messy.

It appears that somewhere around RC10 that SwitchOS devices are no longer able to be discovered. They still can be scene with the discovery tool on 2.2.18 but not with 3.0 rc12. The first time I noticed this was with RC10.

I have confirmed a similar problem with 3.0 rc12. I just netinstalled a shipment of a half dozen new mAP and hAP units. After I netinstall either out of the box, Winbox sees it no problem (except for one of the hAPs, which never showed up at any time). Once I load my generic configuration onto it, Winbox won't pick it up anymore unless you type the MAC address manually. An old copy of "MikroTik Neighbor Viewer" (that I've had for four years and use very rarely) picks the device up immediately, every time, but Winbox rc12 just sits there, blank I ran a ten-minute session on one of the mAPs and Winbox never showed it as a neighbor until I shut it down and logged out -- then suddenly it appeared.

It's not a firewall problem, because I don't load any firewall rules, NAT, or anything else. Each of our mAPs and hAPs is configured as just a dumb AP bridge (switch chip bridging the ethernets, added to software bridge for the wireless) with a single IP address, which is pretty simple.

Winbox 3.0 really does have neighbor protocol problems.

dada +
WirelessRudy +
and more... in my opinion WinBox v3 should be BETA with many, many new release before we can speak about RC. MikroTik, why you lost a numbering like x.y.z, this was a good ideology.

Today little GUI bug:
When we move up and down the WinBox v3 list then last entry is cut. Pressing "v" correct the position but now on the top we have this a entry cut...

Noticed the same, very irritating...

On devices with POE-out ports, any chance of getting a new "POE" pane in the window for the POE-in port to allow us to set ether1-poe-in-long-cable from Winbox?

I have to set the long cable by default. Even on 2 or 3 units attached with 1 mtrs pre-fab cat5e or 6 cable (shielded and or not) and even sometimes it works for a couple of days, after a while units can't be powered up anymore by the rb750. It makes the whole 750 to start flipping. Only setting the long cable option make it work again. We use it by default now because its the only way to get a reliable PoE device at remote site......

Installed loader v.3.0rc12 this weekend and since can't open any new router anymore that has basic factory setting.
I have to open it with old loader first, upgrade the routerboard and only after that the discovery tool will find it.

Then, mac sessions to routers on my desk are very unstable. I have quickly to set a dhcp-client on the board so it picksup a IP from my server and than login by IP. Otherwise it's a matter of less than a minute before board disconnects.
Sometimes boards just don't connect by mac. I can try many times and board comes up to close inmediately.

Old winbox doesn't have any of these issues. It just does do what it is suppose to do, open a board. Either by mac or by IP if is has one....
I've got the feeling each new loader's update brings new issues... its almost lika ROS procedures! Disregard the first 20 or so versions because they give you more headaches than it solves......

I think the website should still have the old v2. loader version as first choice. Not this unstable release candidate.
At times you are out in the field without a laptop so use the client's device. Need to download winbox and get this unstable version... I wan't the 'old' stable one...

What version of winbox do your devices offer on their login page?

What version of winbox do your devices offer on their login page?

I don't understand your question? I login with winbox loader. "Login page"? If you mean the webpage of the building webserver? Never use that....

The bottom line is; when I take a new router out of the box (so factory default) I can't open it with the new winbox. If this is what MT thinks of improving winbox I think they lost directions....

The bottom line is; when I take a new router out of the box (so factory default) I can't open it with the new winbox. If this is what MT thinks of improving winbox I think they lost directions....

If you leave 3.0rc12 open long enough (on the order of a minute or two), it will eventually display the factory-default RB.

I consider this just slightly less painful than entering the MAC address manually.

The bottom line is; when I take a new router out of the box (so factory default) I can't open it with the new winbox. If this is what MT thinks of improving winbox I think they lost directions....

If you leave 3.0rc12 open long enough (on the order of a minute or two), it will eventually display the factory-default RB.

I consider this just slightly less painful than entering the MAC address manually.

Well, tried that, but on some units after 5 mins still nothing happened. And some indeed after a longgggg time connected.
I use now the 'old' loader to find and open de board the first time. After I've set a dhcp-client I take the IP and go from there with the new loader. After upgrade to latest ROS the new loader 'sees' the board....

But far from an improvement......

I just wanted to say that the webpage of each (excluding smips) device offers the winbox v. 2. There is no need to search for it elsewhere. I am using v.3rc12 for some time already having no problems with any new or old devices. Just once it didn't detetect the new neighbour device. So I opened other neighbouring device, use look at its neighbours, copy the mac and put it into winbox 3rc12.
Maybe the explore delay could be caused by more than one network interfaces of winbox running computer connected to the same network as it is definitely my case.

Aside from portability/sync support for my saved sessions, I'd love to see the title bar show the router identity first, then the user@ip so that I can more easily tell which session is which in my taskbar when I have 5+ open!

Please add the export and import addresses from a CSV (Tool>Import,Export)

I just wanted to say that the webpage of each (excluding smips) device offers the winbox v. 2. There is no need to search for it elsewhere.

That's no help. New routerboards come by default with another network than we use. So as long as I didn't change the IP of the interfaces to be in my network I can't open any webpage. The whole fun of winbox loader used to be we have access to routers independed if its in an IP network or not. But that advance use compared to other that have IP-level access only is now gone.
The big 'love' for winbox loader by many was that no matter what network issue you had, you could always login to a router with winbox loader, even without knowing its IP or network it was set for. Now we are losing this advance...

I am using v.3rc12 for some time already having no problems with any new or old devices. Just once it didn't detetect the new neighbour device. So I opened other neighbouring device, use look at its neighbours, copy the mac and put it into winbox 3rc12.

The 'old' loader never had such issues. Why should we now have to find work arounds on a new upgraded version?

Maybe the explore delay could be caused by more than one network interfaces of winbox running computer connected to the same network as it is definitely my case.

No. It happens on all of our 7 different office PC's. None of them have more than one interface. But yes, they are all in one network. But again, 'old' loader has no issues.

WirelessRudy,
what is the problem with saving a winbox.exe from one of your router to your computer local disk and use it whenever you want?

I have not lost any advance with 3rc12. There is no limitation to use Layer3 only, the Layer2 works also normally like always. In case I need, I still can run v2.2.18. Both are locally stored on my disk...

WirelessRudy,
what is the problem with saving a winbox.exe from one of your router to your computer local disk and use it whenever you want?

I have not lost any advance with 3rc12. There is no limitation to use Layer3 only, the Layer2 works also normally like always. In case I need, I still can run v2.2.18. Both are locally stored on my disk...

I'm not quit understanding what you are asking here?

On all my 7 PC's and 4 laptops we have winbox.exe stored (not all the latest but ok) like we downloaded them from the Mikrotik website.
On 3 of the working stations in use for day to day configurations of new units we also have the old winbox loader.
These are on the desktop, but like all info on a PC, ultimately stored on the hd.

So we can use it whenever we want. And I have been one of the users in this forum over the past asking serveral times for improvements on the 'old' winbox loader. When they now finally started to make upgrades (I have installed almost all version when they were released) I was delighted to see the new options finally making it.
BUT (almost as usual, like ROS) they come with lots of errors and new issues. Some of the new versions were hard to work with. My technicians hate the new versions now and all fell back to the old v2 winbox loader...

I didn't download a winbox loader yet from a routerboard for 2 reasons:
1. I need IP level connectivity to do the download. After all we need to browse to the routerboard? Since the board is connected with the ethernet port that has another default network as ours we can't login by html. (And we DON'T want to work with the default 192.168.88.0/24 network that everybody knows now. Would be a bad idea anyway. Sometimes we hook up 2 or 3 new devices at the same time. If we would have a .88.0/24 network we would create IP conflicts every time again. All boards have the same IP.)
2. The version to be downloaded from the website, or downloaded as result of the upgrade order, should be working.

I just can't understand why they are not able to make a simple working version that works under all circumstances.... like the old v2.x?

But than again, I complained about this in version 3.2 or 3.3 or so and at the time I got the reply I was the only one complaining and the rest of the user group was very happy! Well, now we are at version 3.12 or so and many, many more posts with remarks and complaints later and still it doesn't.
But I'll guess after 10 years using MT I still don't understand how it works with Mikrotik.....

RC 12 does not recognize SwOS devices or it takes ages to discover them.
WinBox 2.x finds them the time and immediately.

Maybe the explore delay could be caused by more than one network interfaces of winbox running computer connected to the same network as it is definitely my case.

My machine to setup newly-purchased CPEs has one interface, and is plugged directly into each CPE being initialized, so there is only one device on the cable. Winbox 3 still takes either a long time to show each device, or never shows it. Winbox 2 and MT Neighbor Viewer show it immediately. Once the unit has been upgraded to 6.29.1, it appears somewhat more reliably, but still I need to quit and re-open Winbox 3 frequently to get it to show a router when I switch to a new unit on the cable without closing Winbox.

A feature I'm constantly missing is a filter/search feature for the logs. Would be a very nice feature to have.

I encountered some bizarre sorting behavior in 3.0rc12 (don't know when it was introduced)...

View the firewall filters. Click on the action column to sort by action. Now click on the # column to return to the standard top-to-bottom view. The view returns for a second or two, then immediately jumps back into a sorted view. This happens no matter what other column you sort by -- you can never return to normal order view any more.

This behavior doesn't fail in other places, e.g., firewall nat.

The ROS in question was 6.29.1.

Please add the export and import addresses from a CSV (Tool>Import,Export)

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%

How can it know where you want it? Just set the folder once, and Winbox will remember it.

Pleeeeeeeassse, added support portable!!! It's so easy to implement now!
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.

Why 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.

Why 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.

+1

This happened today:

Earlier tonight update a client CPE (SXT) to the latests ROS manually. But for one reason or the other the wireless package became corrupted. So the link was lost, I found out later when this (very important high profile!) client called. So I took my laptop that just had a new Window OS installed and just before taking it with me managed to download the winbox loader from the MT website...

So 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. Since they use fixed IP for all devices there was no dhcp server to request a possible IP of my CPE.
They even managed to run a IP scan, but not a MT mac address to be found....

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! Found it had a local lan IP we never use anymore. But I could just like that login by mac... installed the wireless package again, reboot and unit backup running...
Went back to the client and installed it and up and running again...

Anybody that now tries to tell me that I am doing something wrong with the new loader that makes it not possible to read any routerboard that is not in the same network as the host used to connect to it have to explain me what I am doing wrong.
Same thing happened to us now on all kind of boards. And every time the 'old' loader doesn't have any problem to 'see' any unit, no matter what IP it has, or not has, set.

I just think it is the new loader that is wrong, not our procedure..... and by not having it at the website at hand it creates problems.

So 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!

+1

If you're going to use Winbox 3 for field work, don't leave home without the Neighbor Viewer tool, which is still available from the downloads page. (Unfortunately, it does not support copy for paste, but it's better than a long drive.)

I wonder what is the problem to do verbatim copy of MAC discovery procedure from WinBox 2 to WinBox3 ?

If multiple routers are chosen, all having the same profile, then opened with the "connect to all" button, only the last router in the list will be opened with that profile -- the rest all come up with empty Winbox windows.

I wonder what is the problem to do verbatim copy of MAC discovery procedure from WinBox 2 to WinBox3 ?

"verbatim copy", sorry for my ignorance, I'm not a techno wizz, but what do you mean with that?

I'm just a simple guy that needs to run a network. It worked fine for years with the old winbox loader. Off course I had wishes, lots could, and still can, be improved for day to day work tool.
But accidents always happen at the same moment. My laptop sort of died the night before and I was just ready with a new factory default install before I had to ran off to this client.
This happened before but usually I can go the MT website and download the tools I might need. In the ultimate event I can even use the clients devices, or even login with http.
But now this was not an option. I quickly downloaded the winbox loader fm the website and went for a presumably quick fix........ that took me 2 hours to finalize... only because the new 'improved' and cheered at loader isn't able to read MT's own routerboards...... what a bummer..... definitely not made my day!!

Not a critical comment this time: But an option that could be very handy in winbox loader;

A button that closes all open subwindows in the main winbox session.

Sometimes I have many, many subwindows opened in a session while also running 10 or more session on different routers in my dual monitor setup. (I actually have 4 dual monitor PC's and still at times could really do with an extra screen while troubleshooting... ) But all these windows and subwindows are very confusing.
So to start a new 'job' on a router I regularly quickly want to 'clean' my session to open with only one or 2 new subwindows of need.
Now you have to click on each subwindow over and over again to clean it!
Last night I had over 30 subwindows open in my CCR while working on firewall rules, some simple queues and at the same time troubleshooting some ethernet port issues.... Its 35 degrees and on a laptop with touchpad this was not something that went very fast. I think it took me a full minute or more to close them all. "One minute?" "Is that all?" Yes, that is a lot if you are rushing to get things done....

One button 'close all' would be handy.....

I wonder what is the problem to do verbatim copy of MAC discovery procedure from WinBox 2 to WinBox3 ?

"verbatim copy", sorry for my ignorance, I'm not a techno wizz, but what do you mean with that?

He means, what is stopping the Winbox developers from just copying the discovery code from Winbox2, and pasting it into Winbox3?

As a software engineer in a past life, I know there are many reasons that you usually can't cut & paste; I also know that it's very unlikely that the old discovery behavior couldn't be duplicated within the newly structured code. Whatever the hold-up, regression (loss of former functionality) should always have development priority.

"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.

"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.

@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.

I think MT developers are so preoccupied in improving things, and convinced about their own skills they'd forget to have procedures in place to grant 'old' functionality still works in new versions. And since they are convinced in doing a good job they see no need to have old versions still readily available.

Its just like the ros upgrade. The moment its been released all auto update systems in place by end users or again on the website, are presented with the new version, with all its possible new defects in it with them.
If you're not already have been creating your own 'previous version file' directory on your own server or you don't know how to get the previous you're with your hands in your hair when the new 'final release' version brings new havoc....

After so many years with so many members complaining its a deception to see lots of MT software upgrade's procedures are still not proper......

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%

How can it know where you want it? Just set the folder once, and Winbox will remember it.

Pleeeeeeeassse, added support portable!!! It's so easy to implement now!
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 needs the same!!! Add this future pls!

On Chinese window system, winbox time in minutes and seconds do not see.

WinBox v3.0rc12
New GrooveA out of the box plugged into the same network
PC IP: 10.0.0.100
GrooveA Default IP: 192.168.88.1

Not sure when it broke but under neighbors tab clicking Refresh button would previously show all Mikrotik devices quickly (for connecting via MAC address for initial configuration). With rc12 the GrooveA doesn't appear for a long time, but if you leave it (5-15mins then it'll finally appear).

When devices are in same IP subnet device shows quickly when you click refresh

I think that I have tracked when the "Neighbors" and "Refresh" do not work.

These functions scan computer for all network interfaces and then scan each particular interface for devices but...
IMHO the procedure stops when the interface is not in "Connected" state and the procedure waits till it will go to "Connected".
It does not matter if interface has IP assigned or not. It just is matter of "cable being inserted".

I have verified it with my LAN RJ-45 port in Win7:
1. No cable inserted, no IP assigned, DHCP on...circle spinning on network connections ..WinBox does not work...it is obvious
2. Cable inserted, DHCP on...circle spinning on network connections ..WinBox does not work...
3. Cable inserted, DHCP on...circle..no circle...IP automatically assigned ..WinBox shows devices and works since moment when IP is assigned.
4. Cable inserted, static IP assigned from device's address pool..WinBox shows devices and works via MAC and IP almost instantly.
5. Cable inserted, static IP assigned not from device's address pool..WinBox shows devices and works via MAC almost instantly.

When you have more interfeces then these steps are repeated for each interface but if any of them is not in "proper" state then
the scanning takes ages. Things go worse if you have virtual interfaces, e.g. VMWare, which rarely go "connected" so they block scanning
each time WinBox is used. When the scanning starts from the interface where we expect devices they are shown but when they are on interfaces
which is next to "bad" interface, they are shown randomly when scanning times-out in resonable time. That is why some devices are shown at once
and for some we need to wait or they jump out suprisingly.

Why WinBox is closing itself from time to time ? Interface used to connect to device changes it's position on interface scanning list and is "blocked"
by "Not connected" interface. Time out crashes WinBox.

Please read these...they enlighted me a little bit:
http://stackoverflow.com/questions/5917 ... -applicati
http://blogs.technet.com/b/heyscripting ... pters.aspx

@BartoszP: Interesting, and I think you can be right. MT should look into it.

But; I have PC's that only have one ethernet port, not even wireless, and off course a laptop only has one ethernet port and a wireless that I usually shut down when I have a troubled ethernet connection.
Still new winbox loader takes ages where 'old' loader inmediately shows connected units.

In my PC's situation it could be they are all connected to a 18 port router (8xEther, 1x fsp + 1xWifi) and of that router many ports are not in use. One or two of these ports are used to connect to a new or test board for config purposes.
So maybe winbox loader 'new' scans all ports in the IP domain (network) and 'hangs' at every interface not in use before it finds the one we are waiting for? Almost the same like you prescribed?

One more possible source of troubles: "Let Windows to switch off interface to save power" option located deep in interface options.
When Windows decide to power it off ? It is real magic for me....

Window mysteries does not change my opinion that old scanning procedure could/should be back in WinBox 3 (could be an option in menu).
It is not responsibile for any configuration job so it does not hurt anything.

A feature I'm constantly missing is a filter/search feature for the logs. Would be a very nice feature to have.

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.

I want it back too.

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......
(paste into another .txt or wordprocessor document off course....)

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

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

Works fine in my windows10.

Feature suggestion:
- Add an "used by" pop up option for an item, which shows who uses the entry.
e.g. interfaces->bridges, address->interfaces, interfaces->routes, pools->dhcp servers and so on.

This would be extremely useful for problem fixing and debugging.

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

You can use CTRL-TAB and CTRL-SHIFT-TAB for switching between windows without a tab control.
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.

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

You can use CTRL-TAB and CTRL-SHIFT-TAB for switching between windows without a tab control.
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.

Just checked on windows and you're right! Now to check why it doesn't work under wine.

Thanks!

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.

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.

Not my experience:
Maybe you just don't have the timeout column enabled in "Show Columns"?

any news about new version? portable?

I think there is a small bug associated with a possible feature request on RC3rc12:

When using winbox 3rc12 and saving a connection in the managed list, the note field is set automatically to the device name, which is kind of OK.
But this works only if the device is on the same L2 level with the device. If it is on a remote network, it somehow gets the note from the last used device, with no way to change it.

The feature request: Allow changing the note field (e.g. with Ctrl-M like a comment) on saved entities in the Managed tab.

feature request

By default, when you select a RouterBoard in the neighbors, set as the default
session: <own>
Note: <identity of RouterBoard>
Group: leave blank

Note: <identity of RouterBoard>
Group: leave blank

I think this already happens.
But the note should be editable, like in Winbox 2 - someone may like other informations there.

Hi,
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.

Hi,
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.

winbox3 blurry.png

do not increase font size. If you bought a laptop with a high dpi screen, you should use it at the high dpi

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.

Not my experience:

Screen Shot 2015-08-28 at 9.54.06 PM.jpg

Maybe you just don't have the timeout column enabled in "Show Columns"?

Ah easy miss read - but I did say IPv6 firewall, not IPv4..

There's no timeout even in Winbox 2.x an overlooked major basic feature... (and its not an option to add it just plain name and address only - its AWOL)

Can this be fixed please its SO annoying.

Hi,
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.

winbox3 blurry.png

do not increase font size. If you bought a laptop with a high dpi screen, you should use it at the high dpi

Shouldn't you rather correct your application gui to work correctly with such common feature?
He didn't lowered the resolution, he just magnified the font in the user screen settings.

A feature I'm constantly missing is a filter/search feature for the logs. Would be a very nice feature to have.

1000+
Or just a tool so you can at least select some words and lines. Cut and paste would a nice feature to.

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.

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.

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.

Restart Winbox with a new Session (or session <none>)

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).
Do you think that closing the Winbox, running new one, changing the settings to start with new session and finally running the session is comparable to pushing just one button on a window which is already on the screen?

Normis, you showed again typical behavior of lazy developer.

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.

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

For one; I didn't make the remark regarding the lazy developer behaviour. I do agree though.

You offer me a work around, that in real is useless.
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 she doesn't have to open the windows of need each time again a clients calls in with; "I have no internet!".

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. 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.

So in both instances it would be of help if there would be just one button that just closes all. Can't be difficult to achieve and I'll bet a lot of us would like it....

Another, very annoying at present, feature that could improve winbox a lot:

Every time you want to show, or hide, columns in windows you have to select, or unselect, one of the many options and it get immediately done when you hit the option... Ok if you only need one, but not ok if you need more changes...

Why can't it be made that you can select or unselect ('check' or 'tic' boxes) and after you have select/unselect all you need to is click on "apply" to have them set all at once (selects and unselects)? This would make life soooo much more easy.

Depending on the work you are doing you have different needs to what gets presented in a winbox sessions subwindows columns. Now if you work with 4 routers, and for the info you need have to arrange 6 new columns on each you need 4 x (each router) 6 (open 'show column' submenu) + 6 (select/un select option) = 48 mouse clicks to set the info of need.

In my suggestion you would need 4 (routers) x 1 (open 'show column' submenu) + 6 + 1 (apply) = 29 mouse clicks to set the same.

This is when you hit the right selection each time. But in real it happens regularly you just pick the wrong one (like on touch screens!) and than you have first to undo what you just had done and after that select what you'd actually wanted...
Very annoying when you are in a hurry of have a lot of work to do.....

I'll guess 20% of my time working on my network gets waisted in re-arranging and arranging menu columns this way..... that could be brought back to at least 5%

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.

Open needed windows, place it how you want, and just uncheck "Autosave on close" on Sessions menu, what's the problem?

You offer me a work around, that in real is useless.

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.

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

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.

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.

Open needed windows, place it how you want, and just uncheck "Autosave on close" on Sessions menu, what's the problem?

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..
Other disadvantage is now that since 'auto save' is disabled, if the router disconnects for whatever reason, when openend again I get 'an' old windows setup again. Like I said, not ideal... but it is a workaround.)

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.....

You offer me a work around, that in real is useless.

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.

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.

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

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.... hmmmm

(I still could do with a button too, see my last remark in my previous post. )

New version

What's new in v3.0rc13:

*) 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;

please make saving column size in winbox romon. every time i have to adjust "identity" column so i can see all.

for me romon rarely worked. now with rc13 i dont get the messege "disconnected from romon" but when i connect to main router and try to connect to rbsxt behind it, it always opens main router and not the rbsxt behind the router that i want to see. so my sollution is dstnat to ap behind router so i can see it with winbox.
i dont have any special config. just the quick setup and romon enabled (without secret) in tools. does it need any special firewall rule?

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.....

I agree, it's not too big of a deal to add a button for this option.
I understand the logic that by adding yet another button, winbox will start to get cumbersome, but maybe it's time to make winbox even more user customizable by allowing to select which buttons are where, etc so that wouldn't be a problem.

Another workaround which I usually use is press and keep esc button until all windows are closed.
I have configured the keyboard repeat to maximum and delay to minimum on my windows box so it's quite fast to close as many windows as there are open.
Escape button does not close any terminal windows though.

I do not like if I make connection to the same device via IP or via MAC and WinBox makes two different sessions and does not remember settings.
Could it remember internally MAC address or any internal id to make and save it as one session ?

"open in new window" for romon still has problem. it connects me to main router and no to device behind it.
when i uncheck it, i can connect to devices behind router.

romon was not working for me months now because i have "open in new window" always checked! ???????
i cant believe this! i wouldnt think of that.

double click to connect to a romon device does not work. you have to press connect button.

when you mark multiples devices in romon and press add/set it justs add one in main window

Romon is acting kinda goofy...
I can't remove the column from Winbox rc13. It just keeps coming back each time even with Romon deactivated.
Is Winbox rc12 still available?

Thanks, I found it..

Having an issue with Winbox... Can't connect to IPv6 addresses.

Can ping the IPv6 addresses and browse using IPv6 but router's IPv6 doesn't come up in neighbour list when opening Winbox.

Having an issue with Winbox... Can't connect to IPv6 addresses.

It's the same as everywhere else (e.g. web browser), you need brackets: [2c██:█88:1104]

-

An unrelated bug:

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.

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.

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.

It did and still does remember it. The problem in rc13 is that on next run, WinBox interface applies advanced mode only partially:

There is bug. You need to set off and on advanced mode again. Then it gets corrected.

Key `C`, for adding comment, not working!

Comment = Ctrl+M

Winbox 3.0rc15 version is released:

*) make "Install & Upgrade" button work again;
*) fixed crash when typing Ctrl-D in empty terminal window;
*) show properly advanced mode on start up;
*) make console use whole terminal window width on reopen.

please fix "romon" together with "open in new window"

This is already fixed.

Fix was already included in 3.0rc13.

for me its working only if i deselect "open in new window"
if i select it i connect only to first device (router)

Sorry. Another issue was resolved. Issue which I though you are talking about did return an error.

I have reported your problem to our developers.

(edited)

Winbox 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.

Winbox 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.

yes yes. now we are talking. thank u

"allow to specify romon agent via command line;"

an example please

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

While we're on the subject of command line options for winbox... I've added the beta Winbox to the Tools available in our Dude. The problem is that when opened from the Dude, winbox invocations get opened with an arbitrary session profile. Is there a command line option one can add to fix this?

now up 3 times on open CCR1009-8G-1S OS:6.32.2

sorry it fixed
Download the Visual C++ Redistributable:

For Windows 64-bit
Visual C++ Redistributable for Visual Studio 2015 (x64) http://download.microsoft.com/download/ ... st.x64.exe

For Windows 32-bit
Visual C++ Redistributable for Visual Studio 2015 (32-bit)
http://download.microsoft.com/download/ ... st.x86.exe

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

Thank you!

(if you change the winbox file name to something other than winbox.exe command line stop working)

Hi,

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?

Regards,
Tobbe

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?

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?

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).

Indeed! A very annoying bug still around!
"Mikrotik, please correct this asap"!!!!

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).

Indeed! A very annoying bug still around!
"Mikrotik, please correct this asap"!!!!

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.

Is it possible to change update interval?
Firewall is updated every 2 seconds, connections - every 5 seconds. Too long.

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.

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.

WHAT? You must be joking?
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!

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.

WHAT? You must be joking?
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!

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.

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.

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.

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.

On the Chinese operating system, no way to see the whole time.

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.

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.

I don't know if it is already reported.
When you lose connection to a routerboard the window of the winbox3.xrc moves to the top left corner of the screen, instead of preserving the same position. Using Windows 7.

The USB button seems to be missing on the CCR-1009 device. Can you check confirm?

-tp

Sometimes the session opens in reduced size window and the order of subwindows according the saved session settings is damaged. It is necessary to maximize the window and reload session settings again. The saved session has to follow the window position and dimension when reloaded.

Missing in all winbox.

IPv6 / firewall / address lists

There is no timeout field hidden or otherwise.

We use IPv6 address lists be nice knowing a time value left.

Thanks!

Didn't get any autoupdate

It doesn't update itself automatically, there is a "check for updates" menu item that "automatically" performs an update if you choose it.

Another thing missing from WinBox is prefix-hint parameter for DHCPv6 client.

I cannot add a new device profile if another one exists with the same IP and Username

Opening rc16 yields a virus detection by AVG

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.

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.

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.

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

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.

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

YES!! Thank you.

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.

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.

Regards,