Clients unable to connect to Wifi managed by Capsman

I’m new to RouterOS and love its capabilities - but for the heck I don’t find the reason why this won’t work (anymore).

I would love to hear any input on my issue!

Strangely all worked perfectly until the FireTV-stick couldn’t connect anymore to the Capsman managed 5Ghz Wifi and during my attempts to get it working again all just got to this point.

Problem: Clients can connect to unmanaged, local Wlan on AP (get IP, can access network/WAN), but not to Wlan managed by Capsman (provided by same AP). Apparently the AP clients don’t get an IP in the Wlan managed by Capsman.

My configuration:
Router (hp ac3) ethernet5 connected to ethernet1 of AP (cap ac).

Config Router: pretty standard configuration with bridge on ethernet2-5 and wlans, dhcp-server running on this bridge

Config AP: I guess not so standard configuration - I want that the AP does not operate its own DHCP-Server but obtains IPs from the Router for its clients. So that there is one IP-range covering the whole network of the router and the AP and all clients can see eachother.

Therefore, I modified the defconf defined bridge on the AP (originally covers ethernet2 and wlans) to include ethernet1, disable the Firewall rules that limit traffic to/from ethernet1 and disabled the default configured DHCP-Server of the bridge. In IP-Adresses, the 192.168.88.1 address is disabled for the AP (so to not collide with the router which sits at this address).

With this configuration, clients can connect to the unmanaged wlan provided by the AP, but not to the Capsman managed Wlan. For the CAPsman managed Wlan the clients don’t get an IP.

More strange things - in Capsman of the router, in tab Remote Cap, no IP address is shown for the AP - only its MAC address. In the leases of the DHCP-server of the router, the AP shows an IP. The AP is also reachable at this IP.

More strange things #2: In the router log I see following error: “removing stale connection [IP of AP] because of ident conflict with [MAC of IP]”

More strange things #3: in the AP log files I see an error from the DHCP-client saying “temporary moving client ether1 from slave to master port, update your config!!!”. However, I cannot find anything on how to change that.

Router OS 6.47.7 on both Router and AP.
Capsman configured following “Manual:Simple CAPsMAN setup” with only one 5GHz Wifi SSID defined for now.

I just changed in the CAP settings of the AP the discovery interface from “bridge” to ethernet1 - now the wifi clients don’t see even the SSID of the capsman managed wlan provided by the AP anymore (but in capsman now the IP of the AP is shown in remote Cap tab instead of its MAC only).

And suprise - all works now!

Why?

Apparently changing the configuration takes a long, long time to transverse my network (although it’s small) and get fully applied in the AP.

A lot longer than clicking apply/ok and doing a test a few moments later.