Hi Tom,
They sent me the following long email, it does mention inbound access but seems like a bit of a generic answer if all those ports really need to be opened inbound via PAT ? I've asked Sonos to clarify exactly what is required inbound (as opposed to stateful outbound), and am still awaiting a reply ! "If your firewall needs to be manually configured, refer to the port numbers below and make sure inbound access is enabled for the Sonos application. Port (TCP) Used for 80 and 443 Music services, radio, and Sonos account 445 and 3445 Music library 3400, 3401, and 3500 Sonos app control 4070 Spotify Connect 4444 System updates Port (UDP) Used for 136 through 139 Music library 1900 and 1901 Sonos app control 2869, 10243, and 10280 through 10284 Windows Media Sharing 5353 Spotify Connect 6969 Sonos setup" 22 Nov 2019, 11:32 by [email protected]: > Hi Rachel, > I does Sonos Require uPnP support ? > (does Sonos require a few ports to be forwarded from your internet > interface back into the Sonos > device on the LAN) > is there a manual port forwarding that you can do to get around the > uPNP requirement ? > > > > > > > > On Fri, 22 Nov 2019 at 11:26, Rachel Roch <[email protected]> wrote: > >> >> Hi, >> >> Refuse to use Sonos myself, but am helping (or trying to) out a friend who >> has a Sonos try to get things working wtih OpenBSD PF. >> >> I've simplified their PF rulese to a simple swiss cheese (i.e. stateful >> NAT'd allow any out to any). >> >> Everything else they care to run on their network is running perfectly. >> Apart from their darn Sonos box. >> >> Sonos support are about as much use as a fart in spacesuit, so I'm hoping >> there's somebody on this list who has already fought and won the Sonos >> battle ? >> >> Thanks ! >> >> Rachel >> > > > -- > Kindest regards, > Tom Smyth. >
