Etherdreams not found on 1.03

Support
1

Has anyone had issues with Etherdreams not being found on the network with the new 1.0x releases? I’m able to ping my ED4s and I kept it a basic flat network no vlans and a /24.

I launched 0.9.9 B9 and instantly saw all the EDs and just used that build for the show.

2

I have no more connection issues lately (i did on older versions)

i would check firewall settings first…

3

Got a wide open firewall, and did a wireshark/traceroute has solid communication

4

Hi Nils,

The Ether Dream discovery mechanism hasn’t changed between 0.9.9 B9 and 1.0.x. The communication layer has been updated internally, but device discovery itself is the same.

Since 0.9.9 instantly sees your ED4s on the same machine and network, this strongly suggests a macOS permissions issue rather than anything to do with VLANs or subnetting.

On macOS, check:

System Settings → Privacy & Security → Local Network

Make sure Liberation 1.0.x is enabled there. macOS treats new builds as separate apps, so 0.9.9 can be allowed while 1.0.x is silently blocked from receiving local UDP broadcast traffic. Ping and Wireshark can still work in that situation, which makes it confusing.

If Liberation 1.0.x isn’t listed there at all, try deleting it, re-downloading, and launching it again so macOS prompts you for local network access.

Let me know what you find.

Seb

5

Hi Seb,

I agree that seems correct. I had the same issue last Sat at an event. I reverted back to 099B9 and that worked well, except for atleast half the 4hour show I noticed it dropping out every 40-90sec or so for a few seconds. Exactly like I’ve seen it act before when I am trying to control ED4s via wifi.

It looks like 1.0.x was not in the local network access, I have 6 099B9 versions in there though. Deleted 1.0.3 and redownloaded the dmg. Nothing though :confused:

6

Hi Nils,

The dropouts every 40–90 seconds sound like a network stability issue rather than anything version-specific. Whenever I’ve had that behaviour it’s turned out to be a bad network cable, network device, or mains interference on a cable (very common in the kind of environments we work in!) Check all your cables / gear and get the best shielded cables you can and watch for runs alongside mains power.

Silly question, but just to rule it out: is WiFi definitely turned off? Double check that. And if you’re not using a router, please make sure that all your stuff is on the right sub net! (PS please always use a router :blush: )

Regarding Local Network permissions / Ether Dream discovery on 1.0.3:

I’ve been trying to figure this out all morning. What I’ve learned is :

  • If there are multiple Liberation versions run, they’ll show up as separate entities in the Local Network permissions settings window but with the same name, whichever app was run first.
  • I’m not 100% sure that we even need local network permissions to see Ether Dream anyway.
  • There are actually some differences between 1.0.3 and 0.9.9 in the discovery system but mostly due to error correction.
  • 1.0.3 works fine here at least so it can work. So there must be something different about your set up that the new code isn’t catching.
  • Maybe it’s worth resetting your permissions anyway?

Try closing Liberation,
In a terminal :
tccutil reset All co.seblee.Liberation
Reboot.
Run Liberation again.

Other suggestions :

  • Turn on logging and see if any errors come up when you first start Liberation
  • Reboot the machine and then start 1.0.3 before any other version. I’m wondering if 0.9.9 doesn’t close down properly it might hog the UDP port.
  • I assume nothing else on your machine is looking for Ether Dreams? MadLaser or something?

If you still have no luck let me know and I’ll send you a new test build.

Thank so much for reporting and I hope we can get to the bottom of it !

Seb