Sonos bridge RX looped packet.

I have some Sonos units, only one is hard wire connected to the net, so Sonos build it's own mesh net. All running ok.

If i hard wire two Sonos unit, in a simple L2 switch all is still ok.
If i hard wire two Sonos init in two ports in the MT then all problem start.
I have seen a lot with the same problem on ASUS, TP-Link, and other routers too. So not a MT problem.

Error is: bridge RX looped packet - MAC d8:f4:e3:88:09:66 -> ff:ff:ff:ff:ff:ff VID 20 ETHERTYPE 0x0806

I think it is a L2 problem, any hints?

The problem is that Sonos mesh obviously doesn’t care about hetwork loops (neither do unmanaged switches). All managed switches know about xSTP (most have it enabled by default) and those can block one of links creating a loop.

Maybe i misunderstand you, because all work when using the switch.
Only not working when connecting to MT in 2 hardware port. Both port is member on the switch chip in MT, so why is that a problem when it work on a simple switch?

The simple switch may (or may not) use a different loop prevention method (or none at all).
The Mikrotik switch may ( or may not) run STP or RSTP or something else:
https://www.geeksforgeeks.org/difference-between-spanning-tree-protocol-stp-and-rapid-spanning-tree-protocol-rstp/

You could try disabling those (if running) and see what happens.

try configuring spanning tree on mikrotik, and make sure your mikrotik switch has the priority. see: https://support.sonos.com/en-us/article/configure-stp-settings-to-work-with-sonos

I had similar issues until I applied the guidance on mikrotik bridge side of things.