Feature Request - urgent

Maybe someone in the forum can help me what to do?

I have five SONOS installations which have actually the follwing IP ranges:

A

10.100.5.x
255.255.255.0

B

10.100.6.x
255.255.255.0

C

10.100.8.x
255.255.255.0

D

10.100.9.x
255.255.255.0

E

10.100.12.x
255.255.255.0

All these networks are connected via VPN.

How do I have to change the network (IP range and/or Subnet mask) that SONOS does not see /show the installations that are not local.

I would very much appreciate help.

Hi @Brendianer 

You have 5 locations? You said 3 at first.

Well, the first thing you need to do is split the large household that’s bridging more than one location - presumably, that’s why that system has 2 subnets. You’ll need to factory reset units in two locations and set them up as new systems, in isolation from the others (don’t set up if you can connect to another system).

You won’t need to do anything to the systems on subnets 8 and 9 (assuming they don’t bridge multiple locations, but 9 looks much bigger than 8, so maybe it does), but 5 and 12 are on the same household so either 5 or 12 needs to be reset and set up again. I don’t see any units currently on subnet 6 - they might have a mix of 5 and 12 or be half of 9? I don’t see any variation of public IPs across any one subnet, so it’s hard to say.

As @ratty mentioned, if the subnet mask on your phone is 255.255.0.0 instead of 255.255.255.0, the app could communicate with any of the systems, but will only do so with the first one it finds. You need to make sure that the controller device always has the same subnet as the speakers you expect it to be able to control while in that location, and a subnet mask of 255.255.255.0.

With all this set, I don’t think it will matter to your Sonos system that you’re on a VPN.

I hope this is of help.

...but 5 and 12 are not in the same household.

5 is in Switzerland and 12 in South Africa.

I am still confused but on a higher level.

@Brendianer 

Did you start one system by taking a speaker from the other? If you did that without first resetting it, that would explain why the two systems see themselves as one (the moved speaker “carried” the household ID to the new location, and it was then expanded to include new units). Either that or the VPN connected them during setup and they’ve since had their subnets changed to be different.

To tell the truth, it’s not (currently) vital that you separate these, though it would certainly make it easier for our technical support team to help you in the future (with non-VPN related issues). It would affect smart-home integration however, as a voice assistant wouldn’t know whether to send instructions to Switzerland or to South Africa (or the other locations). I do, however, recommend that you make the split due to changes coming that I can’t discuss.

A VPN is for joining networks, and what you’re asking is for Sonos, now that it’s on a VPN, to behave as if it’s not. I think the most important factor for the results you’re after would be to ensure the subnet mask on your phone only allows communication with the current subnet, and that it has the correct subnet for it’s current location. If you can’t do this due to desired, non-Sonos-related functionality, it may be better to control Sonos from another device that doesn’t need to communicate with the other VPN locations.

Thanks Corry!

To sort this out: is it sufficient to reset one system?

Do you at SONOS my systems with IDs so that you can tell me in detail what I have to do?

Then I would prefer to do it on PM.

@Brendianer 

That depends on what’s going on with subnet 6 - I see no evidence of it being used by any of your systems/units.

I can send you lists of serials, separated by how they’re organised by households, by PM.