Hi, i'm planning a new install with a Hap-AX3 as a cap-controller, and several Cap-AX's as cap-managed AP's

I have the provisioning name-format set to "name-format=%I", so that i know where the stations are, when they roam
( 4 total SSID's, Infrastructure/management/staff and guests), on different vlans
there are therefore, 8 "interfaces" per CAP, 4 per radio.

but the naming is highly inconsistent::

-- in the HAP, interfaces "wifi1" and "wifi2" (master) become "dynamic", and can't be changed back to unmanaged (?)
-- the slave interfaces are named with "MikroTik" prefix, inconsistent with the master naming, and the numeric suffix is (-2) from the other cap's, and omitted/implicit index "1"
-- in the remote cap's, interfaces are named "Identity"+(NULL|2|3|4) for the 5ghz interfaces, and "Identity"+(5|6|7|8) for the 2,4ghz interfaces

#highly unintuitivelly, as one master interface has no numeric suffix, and the other one does (in a kind of reverse order of bands, which is weird in and on itself)
[edit] -- they really assume random names when reprovisioning, as sometimes the 2ghz interface gets reprovisioned before the 5ghz one. CHAOS!


in the remote cap's themselves, after multiple rounds of provisioning, the slave interfaces get ever higher indexes (wifi21,wifi22,wifi23....), but the master ones keep their original wifi1 and wifi2

so, aside from manually setting all interfaces, and ditching the whole point of a centrally managed system;

how can this be improved, in order to provide a more sane naming structure?

am i missing something in the config part, or this is strictly "feature request" territory?

adding some pictures to illustrate: << note that sometimes the radios are provisioned in reverse order.

Please show provisioning rules, so we can some with some suggestions / possible workarounds regarding the naming.

Regarding this:
"in the HAP, interfaces "wifi1" and "wifi2" (master) become "dynamic", and can't be changed back to unmanaged (?)" -> the only way I found working is to disable CAP (but is not enough) and then to remove remote CAP, and sometimes even this is not enough, then to temporary disable provisioning rules, then click provision on this local radios, and they will come back as normal.

Please show provisioning rules, so we can some with some suggestions / possible workarounds regarding the naming.

very basic using %i for prefixing with cap-name, and "-" for readability