Yes, but not immediately - it should be stored as a DNS name and resolved in real time. For example, it’s pointless to resolve /tool email server once and store it as a numeric address, which is why ROS will store it as a name. However, /system watchdog resolves the same server once and then stores it as a number, which is wrong. Also, you don’t want things to fail because they can’t be resolved immediately when you are configuring a router on a workbench and it has no connection to your network.
This would be good for both /int wireless access and /int wireless connection; also the “add to access list” and “add to connection list” operations, where you already know that the resulting entry will not be incompatible with the connection that already exists, because it is being generated from that connection.
Many of the newer, lower-cost devices have no beepers. I have come to rely on the beepers for so much diagnosis (esp. SXT setup) and I really miss them. I would pay the extra buck.
During an Export of /Interface/Ethernet/Switch/Ports it would be nice to have it use a [ find default-name=xxxxx ] like the /interface ethernet export instead just the set#.
It would be nice if there was an option to display a box containing the Ethernet and DHCP Clients (with the Mac, IP, and how long it has been online) connected to it in the Quick Set page.
I believe this request can be implemented very fast but it helps the ROS management with Multiple WAN a lot!
The “/ping” and “/system ssh” allow user to specify the “src-address” parameter so that the command can initiate the network connection on specific WAN easily.
BUT “/tool fetch” doesn’t include “src-address” parameter.
The problem is one ISP blocks all incoming ping request, thus I cannot use ping as a remote monitoring facility, I need to find alternatives to archive this goal.
I write script to carry out the monitoring job, but as I know, “/system ssh” cannot be executed under script environment, which means I cannot use “/system ssh” to do this job.
The only way to choose is to use “/tool fetch” facility to monitor the remote ROS, BUT it lacks “src-address” parameter, to supplement this deficiency, before using the “/tool fetch”, I need to specify a temporary custom route to fix the outgoing path for remote target.
The whole situation can be simplified tremendously by only adds the “src-address” parameter to “/tool fetch”
fail reason:
result differs from :local interface [/ip neighbor find where identity=“testRouter”]
contains several interface which don’t have the specified identity.
pass reason:
gives exact same result as :local interface [/ip neighbor find where mac-address=“00:11:22:33:44:55”]
contains only interfaces that have that MAC address