I’ve documented my struggles here: http://forum.mikrotik.com/t/how-to-get-consistent-interface-naming-with-capsman3/172740/1
i’m also of the opinion that this is something worth fixing
A- Interfaces “wifi1” and “wifi2” keep their local names (but become dynamic, and loose their previous index on /bridge, suggesting they are deleted and re-created with the same name)
B- Slave interfaces local to the controller are created with “MikroTik” prefix on first boot, and “Identity” on second boot (using %I wildcard)
C- on remote CAPs, the zeroth interface (master) has no numeric suffix, but the slaves have, making reading difficult (slaves count from 2)
Some of these could probably be mitigated with more wildcards:
%band would be interesting (unifying the provision for multi-band setups, good for future-proofing)
%SSID or %VLAN would also be very useful
mostly, i’d like a consistent naming scheme so that i can follow a station on capsman/registration without loosing my mind