Contributor I

Answered

Unable to AirPlay to Era 100 in separate VLAN (Ubiquity)

48 replies
3733 views

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.

This topic has been closed for further comments. You can use the search bar to find a similar topic, or create a new one by clicking Create Topic at the top of the page.

Stanley_4Answer

Grand Maestro

Sonos needs to be on a single network

Show previous replies

K

kepik

Lyricist II

Following this keenly. I wonder if anyone can confirm if today’s player update has addressed the issue? I won’t have time to test until this weekend as I’ll have to (re)reconfigure my network.

Still can’t Airplay on my Arc Ultra + Era 300s

K

kingebeng

Trending Lyricist I

No Airplay unfortunately

However it does work over the Sonos app.
Dont know if this was working before (probably call2home functionality, no direct play towards the speaker)

jarylc

Lyricist III

Following this keenly. I wonder if anyone can confirm if today’s player update has addressed the issue? I won’t have time to test until this weekend as I’ll have to (re)reconfigure my network.

Still can’t Airplay on my Arc Ultra + Era 300s

Yup same here, looking at tcpdumps on my router, the issue is still present

15:19:52.800887 IP 172.27.15.4 > 172.27.14.171: ICMP 172.27.15.4 udp port 319 unreachable, length 80
15:19:53.822932 IP 172.27.15.4 > 172.27.14.171: ICMP 172.27.15.4 udp port 319 unreachable, length 80
15:19:54.871412 IP 172.27.15.4 > 172.27.14.171: ICMP 172.27.15.4 udp port 320 unreachable, length 120
15:19:55.822052 IP 172.27.15.4 > 172.27.14.171: ICMP 172.27.15.4 udp port 319 unreachable, length 80
15:19:56.831136 IP 172.27.15.4 > 172.27.14.171: ICMP 172.27.15.4 udp port 319 unreachable, length 80

.15.4 is my Arc Ultra, .14.171 is my iPad

K

kingebeng

Trending Lyricist I

Following this keenly. I wonder if anyone can confirm if today’s player update has addressed the issue? I won’t have time to test until this weekend as I’ll have to (re)reconfigure my network.

Still can’t Airplay on my Arc Ultra + Era 300s

Yup same here, looking at tcpdumps on my router, the issue is still present

15:19:52.800887 IP 172.27.15.4 > 172.27.14.171: ICMP 172.27.15.4 udp port 319 unreachable, length 80
15:19:53.822932 IP 172.27.15.4 > 172.27.14.171: ICMP 172.27.15.4 udp port 319 unreachable, length 80
15:19:54.871412 IP 172.27.15.4 > 172.27.14.171: ICMP 172.27.15.4 udp port 320 unreachable, length 120
15:19:55.822052 IP 172.27.15.4 > 172.27.14.171: ICMP 172.27.15.4 udp port 319 unreachable, length 80
15:19:56.831136 IP 172.27.15.4 > 172.27.14.171: ICMP 172.27.15.4 udp port 319 unreachable, length 80

.15.4 is my Arc Ultra, .14.171 is my iPad

Can you check the TTL’s of the packets?

jarylc

Lyricist III

Following this keenly. I wonder if anyone can confirm if today’s player update has addressed the issue? I won’t have time to test until this weekend as I’ll have to (re)reconfigure my network.

Still can’t Airplay on my Arc Ultra + Era 300s

Yup same here, looking at tcpdumps on my router, the issue is still present

15:19:52.800887 IP 172.27.15.4 > 172.27.14.171: ICMP 172.27.15.4 udp port 319 unreachable, length 80
15:19:53.822932 IP 172.27.15.4 > 172.27.14.171: ICMP 172.27.15.4 udp port 319 unreachable, length 80
15:19:54.871412 IP 172.27.15.4 > 172.27.14.171: ICMP 172.27.15.4 udp port 320 unreachable, length 120
15:19:55.822052 IP 172.27.15.4 > 172.27.14.171: ICMP 172.27.15.4 udp port 319 unreachable, length 80
15:19:56.831136 IP 172.27.15.4 > 172.27.14.171: ICMP 172.27.15.4 udp port 319 unreachable, length 80

.15.4 is my Arc Ultra, .14.171 is my iPad

Can you check the TTL’s of the packets?

22:31:07.454573 IP (tos 0x0, ttl 254, id 0, offset 0, flags [DF], proto UDP (17), length 104)
    172.27.14.171.320 > 172.27.15.4.320: [no cksum] PTPv2, v1 compat : yes, msg type : announce msg, length : 76, domain : 0, reserved1 : 0, Flags [timescale, unicast], NS correction : 0, sub NS correction : 0, reserved2 : 0, port id : 32826, seq id : 1, control : 5 (Other), log message interval : 254, originTimeStamp : 0 seconds 0 nanoseconds, origin cur utc :37, rsvd : 0, gm priority_1 : 250, gm clock class : 248, gm clock accuracy : 33, gm clock variance : 17258, gm priority_2 : 238, steps removed : 0, time source : 0xa0
