I have a Ubiquity Unifi network with a separate VLAN for my Sonos speakers. They all work perfectly fine (set on SonosNet) + a Roam on WiFi, except for the Era 100 (which is connected to ethernet with the Sonos Combo Adapter). I am unable to connect any device via AirPlay. When I move the Era back into LAN (same VLAN as other devices) it works instantly.
Page 2 / 2
I updated to today’s device update (82.2-59204) but still Airplay is broken to my ERA100’s and continues to work to my Arc. Other services continue to work to the ERA100’s so it just seems to be Airplay affected again.
Has anyone had any joy with this update please?
Spent a little time digging into the issue. To recap, though, everything was working fine until the `81.1-58210` software release which was installed across my system on Oct 21st. Airplay across VLANs worked fine with all speakers; after the system update, Airplay across VLANs stopped working with the newer speaker hardware.
The issue is that the Precision Time Protocol service does not start up properly on the newer speakers. When an Airplay stream is initiated, the sending device contacts the speaker on port 7000. As the devices negotiate the Airplay protocol, the Airplay device starts sending PTPv2 packets to ports 319 and 320 on the Sonos speakers. The speaker initially responds with some ICMP “port unreachable” responses because the Precision Time Protocol service is still starting up, but eventually the speaker starts sending back PTPv2 packets so the devices can coordinate on time and account for audio delay.
The newer Sonos speakers never send PTPv2 packets in response. The Airplay device is sending these packets to coordinate on time, but the Sonos speaker always responds with the ICMP “port unreachable” packets - it never starts listening for these PTPv2 packets.
Again, this only happens across VLANs - if both devices are on the same subnet, then the issue does not happen.
For corporate environments (retailers, etc) keeping devices like Sonos speakers, lighting systems, etc separate from the point-of-sale terminals is very important from a security perspective. For home users, this security by separation is just as important especially with some work-from-home environments.
Hopefully this is an error / oversight and not an intentional change by Sonos, and hopefully Sonos can remedy the situation in a future software update.
PS - If any engineers at Sonos stumble across this thread, please feel free to contact me directly and I can provide some tcpdump packet captures that illustrate the issue. The initial Airplay handshake with the speaker is successful; the speaker just never responds to PTPv2 packets on ports 319 or 320.
Cheers!
Just registered to say thank you for your profound investigation
The latest firmware update apparently has now allowed the desktop app to be able to find my system when I’m on my main VLAN. Previously, I had to be on the IoT VLAN for the desktop app to see it. Reading what tim_p wrote, that explains maybe why my I’m unable to Airplay to the Arc Ultra as that is newer hardware.
Here’s my theory: Sonos intentionally broke AirPlay over VLAN on the current Era 100 so that they can include it as a feature in the Era 100 Pro.
And the saga continues! I have contacted Sonos technical support.
1 - The phone support connects you with a call center where the people working there can barely hear what you are saying because of the large amount of background noise. It took 50 minutes on hold to finally be connected with a person. I could hear about seven different background conversations, and I had to repeat myself at least three times for every question the support technician asked.
2 - After 30 minutes on the phone where the support technician reads from the support documents you can find online, I finally asked them to escalate the issue to the next level support team. The problem is they had a very old email in their system that I no longer use. I had changed my email address with Sonos over three years ago, but this old email showed up in the support system.
3 - I had to contact Sonos support again through the chat window and update my email address with them that way. The chat system is just a robot - you have to explicitly ask to talk to a person who can then help you.
4 - It has now been over a week, and I have not heard anything from Sonos at all. Not even an acknowledgement that this support ticket exists and that the ticket is in a queue to be looked at.
5 - Contacted the Sonos support chat system again today to ask for a status. They have no idea when it will get looked at, nor do they have any estimate on the timeline.
So I’m in support limbo at the moment. Someone might look at the issue or they might not. Someone might send me an email or they might not.
Sonos might care about customer support, or they might not.
If anyone on the forums here tells you to contact Sonos support, this is what you get to look forward to.
Cheers, and Happy Holiday!
I have an appointment with Level 3 Engineering on Wednesday to discuss this issue.
I have an appointment with Level 3 Engineering on Wednesday to discuss this issue.
if you need some more people joining the call, I would be gladly to join as a Network Engineer.
I have an appointment with Level 3 Engineering on Wednesday to discuss this issue.
Thanks for this, and for taking the time to post what you find.
Sonos has taken a nose-dive in customer service ever since they released the “new” app to work with their headphones. It has broken what was existing functionality. I’ve had more hassles than ever with Sonos since then, and I’m STILL running everything on the same VLAN.
I’d also like to move Sonos to an IoT-type VLAN, and I’m really looking forward to whatever you find.
Just finished a great conversation with Mike in engineering. We reviewed tim_p’s debugging write-up and I confirmed that I can see packets going to my Era 100 on ports 319 and 320 but nothing coming back, every other AirPlay device continues to function across VLANs, this used to work before the October update, etc. Also discussed why VLAN support on Sonos devices is necessary for security, especially with the shift to cloud control. Mike understood the issues and will be opening up a bug report.
I will share updates on the progress of the bug report as I receive them.
Great news and thank you for your efforts! Hopefully this also address VLAN issues with the other newer hardware like the Era 300s and Arc Ultra, which is where I’m in.
Reply
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.