Skip to content
  • Register

    • Sonos connection

    Posts: 2
    First Comment
    edited November 2023 in Nebula

    Have installed 2x nwa50ax in our home. Since the installation I cannot access the Sonos appliances via the Sonos app. The speakers are connected and listed in the clients list in Nebula but the Sonos app does not see them. Fyi, all other devices(PC, tablet, etc) seem to function correctly on the Zyxel Aps

    If however the speakers are connected via Ethernet everything works, weirdly airplay device shows up over wifi but does not play. (also works over Ethernet)

    Any ideas?

    Welcome!

    It looks like you're new here. If you want to get involved, click on this button!
    Sign In
    Register

    Accepted Solution

    • Posts: 659  Zyxel Employee
      Zyxel Certified Network Engineer Level 1 - Switch Zyxel Certified Network Engineer Level 1 - Security Zyxel Certified Network Administrator - Nebula Zyxel Certified Sales Associate
      edited September 2023 Answer ✓

      Hello @userAti

      The "Tagging" feature on the SSID page doesn't pertain to VLANs. It is designed to assign specific SSIDs to designated APs. For instance, tagging an AP with “Lobby” and assigning the “Lobby” tag to SSID_lobby means only that AP will broadcast SSID_lobby. For a step-by-step guide on this, refer to:

      [NEBULA] How can I configure to separate SSIDs between NAPs?

      Zyxel_Dean

      Your current setup has both APs with same tags (1, 25, 50). This means both APs are broadcasting SSIDs 1, 3, and 4 based on their associated tags.

      For VLANs, you've assigned VLAN 1 to SSID 1, which serves as the untagged management VLAN. Additionally, VLAN 25 is set for SSID 3, and VLAN 50 for SSID 4. It's crucial to ensure that any uplink devices, like switches and DHCP servers, are appropriately configured to align with VLANs 25 and 50.

      Several factors can block wireless device communication:

      1. Devices connect to different SSIDs on separate VLANs, which are set to not interact on the uplink device.
      2. Devices connect to the same SSID but different APs, and the uplink device linking the APs has port isolation or layer 2 isolation activated.

      Additionally, the Sonos APP and device utilize SSDP for discovery, relying on multicast traffic. Ensure the uplink devices in the network have IGMP snooping set up correctly for efficient multicast traffic forwarding.

      Nami

    All Replies

    • Posts: 659  Zyxel Employee
      Zyxel Certified Network Engineer Level 1 - Switch Zyxel Certified Network Engineer Level 1 - Security Zyxel Certified Network Administrator - Nebula Zyxel Certified Sales Associate

      Hello @userAti

      From your description, it seems there's an issue with the Sonos app's ability to discover and communicate with your Sonos devices over the wireless network.

      Connectivity and Configuration Checks:

      • Ensure that the smartphone with the Sonos app and the Sonos devices are connected to the same SSID.
      • Ensure that traffic between wireless devices isn't blocked by specific configurations. To verify this, navigate to Configure > Access points > SSID advanced settings, select the specified SSID, and check if the Layer 2 isolation and Intra-BSS traffic blocking options are enabled. If they are active, they might be blocking traffic between wireless devices, and you should consider disabling them.
      L2Iso_BSS.png

      If these two features are already turned off, and both your phone and IoT devices are on the same SSID but connected to different APs, their communication might be obstructed by the uplink device connecting the two APs. Could you let us know which uplink device you're using to connect the two APs?

      Recommendations for IoT Devices:

      We suggest setting up a dedicated SSID that operates exclusively on the 2.4GHz band for IoT devices. This can enhance the connectivity and performance of such devices. Here are detailed FAQ:

      What can I adopt to resolve the issue of IoT device being blocked by the AP?

      Zyxel_Judy

      Nami

    • Posts: 2
      First Comment

      Hi Zyxel Nami,

      Layer 2 isolation and intra traffic blocking is already off.

      I found that I had to set in "WiFi SSID settings" → "Tagging" to match the "VLAN ID", I also had to set the "Site-wide → Devices→Access points → NWA50ax(as mac)→ "Tag" to match the "VLAN ID".

      Now it works, will report if anything changes.

      The "VLAN ID" in this case is 1, the default Lan, which is untagged I believe?

      I do not have a deep understanding of networking, so maybe you could explain this behaviour ?

      Regrads,

      Ati

    • Posts: 659  Zyxel Employee
      Zyxel Certified Network Engineer Level 1 - Switch Zyxel Certified Network Engineer Level 1 - Security Zyxel Certified Network Administrator - Nebula Zyxel Certified Sales Associate
      edited September 2023 Answer ✓

      Hello @userAti

      The "Tagging" feature on the SSID page doesn't pertain to VLANs. It is designed to assign specific SSIDs to designated APs. For instance, tagging an AP with “Lobby” and assigning the “Lobby” tag to SSID_lobby means only that AP will broadcast SSID_lobby. For a step-by-step guide on this, refer to:

      [NEBULA] How can I configure to separate SSIDs between NAPs?

      Zyxel_Dean

      Your current setup has both APs with same tags (1, 25, 50). This means both APs are broadcasting SSIDs 1, 3, and 4 based on their associated tags.

      For VLANs, you've assigned VLAN 1 to SSID 1, which serves as the untagged management VLAN. Additionally, VLAN 25 is set for SSID 3, and VLAN 50 for SSID 4. It's crucial to ensure that any uplink devices, like switches and DHCP servers, are appropriately configured to align with VLANs 25 and 50.

      Several factors can block wireless device communication:

      1. Devices connect to different SSIDs on separate VLANs, which are set to not interact on the uplink device.
      2. Devices connect to the same SSID but different APs, and the uplink device linking the APs has port isolation or layer 2 isolation activated.

      Additionally, the Sonos APP and device utilize SSDP for discovery, relying on multicast traffic. Ensure the uplink devices in the network have IGMP snooping set up correctly for efficient multicast traffic forwarding.

      Nami

    Welcome!

    It looks like you're new here. If you want to get involved, click on this button!
    Sign In
    Register

    Welcome!

    It looks like you're new here. If you want to get involved, click on this button!
    Sign In
    Register

    Quick Links

    Categories

    Nebula Tips & Tricks


    Read more

    Nebula Help Center

    EnglishTiếng ViệtРусскийไทย中文（台灣）