Export will not export the complete config

The call of

/export

Don’t export the user names. For this an call to

/user/export

are necessary.

But that's actually illogical when I export root.
The manual says that only the passwords of system users cannot be exported.

This raises the question of what else is missing from an /export call.

Adding the option show-sensitive will not change anything.

Tested with RouterOS 7.20

Have I hit an bug?

And I don’t use the radius database.

It’s always been this way. Probably because without the password they cannot be readded… just guessing.

Additionally, the passwords are only stored as hashes. There was a request for allowing hashes to be exported. But that’s also against security best practices.

It’s not a bug, and I’m not sure this will change, or even if it should.

EDIT: For a full backup of the device there is the binary backup/restore function.

There’s another thing to look out for: certificates are also not part of the export.

No, it's exactly as it SHOULD be.
The user part, since it cannot be completely and directly managed with a "show-sensitive" export, should NOT be included.
The ultimate goal of the export is to be able to use it on another device to configure it the same way, except for the users, which must be managed separately.

  1. dude database
  2. user-manager database
  3. ssh keys
  4. licenses...

Backup of everything (for users passwords is possible only .backup):

Thanks,

it looks the manual are not exact, because for backup command it will be clear written what will be backed up and what not. Only for the export part are it not clear.

An I hope so, that only pw hashes are stored inside :slight_smile: Which will be salted to. :slight_smile:

The backup binary dump makes me not very happy, because it can only restored on the same device, which will be an problem in case of device replacement. (But this is written clean in the manual) But on the other hand, here the certificates in it.

If you have EXACT same device (and often revision) you CAN restore .backup,
BUT after that, restore original interfaces (real and virtual) MACs...

I see in the old wiki, this was exact written so. Only in the new confluence one it was written unclean.

Wiki:

RouterOS backup feature allows you to save your current device's configuration, which then can be re-applied on the same or a different device (with the same model name/number).

Conflucence:
The RouterOS backup feature allows cloning a router configuration in binary format, which can then be re-applied on the same device.

I think the documentation should be adjusted slightly to make it clear.

Just in case, point #17:

My hope for an option “Restore, but without setting mac-address.” keep tight.