Skip to content

Commit fd2d861

Browse files
authored
Create README.md
1 parent f442833 commit fd2d861

File tree

1 file changed

+19
-0
lines changed

1 file changed

+19
-0
lines changed

README.md

Lines changed: 19 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -893,3 +893,22 @@ DOCKER
893893
-----
894894

895895
Docker usage is maintained by [Chris Nesbitt-Smith](https://github.com/chrisns) at [chrisns/docker-node-sonos-http-api](https://github.com/chrisns/docker-node-sonos-http-api)
896+
897+
## FIREWALL
898+
899+
If you are running this in an environment where you manually have to unblock traffic to and from the machine, the following traffic needs to be allowed:
900+
901+
### Incoming
902+
TCP, port 3500 (Sonos events)
903+
UDP, port 1905 (Sonos initial discovery)
904+
TCP, port 5005 (if using the default api port)
905+
TCP, port 5006 (if using https support, optional)
906+
907+
### Outgoing
908+
TCP, port 1400 (Sonos control commands)
909+
UDP, port 1900 (Sonos initial discovery)
910+
TCP, whatever port used for webhooks (optional)
911+
912+
The UDP traffic is a mixture of multicast (outgoing), broadcast (outgoing) and unicast (incoming). The multicast address is 239.255.255.250, the broadcast is 255.255.255.255 and the unicast is from the Sonos players.
913+
914+
If port 3500 is occupied while trying to bind it, it will try using 3501, 3502, 3503 etc. You would need to adjust your firewall rules accordingly, if running multiple instances of this software, or any other software utilizing these ports.

0 commit comments

Comments
 (0)