Hi,
With the ever increasing SMART home adoption and the lack of security from the 10’s if not 100’s of IoT devices that are being installed in peoples homes and offices it is a real surprise that segregating Sonos devices onto their own subnet is such a challenge. I am an advanced IT Pro with over 20 years of experience in the industry and have spent hours and hours trying to get my Sonos devices to work on a segregated IoT network.
I have implemented mDNS repeater’s and IGMP Proxies but I still can’t get my clients on my main network to communicate with Sonos devices on the IoT network.
I have read hundreds of old posts and I understand that the App Control requires the following port openings:
Source: Sonos App Control on LAN - Destination: Sonos Players on IoT LAN
TCP: 1400, 1443 (SSL)
Source: Sonos Players on IoT - Destination: Sonos App Control/ Media Servers on LAN
TCP: 3500, 3400-3402 (App Control)
4444 (System Updates)
UDP: 6969 (Sonos Setup)
1900-1901 (App Control)
With the increased focus on security I am surprised Sonos hasn’t provided guidance on this issue. If anyone can provide an up to date guide that works with the Sonos S2 controller I would be very grateful.
This is of particular relevance for people who use Sonos with a Home Theater setup and AppleTV. Especially when AppleTV is designed as the hub for Apples “HomeKit” smart hub controller of all Homekit IoT devices. It therefore makes sense to have the AppleTV and IoT devices on the same subnet and when using Sonos Arc for Home Theater it make sense to have the Sonos on the same IoT subnet.
