I’ve set my entire network up with static IPs, and everything is talking perfectly. However, every time I reboot the system, one computer sees both hosts, while the other only sees itself. So for example, A can control B, but B can’t control A (or vice versa).
I fixed the problem by navigating to System Settings → Privacy & Security → Local Network → Toggle Ableset off & back on using the computer that is having trouble seeing the rest of the network.
Unfortunately, every time I reboot the system I have to repeat this process.
Is this a Sequoia problem? An M4 problem? Would love to find a permanent solution for this. Any guidance is appreciated, thanks Leo!
@TORI I’ve already shipped that system out on the road and they are just using the workaround of toggling that security setting every day on startup as neccesary. However, I think the problem really lies with the security protocols of macOS Sequoia. I’ve run into similar issues with Dante gear interacting with Apple’s security settings recently, and am currently thinking that I’m going to set all silicon playback Macs up in Sonoma instead, since security seems to be more lax there. Interesting that upgrading to Ableset 3 didn’t fix your issue though, I would have expected that to take care of it for you, assuming you are running in Sequoia.
Yeah I am running Sequoia… I can get the hosts to connect to each other by toggling the local Host permission, but even then my sync playback and drift correction isn’t functioning properly. Hopefully ableset team find something in my Log package that can be resolved . I’m at a complete loss otherwise I’ve tried everything I can find
Yeah @leolabs, I don’t think Ablenet is stable in Sequoia. I would highly suggest all users who rely on redundant network stability to roll back their systems to MacOS Sonoma. Since I’ve started doing that, all of my network security issues have been solved. It would be really helpful to have an official statement on Ableset’s website listing all fully stable OS versions, as right now it is stated that Ableset is fully compatible with all OS versions 12+. In my experience, that is simply not true if you rely on Ablenet. OS 15 (and I’d assume 26, although Ableton itself is not yet fully stable on 26) have security updates that Ableset does not yet have a consistent fix for in either version 2 or version 3.
Thank you for your feedback, those local network issues are indeed a problem on Sequoia, though I did have luck with later versions of Sequoia and they seem to be resolved with macOS Tahoe. I’ll add a remark about this to my FAQs
Hey @leoleo I could try to update the OS, But as mentioned in this Thread, that hasn’t resolved the issues and may actually cause more. And I pull require me to Time Machine both Mac’s etc. quite a time consuming exercise.
Would it be possible to prioritise having a look at the log package I sent you to see what’s happening? I got ableset for redundancy and at the moment i don’t feel confident using it given how oddly the networking is behaving.
Every so often they link up and the sync and drift function works, but it’s rare and I can’t for the life of me figure out when or how I get it to work. I’ve spent 2 full days trying to resolve this now and I’m still where I started.
If you could have a look over it it would be much appreciated
. I’m at a complete loss otherwise I’ve tried everything I can find