I have a hAP ax³ and a cAP ax connected by Ethernet and CAPsMAN, both running v17.6. My Sonos Roam died and was promptly replaced with a Sonos Roam 2. Thanks Sonos!

I think I set up the Sonos Roam when I just had the hAP ax³ and don't remember having any problems then. However, I am struggling to set up the Sonos Roam 2. Some potential solutions suggest first connecting a wired Sonos device. However, I only have the single, wireless speaker.

Running the Sonos App on my GrapheneOS mobile emulating Android works up to the point where I enter the password for my WiFi network where it responds with We couldn't connect to .... I have added the MAC address taken from the base of the speaker to DHCP and the Access List. The SSID and password are correct. The Sonos Roam 2 was closer to the hAP ax³. I also tried with it closer to the cAP ax with similar results.

One thing I have noticed is that when the mobile connects to a temporary network on the Sonos Roam 2 the MAC address used is the same as the one on the base except that it starts with "C6:" instead of "C4:". I don't know if the Sonos Roam 2 can use a private network as well as my WiFi network?

I have seen Mikrotik tips: Sonos on CAPsMAN (https://www.youtube.com/watch?v=YVyj7N6O1kk) but I am less clear on how to make equivalent changes on v17.6.

I have set logging to include "topics=wireless,debug prefix="" action=memory" but could see nothing relating to the Sonos Roam 2 in the log.

Can anybody help?

Running the Sonos App on my GrapheneOS mobile emulating Android

What about genuine android device?

Running the Sonos App on my GrapheneOS mobile emulating Android

What about genuine android device?

Similar results on my old Samsung Galaxy-S8 running genuine android ...

I found What happened to the Sonos app? A technical analysis. It's possible that the original setup of my (now deceased) Sonos Roam was completed successfully with the old app and it is the new app that is causing problems with my replacement Sonos Roam 2.

Would Packet Sniffer help in diagnosing the problem? I note the caution Unicast traffic between Wireless clients with client-to-client forwarding enabled will not be visible to the sniffer tool.

Would I need something like Kismet running on a separate system to investigate further?

Would Packet Sniffer help in diagnosing the problem?

Can you then analyse captured packets?

Post your full config, let's check what settings you have.

Would Packet Sniffer help in diagnosing the problem?

Can you then analyse captured packets?

I have set up Kismet on a system with an Intel AX200 WiFi card. All three devices are on my desk within 250mm of each other. I have captured WiFi traffic during an attempted setup of the Sonos Roam 2 to a .pcapng file and inspected it with Wireshark but can't see anything obvious ...

Post your full config, let's check what settings you have.

Generated with: export hide-sensitive file=sonos_config

I'm wondering if it could be an mDNS issue?

My mobile is issuing several but doesn't appear to be receiving any responses.

v7.16 [stable] is released! contains:

*) dns - added support for mDNS proxy;

There is also a /ip/dns/set mdns-repeat-ifaces=.... It isn't set in my current configuration.

There is some discussion from @Amm0 and others under the release announcement. Maybe something is required to provide an answer to the mDNS query?

I'm wondering if it could be an mDNS issue?

My mobile is issuing several

Code: Select all

Standard query 0x0005 PTR _sonos._tcp.local, "QM" question

but doesn't appear to be receiving any responses.

v7.16 [stable] is released! contains:

*) dns - added support for mDNS proxy;

There is also a /ip/dns/set mdns-repeat-ifaces=.... It isn't set in my current configuration.

There is some discussion from @Amm0 and others under the release announcement. Maybe something is required to provide an answer to the mDNS query?

I have tried: where bridge is all my LAN interfaces (ether1; ether3; ether4; ether5; wifi1; wifi2).

Don't know if this is how it is supposed to be used? Documentation is minimal. Still couldn't set up my Roam 2.

The output of: (run on Ubuntu 24.04.1 LTS) doesn't appear to change whether or not mdns-repeat-ifaces is set. It was interesting to see the output! Saw some services I didn't know I had on my local network.

Maybe I'm looking in the wrong direction? As there are no other Sonos devices on my local network then perhaps no response to _sonos._tcp.local is the expected result?

I suspect this may not be a Mikrotik specific issue.

Tried with a Wi-Fi Hotspot on an Ubuntu 24.04.1 LTS system with an Intel Ax200. Roam 2 setup failed ...

Tried with my old Buffalo WZR-HP-G300NH (rtl8366s) running OpenWrt 23.05.5. Roam 2 setup failed ...

Hoping that the SONOS Community can provide an answer.

Mikrotik is Innocent OK.

Managed to get my Sonos Roam 2 setup by following these steps:

1. Sonos App - force stop
2. Sonos App - uninstall
3. Android - restart
4. Android - connect to network (on Mikrotik)
5. Android - install Sonos App
6. Roam 2 - Factory reset
7. Sonos App - setup

Seriously weird behaviour!