...
- Disable or enable CAP feature on the device
- Set list of wireless interfaces to be controlled by Managercertificate (certificate name | none; Default: none) Certificate to use for authenticating
discovery-interfaces (list of interfaces; Default: empty) - List Set list of interfaces over which CAP should attempt to discover Manager
- caps-man-addresses (list of IP addresses; Default: empty) List Set list of Manager IP addresses that CAP will attempt to contact during discoverycaps-man-names (
- Set 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 - Set list of Manager certificate CommonNames that CAP will connect to
- Set bridge , 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.
Each wireless interface on a CAP that is under CAPsMAN control appears as a virtual interface on the CAPsMAN. This provides maximum flexibility in data forwarding control using regular RouterOS features, such as routing, bridging, firewall, etc.CAPsMAN Configuration Concepts
...