bridge vlan (legacy mode) setup doesn't work - please help

This setup was working well before replacing an HEX GR3 with an HEX lite in a real world scenario, then I reproduced the environment with Virtualbox and CHRs, that desn’t work as well.
This is a schema of the configuration (I hope enough clear):
Screenshot-20201114155849-821x458.png
Obviously, I would like to get one broadcast domain for network 192.168.151.0/24 and one for 192.168.152.0/24 but the ping fails.
On the “rbISP” side, only in the real world scenario:
I’m able to ping ispbox1 before adding vlan151 interface on bridgeisp1
I’m able to ping ispbox2 before adding vlan152 interface on bridgeisp2

I’m sure, I’m missing some configuration hint on the bridge to make it work.
Replacing the two VLAN with two EoIP tunnels the setup works perfectly, but my idea is that EoIP produces a protocol overhead much bigger.

Thanks for your help.

I’m also posting rbISP and rbMAIN configurations:

RBISP

# nov/14/2020 15:35:52 by RouterOS 6.46.8
# software id = 
#
#
#
/interface bridge
add name=bridgeisp1
add name=bridgeisp2
add name=bridgeisptrunk
/interface ethernet
set [ find default-name=ether1 ] name=ether1main150
set [ find default-name=ether2 ] name=ether2isp151
set [ find default-name=ether3 ] name=ether3isp152
/interface eoip
add mac-address=02:8B:38:25:DC:A2 name=eoip-tunnel151 remote-address=192.168.150.2 tunnel-id=151
add mac-address=02:92:67:B2:A4:38 name=eoip-tunnel152 remote-address=192.168.150.2 tunnel-id=152
/interface vlan
add interface=bridgeisptrunk name=vlan151 vlan-id=151
add interface=bridgeisptrunk name=vlan152 vlan-id=152
/interface wireless security-profiles
set [ find default=yes ] supplicant-identity=MikroTik
/interface bridge port
add bridge=bridgeisp2 interface=ether3isp152
add bridge=bridgeisp1 interface=ether2isp151
add bridge=bridgeisptrunk interface=ether1main150
add bridge=bridgeisp1 interface=vlan151
add bridge=bridgeisp2 interface=vlan152
/ip neighbor discovery-settings
set discover-interface-list=all
/ip address
add address=192.168.152.2/24 interface=bridgeisp2 network=192.168.152.0
add address=192.168.151.2/24 interface=bridgeisp1 network=192.168.151.0
add address=192.168.150.1/24 interface=bridgeisptrunk network=192.168.150.0
/ip dhcp-client
add interface=ether1main150
/ip dns
set servers=192.168.152.1
/ip route
add distance=1 gateway=192.168.152.1
/system identity
set name=rbisp
/system package update
set channel=long-term

rbMAIN

# nov/14/2020 15:38:16 by RouterOS 6.46.8
# software id = 
#
#
#
/interface bridge
add name=bridgeisp1
add name=bridgeisp2
add name=bridgeisptrunk
add name=bridgelan
/interface ethernet
set [ find default-name=ether1 ] name=ether1isp
set [ find default-name=ether2 ] name=ether2lan
/interface eoip
add mac-address=02:00:E5:BB:7E:5E name=eoip-tunnel151 remote-address=192.168.150.1 tunnel-id=151
add mac-address=02:44:36:87:F7:7C name=eoip-tunnel152 remote-address=192.168.150.1 tunnel-id=152
/interface vlan
add interface=bridgeisptrunk name=vlan151 vlan-id=151
add interface=bridgeisptrunk name=vlan152 vlan-id=152
/interface wireless security-profiles
set [ find default=yes ] supplicant-identity=MikroTik
/interface bridge port
add bridge=bridgelan interface=ether2lan
add bridge=bridgeisptrunk interface=ether1isp
add bridge=bridgeisp1 interface=vlan151
add bridge=bridgeisp2 interface=vlan152
/ip neighbor discovery-settings
set discover-interface-list=all
/ip address
add address=192.168.88.1/24 interface=bridgelan network=192.168.88.0
add address=192.168.150.2/24 interface=bridgeisptrunk network=192.168.150.0
add address=192.168.151.3/24 interface=bridgeisp1 network=192.168.151.0
add address=192.168.152.3/24 interface=bridgeisp2 network=192.168.152.0
/ip dhcp-client
add interface=ether1isp
/system identity
set name=rbmain

If the configuration was unchanged between the original hEX Gr3 and hEX lite the most likely cause is the different MAC addresses changing the spanning tree topology - try setting protocol-mode=none on all of the bridges. This is one of the issues discussed here https://wiki.mikrotik.com/wiki/Manual:Layer2_misconfiguration

As the legacy method does not use hardware switching the recommended approach would be to reconfigure with a single VLAN-aware bridge.