22:31:07.454646 IP (tos 0x0, ttl 254, id 0, offset 0, flags [DF], proto UDP (17), length 134)
    172.27.14.171.320 > 172.27.15.4.320: [no cksum] PTPv2, v1 compat : yes, msg type : signalling msg, length : 106, domain : 0, reserved1 : 0, Flags [timescale, unicast], NS correction : 0, sub NS correction : 0, reserved2 : 0, port id : 32826, seq id : 0, control : 5 (Other), log message interval : 128, port identity : 0x0, port id : 0
22:31:07.462227 IP (tos 0xc0, ttl 64, id 6838, offset 0, flags [none], proto ICMP (1), length 132)
    172.27.15.4 > 172.27.14.171: ICMP 172.27.15.4 udp port 320 unreachable, length 112
	IP (tos 0x0, ttl 254, id 0, offset 0, flags [DF], proto UDP (17), length 104)
    172.27.14.171.320 > 172.27.15.4.320: [no cksum] PTPv2, v1 compat : yes, msg type : announce msg, length : 76, domain : 0, reserved1 : 0, Flags [timescale, unicast], NS correction : 0, sub NS correction : 0, reserved2 : 0, port id : 32826, seq id : 1, control : 5 (Other), log message interval : 254, originTimeStamp : 0 seconds 0 nanoseconds, origin cur utc :37, rsvd : 0, gm priority_1 : 250, gm clock class : 248, gm clock accuracy : 33, gm clock variance : 17258, gm priority_2 : 238, steps removed : 0, time source : 0xa0
22:31:07.462316 IP (tos 0x0, ttl 63, id 57192, offset 0, flags [DF], proto TCP (6), length 52)
    172.27.14.254.1400 > 172.27.15.4.39546: Flags [.], cksum 0x4f0e (correct), seq 1, ack 2111, win 496, options [nop,nop,TS val 2026687229 ecr 4267826555], length 0
22:31:07.462971 IP (tos 0xc0, ttl 64, id 6839, offset 0, flags [none], proto ICMP (1), length 162)
    172.27.15.4 > 172.27.14.171: ICMP 172.27.15.4 udp port 320 unreachable, length 142
	IP (tos 0x0, ttl 254, id 0, offset 0, flags [DF], proto UDP (17), length 134)
    172.27.14.171.320 > 172.27.15.4.320: [no cksum] PTPv2, v1 compat : yes, msg type : signalling msg, length : 106, domain : 0, reserved1 : 0, Flags [timescale, unicast], NS correction : 0, sub NS correction : 0, reserved2 : 0, port id : 32826, seq id : 0, control : 5 (Other), log message interval : 128, port identity : 0x0, port id : 0

J

jt987654321

Lyricist I

Just piling on, but I am running into the same thing with Unifi VLANs and the Era 100.

Setup:

Theater → ARC + Sub + 2 One SLs (Grouped, all wireless)
Office → Era 100 (wireless)
All Sonos devices are in a VLAN for AirPlay devices (Connected over 2.4ghz on a dedicated IoT wifi)
Personal devices are in a VLAN for users (Connected on a 2.4ghz/5ghz on a dedicated home wifi)
Guest VLAN for visitors (Connected on a 2.4ghz/5ghz on a dedicated guest wifi)
Home/Guest users can initiate traffic with the Sonos VLAN and it is allowed to return traffic only

Why? So I can share AirPlay devices with different people in the house, as well as protect myself from Sonos interrogating my network and collecting more data than necessary.

No matter what I try, I cannot get the Era 100 to allow AirPlay. I can stream directly to it with the Sonos app, but not AirPlay. However, AirPlay works fine with the ARC based theater group. The Era device can be seen by AirPlay, so the announcements work. It just won’t connect.

I even went as far as putting the home and AirPlay VLANs in the same firewall zone and allowing ANY<-->ANY on all ports. Still nothing from the Era.

I’ve also tried rebooting it...in case anyone from Sonos IT reads this :)

controlav

Lead Maestro

Now I don’t understand the details of mDNS, VLANs or Airplay, but this person does:

https://www.derekseaman.com/2023/10/part-3-smart-home-matter-and-thread-deep-dive.html

Flatten your network. All of your IoT devices, smart home hubs (like Apple TV) and Home Assistant servers should be on the SAME VLAN. If you really want to isolate your IoT devices, go for it, but put your HAOS server and smart home hubs on that IoT VLAN and just open TCP ports to HA from your primary network as needed. This is vastly safer than trying to do mDNS forwarding across VLANs. mDNS is designed to be used in a single layer 2 domain, so don’t expect it to work reliability across VLANs. Just don’t!!!!

There’s a lot in the post I linked, but it seems to be clear: mDNS between VLANs is a very bad idea.

Author of the leading independent Sonos apps for Android, MacOS, iOS, Windows and Xbox.

J

jt987654321

Lyricist I

So the advice is to let every piece of cheap IoT gear see your whole network and phone home? If all of your IoT, Hubs, and Controllers are in the same VLAN, that is pretty much everything in most households. Outside of this single issue with the Sonos Era 100, all of my other devices work great in this configuration. They can’t see anything except the home hubs.

Sign up

Login to the community