^THIS!Reconnect button when connection is lost would be something!
I second this.Reconnect button when connection is lost would be something!
Hell yes, do this!Reconnect button when connection is lost would be something!
Yes that is another annoying problem I face a lot I have a desktop icon that calls a toggle script for when im out in the field. I see this more as a problem with particular *nix OS's though, and how they handle setting themselves to link-local and not continuously trying to connect.If you use winbox on linux with a fixed IP config you need also to put in a gateway ... if not you can't use mac connect ...
There's already a separate protocol, coincidentally named "API". It's even enabled by default in RouterOS 6.x, and can optionally use encryption since 6.1.Would it be too much of a security risk to 'open-source' the separate API used by winbox, and allow others to write their own clients for it? I would love a native Linux version and/or proper cross platform java client.
Yes I'm aware of the API and use it a lot, but it has limitations. The protocol used by winbox would be much more thorough in whats available (but to be honest I've never sniffed the traffic to find out!)There's already a separate protocol, coincidentally named "API". It's even enabled by default in RouterOS 6.x, and can optionally use encryption since 6.1.Would it be too much of a security risk to 'open-source' the separate API used by winbox, and allow others to write their own clients for it? I would love a native Linux version and/or proper cross platform java client.
You could use it to write your own "proper cross platform java client".
++Request from the dev's, would like to see winbox as only open one instance but have multiple tabs. When having 5+ winbox instances open it can get annoying switching between them all, a tabbed interface would be awesome!
+1Reconnect button when connection is lost would be something!
It's the same really. You switch tabs with ctrl+tab as you would do on any other program having tabs.It is much easier to switch windows by alt+tab than pointing at tiny tabs.
If you're talking about the API protocol not having a way to tell the client its capabilities, you're - sadly - right, and what's worse is that MikroTik consider adding such a feature an extremely low priority.Yes I'm aware of the API and use it a lot, but it has limitations. The protocol used by winbox would be much more thorough in whats available (but to be honest I've never sniffed the traffic to find out!)