WIFI networking crashes after change to AX device

So far I used a cAP ac to which a mAP light was connected via a “station bridge” as a “wireless cable”.
Now the cAP ac was swapped for a cAP ax.
Yes, I read the note late but that “station bridge” doesn’t work between wifiwave2 and wireless devices, so far OK.

But now a completely new problem arises as soon as the mAP connects as a simple station or station-pseudobridge to “funkfeuer-IoT” wifi. From this point on, no other client connected to the wifi network will receive a DHCP lease from the server in front of it.
As soon as the mAP is excluded from the network, everything works perfectly again.
mAP and cAP have the latest ROS in version 7.14.2

cAP ax:

/interface bridge
add name=bridge1 vlan-filtering=yes
/interface vlan
add interface=bridge1 name=vlan100 vlan-id=100
/interface wifi security
add authentication-types=wpa2-psk,wpa3-psk disabled=no name=WPA-funkfeuer
add authentication-types=wpa2-psk,wpa3-psk disabled=no name=WPA-gast
add authentication-types=wpa2-psk,wpa3-psk disabled=no name=WPA-IoT
/interface wifi
set [ find default-name=wifi2 ] channel.band=2ghz-ax .frequency=2412 .width=20/40mhz configuration.mode=ap .ssid=funkfeuer disabled=no security=WPA-funkfeuer
add configuration.mode=ap .ssid=funkfeuer-IoT disabled=no mac-address=D6:01:C3:01:47:DA master-interface=wifi2 name=wifi2-IoT security=WPA-IoT
add configuration.mode=ap .ssid=funkfeuer-gast datapath.client-isolation=yes disabled=no mac-address=D6:01:C3:01:47:DB master-interface=wifi2 name=wifi2-gast security=WPA-gast
set [ find default-name=wifi1 ] channel.band=5ghz-ax .frequency=5180 .width=20/40/80mhz configuration.mode=ap .ssid=funkfeuer disabled=no name=wifi5 security=WPA-funkfeuer
add configuration.mode=ap .ssid=funkfeuer-gast datapath.client-isolation=yes disabled=no mac-address=D6:01:C3:01:47:DB master-interface=wifi5 name=wifi5-gast security=WPA-gast
/interface bridge port
add bridge=bridge1 frame-types=admit-only-vlan-tagged interface=ether1
add bridge=bridge1 frame-types=admit-only-untagged-and-priority-tagged interface=wifi2 pvid=100
add bridge=bridge1 frame-types=admit-only-untagged-and-priority-tagged interface=wifi5 pvid=100
add bridge=bridge1 frame-types=admit-only-untagged-and-priority-tagged interface=wifi2-gast pvid=200
add bridge=bridge1 frame-types=admit-only-untagged-and-priority-tagged interface=wifi5-gast pvid=200
add bridge=bridge1 frame-types=admit-only-untagged-and-priority-tagged interface=wifi2-IoT pvid=100
/interface bridge vlan
add bridge=bridge1 tagged=bridge1,ether1 vlan-ids=100
add bridge=bridge1 tagged=ether1 vlan-ids=200
/ip address
add address=192.168.1.26/24 interface=vlan100 network=192.168.1.0
/ip dns
set servers=192.168.1.1

Yes, the IoT wifi also temporarily has VLAN id 100.

mAP light:

/interface bridge
add name=bridge1
/interface wireless security-profiles
set [ find default=yes ] supplicant-identity=MikroTik
add authentication-types=wpa2-psk mode=dynamic-keys name=WPA-IoT \
    supplicant-identity=""
/interface wireless
set [ find default-name=wlan1 ] band=2ghz-b/g/n disabled=no mac-address=\
    6C:3B:6B:F5:7F:4E name=wlan2 radio-name=HOME_mAP_Solar security-profile=\
    WPA-IoT ssid=funkfeuer-IoT
/interface bridge port
add bridge=bridge1 interface=ether1
add bridge=bridge1 interface=wlan2
/ip address
add address=192.168.1.28/24 interface=bridge1 network=192.168.1.0
/ip dns
set servers=192.168.1.1
/ip route
add disabled=no dst-address=0.0.0.0/0 gateway=192.168.1.2 routing-table=main \
    suppress-hw-offload=no

Am I making a mistake somewhere that caused the wifi with mAP to crash?

I face this very same issue. I assume it’s because of station-pseudobridge causing a loop detection. Maybe try protocol-mode=none on your cap ax bridge.

This seems to work, but it doesn’t make sense to have to deactivate a security mechanism because of it.
Please Mikrotik, take a look.