I would like to be able to login to a client via Winbox the same way we can PING, MAC PING, TELNET, MAC TELNET and TORCH. This would allow for quick access to other Mikrotik devices from within another device. I believe THE DUDE has this ability.
these tools are ran within the winbox. while other winbox cannot be ran inside other one. So, the best option is to use the Dude, if you require management over large network. just install server somewhere, make network map (you do not have to actually have to have a lot of probes to monitor somehting) and off you go.
Janis,
The Dude definitely makes life easier when it comes to managing dozens or hundreds of routers, but even it has it’s limits. I’d REALLY like to see a winbox proxy service in both ROS and The Dude. Let me give some examples:
-
The Dude running behind a firewall, so we port forward 2210 to The Dude, and we can get in from anywhere, but we can’t use winbox. If The Dude had a built-in proxy, we could use Winbox from outside.
-
When working on a remote corner of the network, there have been times when I’ve had to strip out IP and/or routing configurations. While working with these units, I have to use mac-telnet from one router to the next in order to get things reconfigured. If ROS had a winbox proxy, it would make life easier.
Yes, I’m familiar with the command line, I’m even reasonably comfortable with the command line, but Winbox is much easier to work with in most cases.
if you can port-forward dude, why can’t you do the same for winbox?
actually, port forwarding the Dude may not be the best solution, have you considered using agents?
but can you launch winbox as another program ? not winbox inside winbox inside winbox… you know, programs cant launch another programs
all you got to do to is set path to winbox.exe to launch in winbox configuration ( or even not that much if you think a little)
and if it comes for password let use last remembered password, in my network all devices got same password
I’m not sure I follow. Sure, I can forward port 8291 to one of my MT boxes… now, what do I do about the other 98 units I might need to access?
Tell me, how does ‘Terminal’ work through The Dude? I can right-click on any MT device and open a terminal window. Why can’t I do that for winbox as well?
actually, port forwarding the Dude may not be the best solution, have you considered using agents?
I understand the concept of agents, and I may very well use that type of configuration at some point in time. However, that doesn’t help with the remote access:
Server (172.17.16.1.20) > Work Router > Internet > Home Router > Client (192.168.0.1)
I forward port 2210 on my work router to The Dude Server. Are you telling me there’s a way to do this without forwarding port 2210?
Right now, we use remote desktop to log into a windows machine so that we can use Winbox. I’d love to be able to do away with that machine and run The Dude on a MT router.
Now, let’s say I set up MT on the edge router (a very likely possibility as I continue to re-engineer my network). Now, let’s run The Dude on that router. No more port forwarding needed for The Dude, but I still can’t use Winbox or Webfig from outside the network.
Put another way… I can give YOU access to The Dude on my network. If you needed to Winbox to one of my devices, how would YOU do it? Set up a forwarding rule for every device you wanted to access? That’s a management nightmare, plain and simple.
no, Dude can’t connect winbox to a router inside some private network, also the terminal doesn’t work that way. The Dude "Tools’ are just shortcuts to the Winbox or Terminal program, with the IP address that you specified in the device settings.
Normis, I KNOW that The Dude cannot connect winbox to a router inside some private network. THIS is the feature I’m asking for. Also to add a feature to ROS to facilitiate a winbox connection to another router that is not otherwise reachable (as described by the OP). In no way is anyone asking for a “winbox in winbox” thing that you somehow visualized…
As for the terminal, yes, it does work… I run The Dude as a client on my desktop at home connected to The Dude server on my company network, and I can use the terminal shortcut to connect to ANY ROS unit that’s reachable from The Dude server. Give it a try, it really does work.
EDIT:
Look at a real world example… SSH has a feature for forwarding X11, the concept is NOT new, we’re simply asking you to implement it in the Winbox protocol.
In the winbox loader, add a connection option called “proxy server,” then winbox will use that proxy server for either connecting directly to an IP/Mac or pull a list of the proxy’s neighbors. It should be a fairly simple feature to add to both ROS and Dude.
Hypothetical command line:
winbox.exe [-p <proxy_address>][<connect-to> [<login> [<password>]]]
I know that’s what you asked. I replied that it can’t do this, that’s why we can’t make it 
you could connect to your network using a tunnel and manage your internal network through the tunnel. That will be safer and a very elegant way that is already available.
And creating pptp tunnel is not that hard.
btw, some security bulletins advice use of secure tunnel when connecting through unknown “territories” of internet to home.