Sounds like dynamic data would be an appropriate description.
I understand it is useful to distinguish dynamic data from configuration data, but I would still like to be able to export that info without doing so manually. And, I would like to include all such dynamic data – that is, anything that is not included in the current /export.
None of your requests make sense.
Saving an IP or other dynamic data to be used to reconfigure the (same) machine does not make the slightest logical sense.
If it is dynamic, it is obvious that next time it MUST/WILL be different.
Also write something useless, uselessly, on NAND/Fllash is counterproductive.
The point is that you haven’t understood what export is for.
If you want to get a _print_out of how it’s configured at that moment, use… print.
I did not say that I wanted this facilty in order to reconfigure a machine. I don’t.
Nor did I say I wanted it written in NAND. I want it emailed or FTP’d to a server of mine.
I used the export command as a starting point to explain what I was hoping to accomplish. I see how that caused confusion – sorry for that.
I think it would be useful to have this type of current (but dynamic) data.
For example, right now the only way for me to know the DDNS hostname is to log in to each MT device with Winbox and go to /ip cloud.
And the only way for me to know what the public IP of any MT device is would be to log in and go to /ip address.
I’m sure there is other “dynamic” data that would be nice to know (despite it changing), like: hosts heard by bridge, wireless stations registered, DHCP leases, etc.
When you want to generate a mail with the data YOU find interesting, you can do it.
But probably your requirements are quite unique, so it would not be reasonable to have a standard facility for that.
Print what you want and mail it.
Maybe I’ll just try to develop a script that prints the data I’m interested in to a file, and then email or ftp that. Then deploy the script across all MT devices.