Problem in Bridging with Bonding of EOIP tunnel

RouterOS General
1

Very simple setup, two CHR 6.38.5 in Virtualbox environment named Guest1 and Guest2, both with 3 interfaces:
ether1 - simulating ISP1
ether2 - simulating ISP2
ether3 - simulating LAN

all interfaces are connecting to internal networks only (no interface with host network)

Network Connections:

Guest1 Guest2
ether1 -------ISP1-------------ether1
ether2--------ISP2-------------ether2
ether3 ether3

created two EOIP tunnel, “eoip-tunnel1” over ether1 on both guest and “eoip-tunnel2” over ether2 on both guest.
created a bond “bonding1” over two EOIP tunnels.
created a bridge “bridge1” over “bonding1” and “ether3”

Problem: when bridge1 covered ether3 only, a virtual PC connecting to ether3 could ping to the guest. However, when the bonding1 added to bridge1, no reply for ping.
Findings: when I added address to bonding1 at both guest, say 192.168.255.1/30 and 192.168.255.2/30, I can ping from one guest to the bonding interface on the opposite guest.

Below is the config (very simple)
Guest 1:

/interface bridge
add name=bridge1
/interface eoip
add !keepalive mac-address=02:CF:B7:AC:38:F7 name=eoip-tunnel1 \
      remote-address=10.0.0.2 tunnel-id=0
add !keepalive mac-address=02:D2:DE:13:36:0C name=eoip-tunnel2 \
      remote-address=10.0.1.2 tunnel-id=1
/interface bonding
add name=bonding1 slaves=eoip-tunnel1,eoip-tunnel2
/interface bridge port
add bridge=bridge1 interface=ether3
add bridge=bridge1 interface=bonding1
/ip address
add address=192.168.88.1/24 interface=bridge1 network=192.168.88.0
add address=10.0.0.1/24 interface=ether1 network=10.0.0.0
add address=10.0.1.1/24 interface=ether1 network=10.0.1.0
add address=192.168.255.1/30 interface=bonding1 network=192.168.255.0

Guest 2:

/interface bridge
add name=bridge1
/interface eoip
add !keepalive mac-address=02:FE:46:73:47:48 name=eoip-tunnel1 \
      remote-address=10.0.0.1 tunnel-id=0
add !keepalive mac-address=02:F0:ED:5F:89:0C name=eoip-tunnel2 \
      remote-address=10.0.1.1 tunnel-id=1
/interface bonding
add name=bonding1 slaves=eoip-tunnel1,eoip-tunnel2
/interface bridge port
add bridge=bridge1 interface=ether3
add bridge=bridge1 interface=bonding1
/ip address
add address=192.168.89.1/24 interface=bridge1 network=192.168.89.0
add address=10.0.0.2 interface=ether1 network=10.0.0.0
add address=10.0.1.2/24 interface=ether1 network=10.0.1.0
add address=192.168.255.2/30 interface=bonding1 network=192.168.255.0
2

Alright, I answer it myself! :laughing:
As inspired by the DHCP problem as mentioned in this post http://forum.mikrotik.com/t/ros-6-38-serious-dhcp-server-problem/105259/1
I suspected the same problem happened in this scenario.

BINGO! same STP problem also applied here and I resolve it by adding the admin-mac attribute to the “bridge1”, all the things solved at once.

It seems that the STP problem introduced in 6.38 interfere the RouterOS in many aspects. :confused: