Sonos stopped working, cannot find speaker on same network

Started by TrueType, January 10, 2021, 02:16:31 PM

Previous topic - Next topic
Hello, many topics about Sonos not working on different VLAN's but I have had a working configuration on the same VLAN for about 1 month but now suddenly my Phone cannot find the Sonos Move Speaker on the same network... Sometimes it finds it for a little while but then it disappears again. I have looked into the logs but cannot se any denies.. Neither is any ports blocked, it has been working flawlessly for a month... Any suggestions is very appreciated!

When devices are on the same network segment packets don't go via the router unless you are bridging interfaces.
OPNsense 24.7 - Qotom Q355G4 - ISP - Squirrel 1Gbps.

Team Rebellion Member

Quote from: marjohn56 on January 10, 2021, 03:54:09 PM
When devices are on the same network segment packets don't go via the router unless you are bridging interfaces.

Okey, yeah so it's even more strange it didn't work since they are on the same network. Now I tried resetting the Sonos and put it on my 2.4Ghz Wifi instead of 5Ghz and it seems more stable even though my phone is on the 5Ghz network. It has been working for about an hour now at least. Maybe has something todo with my UAP-AC-Pro

Probably. Buddy of mine had similar issues on his network with his iPhone, iPad and Sonos. I cannot remember what he did to solve  the issue. He does have his speakers on a separate VLAN and is using UDPBroadcastReleay, though the issue was with the Apple stuff.
OPNsense 24.7 - Qotom Q355G4 - ISP - Squirrel 1Gbps.

Team Rebellion Member

Quote from: marjohn56 on January 10, 2021, 04:39:07 PM
Probably. Buddy of mine had similar issues on his network with his iPhone, iPad and Sonos. I cannot remember what he did to solve  the issue. He does have his speakers on a separate VLAN and is using UDPBroadcastReleay, though the issue was with the Apple stuff.

Aah okey, yes I have found multiple topics about having Sonos on separate VLAN.

It's been working since my last post, so I take it as it is working now. :)