You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm trying out this software on Ubuntu (without docker). My sonos (S2) is on the same network as the ubuntu (both ethernet). I get the error "No system has yet been discovered".
When I perform a tcpdump, I can see absolutely 0 UDP packets related to sonos. My ufw rules are open for the local network. I can in fact see other UDP packets from network devices in the dump.
I've already tried the "disableIpDiscovery" setting, as well as setting the IP in the config.
I would expect to see at least outgooing UDP broadcasts from this tool. What more can be tried?
The text was updated successfully, but these errors were encountered:
Is this a barebone ubuntu install? No VM or similar?
You should definitely see outgoing udp destined for port 1900 if it is
scanning for systems.
I don't really have any ideas if that isn't the case. I haven't tested this
with later node versions on Linux in a while, but I wouldn't expect any
changes to the socket code that would cause this.
Maybe there is some SELinux stuff that blocks untrusted applications to do
anything with sockets?
On Mon, 26 Feb 2024, 20:53 Sam Roose, ***@***.***> wrote:
I'm trying out this software on Ubuntu (without docker). My sonos (S2) is
on the same network as the ubuntu (both ethernet). I get the error "No
system has yet been discovered".
When I perform a tcpdump, I can see absolutely 0 UDP packets related to
sonos. My ufw rules are open for the local network. I can in fact see other
UDP packets from network devices in the dump.
I've already tried the "disableIpDiscovery" setting, as well as setting
the IP in the config.
I would expect to see at least outgooing UDP broadcasts from this tool.
What more can be tried?
—
Reply to this email directly, view it on GitHub
<#886>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAYE2IZTF7T64G2DH36DY5LYVTR3TAVCNFSM6AAAAABD22DSGGVHI2DSMVQWIX3LMV43ASLTON2WKOZSGE2TKMBQGQ2TQNY>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
yes this is a plain ubuntu 22.04 install. No SELinux installed. The only 'special' config is that I also have a tunnel and docker network interfaces. But, I've set the IP to the eth interface. Also, when I do a tcpdump over all interfaces, none of them pick up outgoing UDP requests.
I'm trying out this software on Ubuntu (without docker). My sonos (S2) is on the same network as the ubuntu (both ethernet). I get the error "No system has yet been discovered".
When I perform a tcpdump, I can see absolutely 0 UDP packets related to sonos. My ufw rules are open for the local network. I can in fact see other UDP packets from network devices in the dump.
I've already tried the "disableIpDiscovery" setting, as well as setting the IP in the config.
I would expect to see at least outgooing UDP broadcasts from this tool. What more can be tried?
The text was updated successfully, but these errors were encountered: