Within the same machine I can use slconsole to connect to sooperlooper, the machine is not firewalled and network functions fine for the rest of the programs.
On a separate machine, with hostname cloud-laptop, I attempt to connect to sooperlooper on alarmpedal:
but the gui on my side is blankslgui --connect-host=192.168.1.4 --never-spawn
slgui: our URL is osc.udp://cloud-laptop:12595/
checking on the remote system, sooperlooper logs:
The OSC error happens every time I attempt to connect with the gui, so it indicates that there's at least a recognized effort, but it fails.sooperlooper
Copyright 2007 Jesse Chappell
OSC server URI (network) is: osc.udp://alarmpedal:9951/
OSC error -2: Name or service not known
One thing that's weird to me is that the reported OSC URI are using the hostnames, but those hostnames aren't available in the network; if I were to ping them there'd be no dns resolution:
Running sooperlooper on cloud-laptop and connecting with slgui using loopback networking does work properly.ping alarmpedal
ping: alarmpedal: Name or service not known
Is sooperlooper assuming the hostnames are available network-wide and using them internally in the protocol - failing so, or is there some other bug at play here?