Skip to content

CAPsMAN

← Documentation index

An access point provisioned by CAPsMAN holds none of its own wireless configuration — the controller owns it. Reading the AP directly returns blank SSID, security and band, which makes a perfectly healthy access point look broken.

The platform models the controller relationship instead.

Device roles

Every device is classified from /interface/wifi/capsman and /interface/wifi/cap, and for legacy CAPsMAN from /caps-man/manager and /interface/wireless/cap (see Legacy CAPsMAN):

Role Meaning
standalone Has radios, manages them itself
cap Radios are provisioned by a controller
controller Runs CAPsMAN; has no radios of its own
controller_cap Runs CAPsMAN and has radios of its own: under itself (a supported MikroTik arrangement), or set locally on an access point that is also a controller
none No wireless hardware

The role is detected, not inferred from device_type. That matters because a dedicated controller is usually classified as a router, and device_type is a label a human typed rather than a fact about the hardware. The Radios tab and the wireless section follow the detected role.

A device found to have no wireless role (none) is checked again about once a day, and on a manual Sync, so a router where CAPsMAN is switched on after it was added becomes a controller (#365). A check where the device didn't answer, or answered with an error other than "no such command", isn't recorded.

A recorded role only changes when two checks in a row agree. Until then the device keeps its role, and a controller keeps its list of CAPs and radios. One bad read after a restart turned working controllers into none and moved their clients back onto them (#365). A controller where CAPsMAN really is switched off shows as none after the next slow poll (about 5 minutes), or a second Sync.

How CAPs are matched to devices

The controller enumerates every radio it manages — local and remote — through /interface/wifi/radio, each with a radio-mac. Those MACs are matched against every interface MAC in the fleet.

MAC rather than IP address, deliberately: a MAC is hardware identity and unique fleet-wide, whereas an address is only unique within a broadcast domain. An installation with several segments reusing the same addressing would otherwise attribute a radio to the wrong device entirely.

Two refinements come from real deployments:

  • A controller mirrors each CAP's interfaces locally, so a CAP's radio MAC genuinely appears on two devices. A radio the controller reports as local: false lives on a CAP by definition, so the controller is never a valid answer for it.
  • A radio MAC often differs from the device's interface MAC in the final octet, so lookup falls back to a five-octet prefix while keeping the OUI exact.

A CAP that is not in the fleet is surfaced as unmanaged rather than hidden — that is usually the reason an access point appears to be missing.

What you get

The CAPsMAN panel on the Wireless page lists every controller with the access points it provisions, one row per radio: the AP it lives on (linked), interface name, provisioned SSID, operating channel, connected clients, and state.

Two details are read from the controller rather than the CAP, because the CAP does not know them:

  • SSID — held on the controller's mirror of the interface.
  • Client counts — a CAP's own registration table is empty when traffic is processed centrally. Counts come from the registration table with each client attributed to its radio by following master-interface, since clients register on the virtual AP carrying the SSID rather than on the physical radio.

Clients are shown on the access point they're connected to, even when the controller is the one listing them (#365). With traffic processed on the controller, its registration table names each CAP radio by the controller's copy of it (WAP-5Ghz). The client list, client detail, the AP density chart and the topology map put the client on the CAP that radio lives on, on the CAP's own interface for it (wifi2_5Ghz), with the CAP's way up as its connection path. A client on a virtual AP, such as a guest SSID, moves to the CAP too and keeps the controller's interface name. If the CAP isn't a managed device, the client stays on the controller.

A controller with radios of its own (controller_cap) is listed with its own clients. Its copies of its CAPs' interfaces hold the CAPs' clients, and those are counted on the CAPs.

A controller with no radios of its own isn't an access point. It has its own section on the Wireless page, and isn't counted in Total APs or listed in the Access Points table. In Channel Usage, the controller's copy of a CAP radio is left out when the CAP is a managed device, since the CAP's own entry shows that radio. If the CAP isn't managed, the copy is the only view of that radio, so it stays, grouped under its controller.

Write protection

A provisioned radio is owned by the controller, so a local write to it is either rejected outright or silently replaced at the next provision — while the API reports success.

Five paths refuse or skip provisioned radios, naming the controller in the error: bulk SSID deployment, interface create, interface edit, interface delete, and guest network setup.

Set up CAPsMAN

Set up CAPsMAN on the Wireless page makes a device a controller with one SSID, on both bands or one, from Ron's request in #438. Choose the device, then enter:

  • the SSID and password (WPA2, plus WPA3 on wifi);
  • the bridge Wi-Fi clients join, on the controller and on every AP, so each AP needs a bridge with this name;
  • the country, optional, as RouterOS names it (united states);
  • the radios: 2.4 GHz and 5 GHz, 2.4 GHz only or 5 GHz only. With both, tick A different SSID on 5 GHz to give 5 GHz radios a name of their own, with the same password;
  • the role: Controller and AP, where its own radios broadcast the SSID too (legacy CAPsMAN only, see below), or Controller only.

It works on either CAPsMAN, and asks which when the device has both. A wifi controller only manages wifi-package APs, and a legacy one only legacy wireless APs.

What it does on the device:

Step wifi legacy
A configuration named mtm-capsman with the SSID, password and bridge /interface wifi configuration /caps-man configuration, with local forwarding
A provisioning rule, commented mtm capsman, that gives it to every radio, or one band's /interface wifi provisioning, matching supported-bands /caps-man provisioning, matching hw-supported-modes
A different SSID on 5 GHz only: a second configuration, mtm-capsman-5ghz, and rule, commented mtm capsman 5ghz, for 5 GHz radios; the first rule then takes 2.4 GHz the same menus the same menus
CAPsMAN on /interface wifi capsman /caps-man manager
Controller and AP only: its own CAP, pointed at 127.0.0.1 (not offered) /interface wireless cap, with the chosen band's wlans

Running it again on the same device changes the same items. Leave the password empty to keep the one set. Switching to Controller only turns its own CAP off, and its radios go back to their own settings. The change runs under Change Guard, and Review changes shows the writes first.

  • Other APs join by turning on their CAP, with discovery on the same network. The wizard doesn't change them.
  • RouterOS uses the first provisioning rule that matches a radio. With both bands, rules the device already has come before the new one, and the form says so. With one band, the new rule goes first, so that band's radios take the SSID and the other band's go on matching the rules already there. That way you can try a 5 GHz network without touching the 2.4 GHz one.
  • With one band and Controller and AP on legacy CAPsMAN, only the device's own wlans of that band join the controller. The other band's wlans keep their own settings.
  • With a different SSID on 5 GHz, both rules go before the device's own. Unticking it, or choosing one band, removes the 5 GHz rule and configuration again.
  • RouterOS applies provisioning rules when a radio joins. On legacy CAPsMAN, when the rules change, the setup provisions the radios that have already joined again, so they take the new SSID; their clients reconnect. On wifi CAPsMAN, access points that have already joined take the new rules when they next connect.
  • A legacy controller that also serves its own radios counts them as its own on the Wireless page, clients included, and Wireless Settings marks those wlans CAPsMAN with the SSID the controller puts on the air.

Current limits

On wifi CAPsMAN, the controller doesn't serve its own radios. A wifi controller can't manage its own radios through its own CAP (MikroTik's wifi documentation says so). RouterOS only offers one way to provision them, /interface wifi radio provision. That replaces each radio's own settings, its virtual APs included, and they don't come back when the rule goes: on a test wAP ax, they had to be rebuilt from a backup. So the wizard only offers Controller only on wifi. To put the controller's own radios on the SSID, set them by hand. Other APs join as usual, and legacy CAPsMAN isn't affected.

Editing an existing controller's provisioning, configurations and interfaces isn't offered, apart from the setup above. A CAPsMAN configuration applies to every access point bound to it simultaneously — the fleet-wide version of the failure Change Guard exists to prevent.

Legacy CAPsMAN

The original CAPsMAN (/caps-man, from the wireless package) is supported too (#250). Older 802.11n and 802.11ac wave 1 access points (RB951, hAP ac lite, cAP ac and similar) can only be CAPs of this one, often managed from a CHR.

  • Controller: a device with /caps-man manager enabled is a controller, even when it also has the newer wifi menu, as every RouterOS 7.24 device does. A controller can run both CAPsMANs at once (newer APs on one, legacy APs on the other); both are read, and their radios and clients are listed together.
  • Radios and APs: read from /caps-man interface and matched to access points by MAC, the same way as the newer CAPsMAN. The Wireless page and the CAPsMAN panel show them without any difference.
  • Clients: under legacy CAPsMAN only the controller lists the clients (/caps-man registration-table); the access point's own table stays empty. They're read from the controller with their signal, traffic and last known address, named by the comment given to them there when DHCP doesn't name them. A client on one of a managed access point's radios is shown on that access point. One on a virtual interface, or on an access point that isn't managed, is shown on the controller.
  • The CAP: an access point whose /interface wireless cap is enabled is a CAP. The interfaces it hands to the controller are marked as managed by CAPsMAN and show the SSID from the controller rather than the AP's own, unused settings.

Devices classified before this was added are checked once more, so an existing legacy controller is found after upgrading.

Developed against the #250 reporter's CHR and RB951Ui-2HnD output (RouterOS 7.24.5). It hasn't been run against RouterOS 6.

Roaming history

A client's association history is reconstructed from access point logs at GET /api/clients/:mac/roaming?range=24h, and shown on the client detail page.

Roaming happens between polls, so a poll-based view can never see it — the log is the only record that a client moved, when, and at what signal. Sessions are rebuilt from RouterOS's own lines, including every band or AP change and the disconnect reason.

Sessions with six or more roams per hour are flagged. A client bouncing between radios usually indicates roaming thresholds rather than a faulty client: overlapping cells at similar signal give it no reason to prefer one.

Nothing new is collected — this reads the events already gathered, so it works retroactively over whatever log history exists. It does require association logging to be enabled on the access points.