I've been banging my head against the wall on this one for a few days now and hopefully someone can help me shed some light on it. Long story short, I'm running Mikrotik 6.13 as a VM ontop of a VMWare ESXi host machine. This setup works great except for one issue: bridging doesn't seem to work.
A quick summary of what I've done: I've used the VMWare network manager to create 2 virtual switches and connected both to two interfaces on the Mikrotik VM. I've then created two ubuntu VMs and connected each to one switch. In the Mikrotik I've created a bridge and added both interfaces and assigned the bridge an IP address of 172.16.31.3/24. One of my VM's has an IP 172.16.31.1/24 and the other has 172.16.31.2/2. When I bring up all interfaces the VM's cannot ping each other. One of the two VM's can ping the Miktotik but not the other one. If I disable the working interface on the Mikrotik then suddenly the other VM can ping the Mikrotik. If I disable the bridge both VM's can ping the Mikrotik but obviously not each other. Here's some of the output from my Mikrotik:
[admin@MikroTik] > /interface bridge print
Flags: X - disabled, R - running
0 R name="test_bridge" mtu=1500 l2mtu=65535 arp=enabled
mac-address=00:0C:29:74:9A:81 protocol-mode=none priority=0x8000
auto-mac=yes admin-mac=D4:CA:6D:6F:9A:F9 max-message-age=20s
forward-delay=15s transmit-hold-count=6 ageing-time=5m
[admin@MikroTik] > /interface bridge port print
Flags: X - disabled, I - inactive, D - dynamic
INTERFACE BRIDGE PRIORITY PATH-COST HORIZON
0 ether2 test_bridge 0x80 10 none
1 ether1 test_bridge 0x80 10 none
[admin@MikroTik] > /interface bridge host print
Flags: L - local, E - external-fdb
BRIDGE MAC-ADDRESS ON-INTERFACE AGE
test_bridge 00:0C:29:07:4F:5E ether1 0s
test_bridge 00:0C:29:51:14:8A ether2 1m47s
L test_bridge 00:0C:29:74:9A:77 ether2 0s
L test_bridge 00:0C:29:74:9A:81 ether1 0s
Hopefully someone can shed some light on this.