Thanks all for your ideas. I'll spend a little time on it over the next few days and see how far I can get.
22 Nov 2019, 16:34 by s...@spacehopper.org: > On 2019-11-22, Peter N. M. Hansteen <pe...@bsdly.net> wrote: > >> On Fri, Nov 22, 2019 at 12:56:51PM +0100, Rachel Roch wrote: >> >> >>> 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. >>> >> >> I get the feeling that there is some confusion at the support people's >> end about what needs to be open inbound vs outbound. >> > > Most users will not have a separate firewall device between Sonos and > anything accessing it, only a host firewall on e.g. Windows machines > running their software, and I think that is what their advice refers to. > > If it is indeed on a different subnet then there are other things > that might need considering, like whether multicast can make it through. > > The other thing to consider if the various devices involved are all > connected via wifi is whether client isolation is enabled. > > We really need a sketch/description of the desired setup to give > further advice .. >