Sorry for the redundancy but I figured I’d put this here at the top of topics so that Leo can see it. I’m having the same issue this guy had and he tried to help me. Apparently had something to do with an ad hoc network created.
I went into my network settings and there is in fact an ad hoc network set up and I can’t get rid of it. I sent a log package to Leo, I thought. Maybe it didn’t quite go through.
But I’d love to sort this out. A little more info… I believe I might have used terminal to create an ad hoc network a while back. I know, stupid idea. I was testing some things out. I have another computer that my system(s) are working fine on. Ableton and ableset. No issues.
So if Leo sees this and I can make sure he gets a log package to see what’s going on maybe can help me get this computer back up and running with ableset?
Thanks for the follow-up — and no worries at all, really appreciate the extra context.
Just to confirm: your log package did come through, so we have everything we need. We’re currently taking a look at the network configuration issue on our end, and we’ll get back to you as soon as we have more insight.
Thanks again for your patience — we’ll keep you posted!
Thanks Agus. I have a feeling it’s somewhere where I tried to create an ad hoc network on my M1 Macbook Pro through terminal. Thanks for working on it.
Hey @jason, please excuse the late reply on this one!
It seems that the ad-hoc network you created somehow changed the IP address of the local loopback interface (lo0) that AbleSet uses to communicate with Live.
To reset the IP address of that interface back to 127.0.0.1, you can use the following shell command:
