Feature requests

Do you want to be cut off by a hacker?

Look this:
How do I delete previous sessions stuck in an easy way?
Imagem 20170420092152a.png

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. :frowning: 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.

Help us old keyboarders out and add ALT tags to menu and buttons.

This way we can use ALT C for a Close button or ALT O for OK.

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#.

Ip dns port support
So for example we can use 208.67.220.220:443

Requesting for neater and more readable exports

currently:

export compact
/something1
some config
/something2
some config

suggestion:

export compact
/something1
some config

/something2
somet config

spacing them out improves readability a lot.

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! :wink:
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”

+1

please, MSTP & PVRSTP next version…

+1
Really need, please!

request: a default set if IPv6 firewall rules with IPv6 enabled be default

Please add the ability to do a where query in with any valid-variable.

fail example:
:local identity “testRouter”
:local interface [/ip neighbor find where identity=$identity]

fail reason:
result differs from :local interface [/ip neighbor find where identity=“testRouter”]
contains several interface which don’t have the specified identity.

pass example:
:local macAddress “00:11:22:33:44:55”
:local interface [/ip neighbor find where mac-address=$macAddress]

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

setup some VPN tunnel between the routers :slight_smile:
then you may ping inside the VPN, or just use VPN Interface state to detect remote failure

that’s because the variable name “identity” is the same as parameter name “identity”. the following code works correctly:

:local id "testRouter"
:local interface [/ip neighbor find where identity=$id]

by the way, use the following is also correct:

:local interface [/ip neighbor find where $identity=$id]
:local interface [/ip neighbor find $identity=$id]

Thank you, I will try it out!

this one can be quite neat if someone is into parental control

https://datatracker.ietf.org/doc/draft-tale-dnsop-edns0-clientid/

the code is there in dnsmasq since 2.76