Ethernet aggregation + vlan - bonding vs bridge?

Hi,

we are changing topology of our networki, moving our centre to the cloud. So at the main company location, we will terminate Fortigate and move to CCR, as other 10+ branches already do.

In our network, we have 2 core switches, which are connected to FG, using an Aggregate functionality, which is 802.3ad interface. Upon that, one VLAN for wi-fi guests is created.

Moving to Mikrotik - we have CCR2116 for our location available. I could create 802.a3 using a bonding interface, which I never used though, and just wondering, what would be the benefit in comparison to just creating a bridge and putting those two ethernet ports there, plus adding a VLAN for the wi-fi guests upon the bridge itself?

Any suggestions?

Thanks,
/Petr

If you simply create bridge and add two interfaces, then those two interfaces will be consideted independent (connecting to two independent devices). With RSTP enabled (default setting on bridge) loop will likely be detected and one of links will be blocked.

If the same two interfaces are made members of same 802.3ad bond, they will be used as aggregate (and redundant) links … because they will be parts of single logical link between two devices.