You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In current moment sonos control application using ssdp to discover players . It create really pain for a lot of people who try to make their network more secure and segment based. But problem with SSDP is that it have TTL 1 and cannot communicate between different segments. Situation even worse in secured wifi installations Sonos controller cannot find Sonos player even if it using same Wifi accesspoint and same wifi network because quite often Wireless Client Isolation on wifi enabeld.
All of of these create quite specific requirements for network where sonos can work :
network have to be not segmented . everything is same segment . it create just mess in your network.
for wifi must be disabled Wireless Client Isolation. It is very nice for malware spread.
Due to it people as i see in internet quite often build such kind of surrogates setup like IGMP proxy to forward multicast traffic between segments or using "docker : host network" which i also think is an surrogate which used only for one purpose - to search Sonos player system.
If to implement connection from control application to exact ip address it will give possibility to move all SONOS speakers to separate network segment. It will be possible to use normal docker network instead of "docker host" which is not very good in most setups.
The text was updated successfully, but these errors were encountered:
In current moment sonos control application using ssdp to discover players . It create really pain for a lot of people who try to make their network more secure and segment based. But problem with SSDP is that it have TTL 1 and cannot communicate between different segments. Situation even worse in secured wifi installations Sonos controller cannot find Sonos player even if it using same Wifi accesspoint and same wifi network because quite often Wireless Client Isolation on wifi enabeld.
All of of these create quite specific requirements for network where sonos can work :
Due to it people as i see in internet quite often build such kind of surrogates setup like IGMP proxy to forward multicast traffic between segments or using "docker : host network" which i also think is an surrogate which used only for one purpose - to search Sonos player system.
If to implement connection from control application to exact ip address it will give possibility to move all SONOS speakers to separate network segment. It will be possible to use normal docker network instead of "docker host" which is not very good in most setups.
The text was updated successfully, but these errors were encountered: