TL;DR Enable “Multicast Enhancement” in Unifi under Wifi > Network > Advanced
Ubiquity Unifi Wi-Fi Access Points with Oculus Quest 2 VR Headsets. Since purchase I have only bee able to get casting working once and I’m now assuming it was a fluke. Was at a friends place the other day and it worked perfectly casting to an iPad on their Netgear Nighthawk AP.
Get it home and was continually getting “unable to connect” warnings no matter which end (the headset of the iPad) initiated the cast.
Oculus support site was not useful, only mentioning P2P traffic must be allowed
Did a Wi-Fi packet capture and noted the 224.0.0.X address packets. which lie in the 220.127.116.11 > 18.104.22.168 multicast address range.
Ubiquiti Unifi Control Panel notes “Multicast Enhancement’ as “Permit devices to send multicast traffic to registered clients at higher data rates.”
Which suggests the AP’s do rate limiting of Multicast address range packets normally, likely to prevent network storms, but also effecting oculus streaming/casting.
This rate limiting likely lets the iPad initiate the connection, and then as soon as the video stream starts it crashes.
Turning Multicast Enhancement on for the SSID which your Quest 1/2 and mobile device resolved the issue for myself.
It seems odd to use multicast, unless they are anticipating multiple devices to be receiving the casted video.
Other changes made as a part of testing were to confirm Avahi/mDNS service settings on pfsense and confirm no DNS issues as the Unifi CK was reporting a DNS resolution issue for the headset while it was having casting issues. These aren’t necessary for this fix but may lead you down other paths if its still not working after enabling Multicast Enhancement in Unifi.
This did help, but only got the streaming working for about 10-20 minutes before it fails. Are you seeing the same issues?
I think the 10-20 minute dropout just falls within the normal issues of oculus streaming. I have experienced them as well.
I’ve also found that streaming will stutter and/or fail more frequently when the headset’s battery is bellow 30% capacity. Likely a CPU/GPU clock speed limit at low battery voltage.