Feature Request - urgent

Hi @Brendianer 

Welcome to the Sonos Community!

We don’t support the use of VPNs - if you weren’t linking the 3 locations, I’m sure you wouldn’t have this issue as the app is capable of switching between systems without problems

It seems, however, that your VPN is allowing the app in one location to communicate with Sonos in an other location. This is the point of VPNs, so I’m not sure why you are surprised, nor why it worked differently before.

Perhaps you can configure your router to not include Sonos devices in the VPNs?

It could also conceivably help to reboot your phone, if it hasn’t been done in a while.

Thanks Corry!
But I do not agree. The VPN connection already existed under S1. At that time the local installation was always displayed.
Why can't you just view the local installation instead of the more distant one?

Hi @Brendianer 

Given that the point of a VPN is to combine 2 (or more) networks such that they are now the same network, how are we to tell which system is local and which is not?

There is no reason why things would be different on S1. I think you might be confusing correlation with causation. Perhaps something was changed in your network around a similar time as you went to S2?

It does, however, come down to this - we do not support the use of VPNs.

Hopefully, someone in the community may have some ideas.

Believe me: I am now running 6 installations, some of them quite large, which worked without any problems with the same network installation under S1.Why can't the app find the local installation based on the local IP address?

Is there maybe a port to be blocked that SONOS does not recognize the farer system?

If you’re on a VPN, there is no “local” distinction.

I'm not a software engineer: but can't you take the IP of the device (e.g. mobile phone) as a basis and then display the SONOS installation that has the same IP range?I would do it like that... 

Hi @Brendianer 

Yes - that’s exactly what we already do. Sonos does not work across different subnets, so yes, this should work (though it wouldn’t suddenly make it a setup that we support).

However, all the Sonos units on all three of your systems are configured to be on the same subnet. You’ll need to reconfigure your VPN to put the devices on different subnets, which may interfere with the actual reasons you have the VPN set up in the first place.

I recommend you remove Sonos equipment and your controller device from the VPN - this would keep things separate, and there’s no reason for them to be on the VPN anyway - they certainly don’t benefit from being on it.

Can you maybe help/assist?

As an sample I have one net with

10.100.5.x
255.255.255.0

and one with

10.100.6.x
255.255.255.0

Connected via VPN.

How do I modify that?

Hi @Brendianer 

My mistake - all your units are 10.100.x.x, but the larger Sonos system has different subnets just on that one system (I assume if you could connect to it, you’d have missing rooms). I would certainly look to fix this first - if your phone, in location A, gets an IP with a subnet matching the system in location B, then all you’ll see in the app is system B. If you configure your networks so that all clients in one location get the same subnet and if that subnet is unique to that location, that should help.

As Sonos don’t support VPNs, we (the technical support staff) don’t get training in their use, or in how Sonos would operate on them, so I cannot help. I recommend getting professional network configuration assistance.

The mobile’s subnet mask is possibly set to 255.255.0.0, hence the remote Sonos system would be visible.