/interface wireless cap menu:
| Property | Description |
|---|---|
| enabled (yes | no; Default: no) | Disable or enable CAP feature |
| interfaces (list of interfaces; Default: empty) | List of wireless interfaces to be controlled by Manager |
| certificate (certificate name | none; Default: none) | Certificate to use for authenticating |
| discovery-interfaces (list of interfaces; Default: empty) | List of interfaces over which CAP should attempt to discover Manager |
| caps-man-addresses (list of IP addresses; Default: empty) | List of Manager IP addresses that CAP will attempt to contact during discovery |
| caps-man-names (list of allowed CAPs Manager names; Default: empty) | List of Manager names that CAP will attempt to connect, if empty - CAP does not check Manager name |
| caps-man-certificate-common-names (list of allowed CAPs Manager CommonNames; Default: empty) | List of Manager certificate CommonNames that CAP will connect to, if empty - CAP does not check Manager certificate CommonName |
| bridge (bridge interface; Default: none) | Bridge to which interfaces should be added when local forwarding mode is used |
| static-virtual (Static Virtual Interface; Default: no) | CAP will create Static Virtual Interfaces instead of Dynamic and will try to reuse the same interface on reconnect to CAPsMAN if the MAC address will be the same. Note if two or more interfaces will have the same MAC address the assignment from the CAPsMAN could be random between those interfaces. |
/caps-man manager menu:
| Property | Description |
|---|---|
| enabled (yes | no; Default: no) | Disable or enable CAPsMAN functionality |
| certificate (auto | certificate name | none; Default: none) | Device certificate |
| ca-certificate (auto | certificate name | none; Default: none) | Device CA certificate |
| require-peer-certificate (yes | no; Default: no) | Require all connecting CAPs to have a valid certificate |
| package-path (string |; Default: ) | Folder location for the RouterOS packages. For example, use "/upgrade" to specify the upgrade folder from the files section. If empty string is set, CAPsMAN can use built-in RouterOS packages, note that in this case only CAPs with the same architecture as CAPsMAN will be upgraded. |
| upgrade-policy (none | require-same-version | suggest-same-upgrade; Default: none) | Upgrade policy options
|