Question: Should we provide additional guidance regarding firewalls.
Depending on the user's distro, they may have one of the following installed as firewall:
- iptables/nftables
- ufw
- firewalld
And unfortunately it may not always be clear which.
In my case, on a 2023 install of CachyOS, I had firewalld as the default, on a distro which defaults to ufw nowadays.
Because I had the iptables services running, I assumed I was on raw iptables, I instead was on firewalld.
It took me an hour of debugging, as a software dev myself; I imagine regular users may have it harder. Is there any way we could amend the README to provide instructions, either how to detect your current firewall, and/or migrate to ufw.
SONOS is a home device, and it uses SSDP to allow auto discovery. So there is no good way, and in my opinion no good reason to enable any firewall in your home devices. Keep your firewall in your main router. Apart from the discovery, the communication between Noson and the devices requires the port range 1400-1410 (Noson listen on TCP), and 1400 or 3400 or depend your sonos device(s) ... have a good luck
Ya, I figured.
I brought this up because a bunch of distros have a firewall set up by default, as it was in my case; I wound up learning this the hard way.
I ended up returning the device in the end though, there wasn't a way to losslessly send audio to it from a PC without either 8+ second latency or being lossy. (e.g. DAC -> ADC with the 'line in adapter' is lossy due to double conversion). Their official app was also extremely unstable and would keep dropping the device, which was 1m away from the access point (unlike NOSON, which ran just fine).
I think my router wasn't being friendly with SSDP.
The ports are randomized.. I had no luck opening them. They don't even use the dynamic port range. I ended up allowing all traffic from the devices IP.
ufw allow from <DEVICE_IP>
I think you could limit the protocol to UDP and the port range to something high.. but not worth the effort.
Some of the blocked requests: