Skip to main content
Version: 7.26

client


cmr/client​

Conditions: !smips
Type: Settings Directory

For an overview of the CMR-client and its usage, see the CMR-Client documentation.

ArgumentTypeDescription
enabledenum (yes | no)Whether CMR client is enabled or not. Default: no.
peer-id ( unset )stringUnique CMR specific device identifier, of the CMR server.
local-id ( unset )stringUnique CMR specific device identifier.
pairing-requirement ( unset )enum (none | password | confirm)

Defines what the remote device must do before this device accepts the pairing:

  • none - this device accepts pairing automatically, without additional checks
  • password (default) - the remote device may approve pairing by giving the username and password of a RouterOS user on this device; CMR has no separate pairing password
  • confirm - pairing must be approved locally with /cmr/client/pair on this device; approval from the remote side is not possible
controller-addresses ( unset )multi { array-id, address: address (flags=46Dv) }Specifies the controller IP addresses to use. This setting is optional when the client can discover the controller automatically through neighbor discovery or DNS (_cmr._tcp.lan, or _cmr._tcp. followed by the domain name from DHCP), but must be configured when the controller address cannot be determined automatically.
vrf ( unset )enum
Read-only ArgumentTypeDescription
statusstringCurrent CMR-client status.
controller-identitystringCMR server identity.
controller-addressaddress (flags=46iv)CMR server IP address.
pairing-statusmulti { array-id, status: string }Current pairing status.
saved-addressesmulti { array-id, address: address (flags=46v) }List of CMR server's discovered IP addresses.