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
    November 2, 2016
    Yes. I've been in touch with the IT company who configured the network to get an idea of whats setup.

    It could be that the WAP networks are isolated guests running on a 10.x.x.x subnet.

    If a plug a SONOS:BOOST into AP1 then it will likely pickup a 172.16.31.x address. The iPad sitting on the 10.x.x.x network I assume wouldn't see it (back to square one).

    So options are either use Android to directly connect to SonosNet, or connect a dedicated laptop with Sonos app via Ethernet to the SONOS:BOOST.

    Or even better, could I connect the laptop to the SONOS:CONNECT (physical location is better)?
    ratty
    ratty
    November 2, 2016
    It could be that the WAP networks are isolated guests running on a 10.x.x.x subnet.
    Quite possible, though usually guest SSIDs are identified as such by default.

    If a plug a SONOS:BOOST into AP1 then it will likely pickup a 172.16.31.x address. The iPad sitting on the 10.x.x.x network I assume wouldn't see it (back to square one).

    It wouldn't see it because it's on a different subnet. If it's on a guest SSID it could be further restricted.

    So options are either use Android to directly connect to SonosNet, or connect a dedicated laptop with Sonos app via Ethernet to the SONOS:BOOST.

    Or even better, could I connect the laptop to the SONOS:CONNECT (physical location is better)?

    You could wire a laptop anywhere into the network. The Ethernet ports on the wireless Sonos units are also available. Note however that (a) the Sonos ports are 10/100 only (not 1Gbps), and (b) the connection speed via a wireless Sonos box will be limited to SonosNet's bandwidth.

    Also, to use SonosNet on the Android you first need to connect it via WiFi.
    Terms & ConditionsAccessibility statement