It’s also been months not hearing from you too.
True, can’t comment anything when there’s nothing new to share…
I confirm, there is NO DYNAMIC entry when using CapsMan2.
It only affects profiles with EAP authentication.
MT support finally responded and confirmed that no steering group is automatically created if EAP is used as a authentication mechanism:
That being said, regarding the original query. Feedback from developers currently is as follows:
Dynamic neighbor groups are automatically created while using PSK, if the same SSID and PSK are used, these attributes tell us that interfaces have the same connection requirements, since we have this information, RouterOS can create a dynamic group for this scenario, for these specific interfaces.
In the case of EAP, currently, it’s not possible to create automatic neighbor groups, since there are no comparable attributes that would guarantee that the connection requirements are the same in all cases. Which, unfortunately, means that the network administrator needs to specify that interfaces are part of the same group.
We might investigate in the future, if we can find some workaround that would allow dynamic neighbor steering groups for EAP, but currently, I can’t give any guarantees regarding that.
I asked them to add some information to the documentation, which they did right away: https://help.mikrotik.com/docs/display/ROS/WiFi#WiFi-Steeringproperties