Skip to main content
feisar
Contributor I
October 19, 2016
Question

Multiple Home WiFi Connections

  • October 19, 2016
  • 22 replies
  • 1952 views
Hi,

At home, I have a few different networks with associated WiFi SSIDs (e.g. trusted, guest, IoT). I would like the Sonos device to be on my 'IoT' network but I want to be able to control it from devices on my 'trusted' and maybe 'guest' network, which, of course, use a different SSIDs ``.

Unfortunately, when I try to control the Sonos from a device connected to a different SSID the Sonos App gives me a message effectively saying 'sorry, different WiFi name, can't do it'.

Now, I don't think there is a technical reason for this block, because if (for testing purposes) I placed the App in one network and the Sonos in another then allow the correct ports between them but make sure their connected to the same SSID - it works (I did this test by connecting to my home VPN, which puts the App device in a different network).

Anyway, short story, can I just tell the App or Sonos to ignore the fact that the SSID doesn't match because I know it will work anyway?

Tried to explain best I can but please ask questions if I haven't made myself clear.

Thank you,
    This topic has been closed for further comments. You can use the search bar to find a similar topic, or create a new one by clicking Create Topic at the top of the page.

    22 replies

    Show previous replies
    Nickaminsky
    October 31, 2016

    Yes. Assuming there's an Ethernet feed to the location of each AP you could wire the CONNECT and one of the CONNECT:AMPs directly. No need for a BOOST.

    Not quite following that sorry.

    So you'd have the AP in each location connected into the SONOS via ethernet? and then the other SONOS ethernet port connected to the main router?

    What about the other 3 CONNECT:AMPs? Or do they connect using SonosNet?
    ratty
    ratty
    October 31, 2016
    Yes. You can daisy-chain each AP through the CONNECT/CONNECT:AMP.

    The 3 other CONNECT:AMPs will talk to the wired one using SonosNet.

    The term 'BOOST Setup' has sowed considerable confusion. You don't need a BOOST for SonosNet operation. Just wire one or more Sonos devices, of any type, and the SonosNet mesh is automatically set up.
    Nickaminsky
    October 31, 2016
    OK. Done some more investigating.

    The setup looks like 2 APs. One of which is a Dell SonicPoint N2. I assume the other one is the same but can only check later on.

    They are connected to a router using Ethernet.

    The iPad can see all SONOS devices when connected to AP2, but sees nothing when connected to AP1

    Here is the interesting part. The SonicPoint N2 is running 2.4GHZ and 5GHz WIFI.

    I can test this using my android tablet by manually telling it to use either 2.4GHZ or 5GHz WIFI.

    With AP2, my tablet can connect to 2.4GHz fine, but cannot seem to connect to the 5GHz band - it simply doesn't get an IP address.

    What I think is happening is the iPad Sonos app is connecting to AP1 over 5GHz WIFI and not seeing any devices.

    When it connects to AP2 its using 2.4GHz and sees all devices.

    Does that sound plausible?

    If so is the only solution to disable the 5GHZ WIFI throughout?
    ratty
    ratty
    October 31, 2016
    You're probably getting close. Many APs won't forward multicast traffic between their two wireless segments. This stops a Sonos controller on 5GHz from discovering the players on the 2.4GHz band in 'Standard Setup'.

    Wire the CONNECT and CONNECT:AMP, as already discussed, and this problem will go away. Either that or you must prevent your phone/tablet from attaching to 5GHz.
    Nickaminsky
    October 31, 2016
    I'm not sure the CONNECT:AMPs are in close proximity to AP2 in order to wire one of them over ethernet. I'll find out later

    The CONNECT probably can be wired into AP1 providing I have audio interconnects long enough back to the amp.

    Would it be sufficient to have the single CONNECT over ethernet provide SonosNet assuming its range can reach the CONNECT:AMPs ?

    And would the iPad connecting over 5GHz still see the devices in this scenario? Presumably it would connect to AP1 over 5GHz and then AP1 being connected to the CONNECT can then see the SONOS devices over SonosNet ?
    ratty
    ratty
    October 31, 2016
    I'm not sure the CONNECT:AMPs are in close proximity to AP2 in order to wire one of them over ethernet. I'll find out later

    The CONNECT probably can be wired into AP1 providing I have audio interconnects long enough back to the amp.
    You could always wire a BOOST or BRIDGE instead.

    Would it be sufficient to have the single CONNECT over ethernet provide SonosNet assuming its range can reach the CONNECT:AMPs ?

    It's a big assumption, considering you felt the need for two APs. Presumably mobiles at the AP2 location have a weak (if any) signal from AP1.

    And would the iPad connecting over 5GHz still see the devices in this scenario? Presumably it would connect to AP1 over 5GHz and then AP1 being connected to the CONNECT can then see the SONOS devices over SonosNet ?

    Yes. The Sonos devices would be attached via the wired network.
    Nickaminsky
    October 31, 2016
    OK thanks very much for your help.

    Its looking likely that I'll go with my original idea of wiring in a SONOS:BOOST up to AP2. Assuming its in a central location to the SONOS devices - which I'll find out later.

    Because the SONOS devices would be connected over ethernet (via SonosNet mesh) to AP2, I still should be able to see them with my iPad connected to AP1 over 5GHz...have I got that right?
    ratty
    ratty
    October 31, 2016
    Because the SONOS devices would be connected over ethernet (via SonosNet mesh) to AP2, I still should be able to see them with my iPad connected to AP1 over 5GHz...have I got that right?
    Correct.
    Nickaminsky
    October 31, 2016
    I now don't think this is related to the 5GHz issue. I did some more testing earlier with my android tablet set to just connect to the 2.4GHz band.

    The Sonos app connected on AP2 but when I moved over to AP1 it lost connection to SONOS, just like the iPad does.

    So it looks more a case of the connectivity between the two wireless APs is not achievable for SONOS.

    Using a netbook connected to AP1 over WIFI, I can ping the SONOS IP addresses (netbook and SONOS all on a 10.0.0.x subnet)

    If I connect the netbook to AP1 via ethernet it picks up a 172.16.x.x address and the SONOS 10.0.0.x devices are still pingable. I can also access the internet fine.

    I think my next step is to connect a SONOS:BOOST to AP1 via ethernet.
    ratty
    ratty
    October 31, 2016
    If I connect the netbook to AP1 via ethernet it picks up a 172.16.x.x address and the SONOS 10.0.0.x devices are still pingable. I can also access the internet fine.
    Whoa! You have two separate private subnets. Either something somewhere is acting as a second router (complete with DHCP), or there are two DHCP servers on the same segment (a recipe for chaos).
    Show more replies
    Terms & ConditionsAccessibility statement