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 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?
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 …
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:
avahi-browse --all
(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?