Mosaic does not connect to Bartok

Support
13

Warren, it’s hard to tell what might have broken, but looks like you changed quite a few things in your network.

My suggestion is to put everything back to how it was, reboot everything and get it back to a working condition. From there, change one thing at a time, ensuring that everything works step by step.

I suspect you have some very basic cable or physical connectivity issue (as is often the case when folks change many things at once), rather than anything systemic (albeit, EtherRegen is a slightly weird piece of kit that may cause funky problems :grin:)

Not quite actually. Mosaic’s discovery of the dCS components is not based on UPnP discovery.

Here’s how it works (based on the last time I looked closely at Mosaic-to-dCS component discovery), it’s quite simple;

(In a freshly rebooted system)

  1. The dCS component issues multiple Multicast join request (to multiple multicast addresses) to ensure it sees all relevant Multicast queries
  2. When launched, Mosaic issues an mDNS service discovery query out onto the local network
  3. Any dCS component on the local network that sees this mDNS query will respond with an mDNS response
  4. With that response, Mosaic learns the IP address of the dCS component and issues an ARP request (to learn the MAC address of the dCS component)
  5. The dCS component responds directly to the ARP request, from which point the two are off to the races.

In a non-freshly booted system, one or both of these (mDNS and ARP) steps may not be necessary, for example, the MAC address of the dCS component may already be in the ARP cache of the Mosaic platform.

When folks add network elements between Mosaic and the dCS component, it could break either mDNS or ARP, which will then prevent Mosaic from discovering the dCS component.

ARP is usually pretty robust across multiple layer 2 segments, so, it’s not usually the problem, but mDNS which is built on Multicast UDP packets sent out on address 224.0.0.251, could be relatively easily broken across dodgy network elements :laughing:

ps:

Just for kicks I did a Google search of Eero and multicast, here’s what came back;

But according to Pixel Magic, eero does not forward all multicast packets without dropping, causing failures in multicast based discovery used in Lumin and Roon.

I do know there are others here on dcs.community using Eero without problems, but be very careful when adding possibly dodgy network elements between Mosaic and your dCS component :stuck_out_tongue_winking_eye:

2 Likes