Routing works on wlan1 but not a Bridge

here is the strange problem:
I use my Mikrotik as wireless client: DHCP client on wlan1, route traffic with routing mark WiFi to wlan1, masqurate rule has out interface as wlan1. Works fine.

when I created a Bridge WLAN, which include wlan1 and ether 2,then change DHCP client to be on WLAN, masqurate chagned out interface to WLAN, routing did not need change as I use IP 192.168.0.1 as Gateway (which is my 4G modem)

Problem:
I can no longer ping the the gateway 192.168.0.1 from the router, yet the Route shows 192.168.0.1 is reachable via WLAN

Test:
if I disable ether4 from the Bridge, it started work again.

background:
ether 4 has no IP address assigned to it and it is not a slave port.

I’ve tested the same configuration (both wlan1 and ether4 in WLAN Bridge) but instead of connecting to the 4G modem, I connect to another Mikrotik Access Point, works fine.
I am confused.

New discovery:
when ether4 is enabled, 192.168.0.1 is not in APR table, as soon as ether 4 is disabled, I can see an entry for 192.168.0.1

That explains the problem but why would APR table beehive this way? Bridge WLAN has ARP enabled, so are wlan1 and ether4.

Check this:

https://wiki.mikrotik.com/wiki/Manual:Wireless_Station_Modes

In short, standard wireless doesn’t like bridging very much.