Very disapointed with this behavior… All external devices can freely connect to CAP-Manager, but internal WiFi-interface must done workaround prior to connect to own CAPsMan.
I’m using 6.49.7 with internal LAN bridge (br-lan, 192.168.30.1) and none of above advices does not help me. Here are two rules that really help me to accomplish this quest:
add action=accept chain=input comment="Capsman local" protocol=udp src-address=192.168.30.1 src-port=5246,5247
add action=accept chain=input dst-port=5246,5247 protocol=udp src-address=192.168.30.1