about port eoip-tunnel and port forwarding b310s-22

hello I want to do tunnel between 2 place with mikrotik
but one microtik work with internet 4g b310s-927
the secand with modem dsl bridge the password ppp in mikrotik

but not work
i work this in 1st mikrotik

/interface bridge
add name=bridge1
/interface ethernet
set [ find default-name=ether5 ] name=lan1
set [ find default-name=ether2 ] name=lan2
set [ find default-name=ether3 ] name=lan3
set [ find default-name=ether4 ] name=lan4
set [ find default-name=ether1 ] name=wan1

/interface eoip
add !keepalive local-address=192.168.8.102 mac-address=02:E0:8C:58:AC:95 name=
eoip-tunnel1 remote-address=*.sn.mynetname.net tunnel-id=100
/interface list
add name=WAN
add name=LAN
/ip pool
add name=dhcp ranges=192.168.0.100-192.168.0.250
/ip dhcp-server
add address-pool=dhcp disabled=no interface=bridge1 lease-time=1d10m name=dhcp1
/tool user-manager customer
set admin access=
own-routers,own-users,own-profiles,own-limits,config-payment-gw
/interface bridge port
add bridge=bridge1 interface=lan1
add bridge=bridge1 interface=lan2
add bridge=bridge1 interface=lan3
add bridge=bridge1 interface=lan4
add bridge=bridge1 interface=eoip-tunnel1
add bridge=bridge1 interface=wan1
/ip neighbor discovery-settings
set discover-interface-list=all
/interface list member
add interface=wan1 list=WAN
add interface=lan2 list=LAN
add interface=lan3 list=LAN
add interface=lan4 list=LAN
add interface=lan1 list=LAN
/ip address
add address=192.168.0.254/24 interface=bridge1 network=192.168.0.0
add address=192.168.8.101/24 interface=wan1 network=192.168.8.0
/ip cloud
set ddns-enabled=yes
/ip dhcp-client
add dhcp-options=hostname,clientid disabled=no interface=bridge1
/ip dhcp-server network
add address=192.168.0.0/24 dns-server=8.8.8.8,8.8.4.4 gateway=192.168.0.253
netmask=24
/ip dns
set servers=8.8.8.8,8.8.4.4
/ip firewall nat
add action=masquerade chain=srcnat comment=“masquerade hotspot network”
src-address=192.168.0.0/24
add action=masquerade chain=srcnat out-interface-list=WAN
/ip route
add check-gateway=ping distance=1 gateway=192.168.8.1
/





in the secand mikrotik


/interface pppoe-client
add interface=wan2 keepalive-timeout=disabled max-mtu=1500 name=pppoe-out1
password=3
0 user=03
0

/interface eoip
add !keepalive mac-address=02:52:2E:B7:3F:56 name=eoip-tunnel1 remote-address=
************.sn.mynetname.net tunnel-id=100

ip dhcp-server
add disabled=no interface=bridge2 lease-time=1d10m name=dhcp2

add bridge=bridge1 hw=no interface=local1
add bridge=bridge2 interface=eoip-tunnel1

Are you sure that the WAN IP addresses of both Mikrotiks are not only public but also reachable from the internet? I’ve seen mobile internet providers assigning public IPs to clients but nevertheless NATing them to other public IPs, so the ones assigned to clients were unreachable from outside. The Mikrotik cloud DDNS registers the IP from which the update request has actually arrived, but that does not mean that such address is used to NAT only a single client, so even if the LTE client sends GRE packets out, the return path may not be open on the NAT (as two GRE connections between the same two addresses cannot be distinguished from one another because GRE doesn’t use port numbers). Try to run /tool sniffer quick interface=your-pppoe-interface-name ip-protocol=gre on the machine with pppoe, can you see the GRE packets come in from the public IP you can see on the LTE WAN of the other Mikrotik or from another one?