Winbox3rc2 If you’re using the “Open In New Window” using by enabling,
when the connection destination connection is lost in such as restarting,
I want you to stop the window of Winbox come to start another.
When the beta, the window only dialog comes out one I’m sure that was never to be newly generated.
Normis:
Now we have Winbox 3.0rc2. But where is changelog?
Why on download page is still and only 3.0rc1 ?
Winbox 2.2.18 is still missing on download page. In another thread you promise fix http://forum.mikrotik.com/t/winbox-download/84905/1
Doesn’t just crash Winbox, but reliably crashes target router. When I click Save button, Winbox often crashes on next menu command; a minute later, I get a supout mailed to me from the router I had been on.
Sorting log is quite complicated one - I can imagine - but would it be possible to be able to copy lines from log window? Just like from terminal.
Also… has anyone encountered problems with “Copy” (interface/firewall rule…) button? It happened to me several times randomly:
create object (interface, firewall, rule…), set it up and apply changes
copy it, modify it, and apply changes
→ copied object sometimes does not work as expected. Sometimes the new object uses the values from original object, even if the configuration shows new ones.
Happened (not every time) with IPsec peers, IPsec policies, EoIP tunnels (RouterOS 6.24, WinBox 3 RC1 - tested yesterday on EoIP tunnels). On other side, no problem with firewall filter/nat rules with the same approach. It’s not a new thing - happened sometimes even with last WinBox 2 version and RouterOS back to 5.x
Please add a protocol of winbox://[username:password@] so we can include links on web pages to open winbox and login. I understand that there are security concerns around including the username or password in the url like that. If it’s optional then it’s up to the administrators to decide. See the next feature request for a way around including the password.
So it would work alot like mailto: tags on web pages. If you click the link then winbox would open. If the username and password are not supplied then it would simply open winbox and leave it at the connect window with the IP filled in. If the username is supplied then both the IP and username are filled in. If the password is supplied, then it will attempt to just connect, bypassing the connect window completely. If the username and password are already stored, that could be used as well.
Please add the ability to use public key credentials with winbox for Mikrotik login.
It would work exactly like SSH’s authentication.
Winbox could import existing keys from SSH or create a new key pair.
Any public key on a mikrotik that is associated with a user account would accept logins by SSH and Winbox if the corresponding private key is in winbox.
This would go nicely with the winbox://username@IP address request.
Can’t we start a new tread for rc2?
I mean, this forum is filled with bug reports, amendments, wishes and other desires or failures regarading rc3.0, 3.1 and probably already some of 3.2
I don’t expect all bugs etc. to be solved by now, but its now use having discussion going on about versions that are updated already.
Wit a new tread we can at least be sure we talk about the latest version. Forget about what is written about the previous one.
If you reported a bug in earlier versions, check if it solved. If so, good… If not, report again but now in this new tread.
It keeps the tread clear, both for us users/readers as for the MT guys…
By the way, I like the new winbox a lot. Long been waiting for. But, no surprise, its not stable and still a lot bugs to be solved and maybe some more adjustments in its capacities to be made.
I still work with the ‘old’ version beside the new one. One thing notices immediately is that the new version is soooo much slower to start. Opening a router takes seconds, were on the old version it opens at the click…
Keep up the good work! But please start a new tread!