I find myself often in need to open a new Winbox window and connect to a new device using the IP address found in an already open Winbox, in places like Neighbors or DHCP Leases etc. Currently have to manually retype or copy/paste the address in the Connect dialog. There are actions like Ping/Telnet/MAC-Telnet/Torch, and New Winbox would be useful to add as a new action there. (Neighbors local to the PC and seen by Winbox itself are not necessarily the same as Neighbors seen by a remote router in more complex networks.)
I can't ever recall needing to do that. If it's in neighbors, click either the IP or MAC, and the connect panel at the left populates, and you can either save or connect from there - zero copy and paste. ???
The router is routing between a few VLANs, and the Mikrotik device I want to manage is on a different VLAN than my management PC or Mac running Winbox, so it will not appear directly in Neighbors It's a wireless network with IP addresses of managed devices assigned by DHCP from the central router, saved IP addresses might change over time so I need to use a reasonably fresh one.
- customer calls and reports poor service, I want to check the wireless signal or ethernet link status of the LHG/Disc/SXTsq on their roof
- I open Winbox and log into the central RB5009 that manages the network and find the IP address of the customer's device based on its name in DHCP leases
- I want to connect with a new Winbox to the found IP address, currently need to copy the IP address to the connect dialog, want to be able to directly choose a "New Winbox" action from the actions menu where Ping/Telnet/Torch to that IP address are.
Another useful action to add to that menu could be Btest or Speed Test (test bandwidth only between the central router and the customer, not testing the management link which could be WiFi or even remote VPN).
Do you manage the RB5009 as well? If so, make the leases static, and stop chasing the IP. If not (or you have a remote behind a NAT), you could also do what I did, and have it connect home on an ipsec tunnel, also giving a fixed management identity.
(Myself, I pretty much flat out refuse to let any infrastructure devices take random addresses. They are static, either on the device, or via statiC DHCP assignmenta.
(Dynamic DNS might also be an option, if available).
I've often made permanently-on devices (like access points, switches) static reservations but recently added them as static DNS entries as well so can use a human friendly name like router001.lan