QUEST 3 WiFi 6E 6GHz band not working

[mqoLtn]

Hey Guys,

im struggling to onboard the Quest 3 on my WiFi6E enabled SSID.

Currently running an enterprise grade Cisco LAP -  9136AXI (one of the most robust and expensive APs from Cisco) managed by 9800 virutal WLC running on my esxi server.

I have created a new 6GHz only SSID with really basic security settings (WPA 3, using SAE AKM suite).

All my other devices that do support 6E (Intel AX211 wireless cards on my laptops) are able to discover the 6GHz SSID but Quest 3 is struggling to do that.

Cisco by default sends the information about 6GHz BSSID in the 5GHz beacons/probe responses - this is known as RNR (reduced neighbor report) and it helps to speed up the discovery so the device doesnt have to probe/wait for beacons on all the available 6GHz channels

However i suspect that the quest 3 in its current wireless driver iteration does not support this.

I have tried different radio settings for the 6GHz. tried 20/40/80/160MHz wide channels, tried to use each PSC channel available in the ETSI region.

I have even tried to enable FILS frames (not sure if quest would even understand them) for enhanced discovery, but simply quest 3 would not find anything.

So my question here is - does Quest3 support WiFi6E, or only WiFi 6 (11ax) ? If it does indeed support 6GHz band, how does the discovery work? Does it support RNR? Does it do passive/active listening/probing on all 6GHz channels ?

There is next to none technical information about the Wireless chipset/driver behavior used in Quest3. So i'd really appreciate if someone would be able to answer my questions, preferably someone who understands the 802.11 standard 🙂

[MetaQuestSupport]

Hello, @mqoLtn! We see your Meta Quest 3 is having a little trouble connecting to Wi-Fi. We want you to have the best VR experience possible, so we're here to lend a helping hand. Here are a few nifty tips we'd love for you to try. Let us know if you've tried this:

1. Reboot the headset.
2. Remove any unsupported third-party accessories that may affect communication (such as headset covers, etc.)
3. Try connecting to a different network.
4. Perform a factory reset.

[mqoLtn]

Thanks, but i wanted some real technical information. Not your usual generated answer

I work with wireless technologies as my full-time job so I'd really appreciate if you could provide me with more technical information about the WiFi capabilities of the headset with regards to 6GHz band

Thanks

[MetaQuestSupport]

Hey there, @mqoLtn, and thank you for reaching out to the community with this! An unwired PCVR experience is like no other VR experience, and we totally understand wanting to connect as quickly as possible! The great news is that the Quest 3 does support Wi-Fi 6E in areas where it is available, and that many folks are enjoying the benefit of a 6ghz network, especially where the 5ghz band is crowded. As for the specifics you are asking for, the publicly available information for the Quest 3 is located on the main store page HERE; however, they are not as detailed as you are looking for, as you mention. It seems you are reaching out because of the issue you are experiencing, in addition to wanting the specifications, and you might want to follow along to this forum thread as it may pertain to what you are seeing: 

What Wifi 6e routers currently works bug free with the Quest 3?

Also, you may want to submit a bug report to add your voice and data to assist with our engineers finding a resolution. You can do that at the link here:

Submit a Bug Report

One more thing, if you have more interest in Quest 3 from a development standpoint you can always look into the Oculus Developer Center, here:

Oculus Developer Center

While this may not have provided the exact information you were hoping for, we sincerely hope it helps get you further along towards a resolution for your issue. In the meantime, should you have any additional questions, please don't hesitate to reach back out as we'll be happy to assist. Happy holidays!

[say.what.982994]

Facebook's headset technical support is a absolute joke. Employees are incompetent and all they do is give you the runaround. They will ask for personal information just to play games or use a app.

[heardr]

Did you ever figure this out, or were you at least able to get in touch with a wireless/technical specialist with Meta, and if so did they have an adequate response?

I am also very interested on how this setup might work as I have been looking to replace some of my 3702/3802 infrastructure with 9136 and/or 9166 APs. Also, I assume you are setting the AP up in FlexConnect mode so the traffic isn't subjected to additional latency from a CAPWAP tunnel to the 9800? 

I haven't done much with wireless VR or 6GHz networks previously, though I might suggest doing a Wireshark capture to see if you can capture the association of a working 6GHz device and the Quest 3. Comparing them might shed light on the issue. If the Quest can't locate the SSID to test the association, then perhaps you could enter the SSID manually to trigger an association request. If there is an association error it might even show up in the logs on the WLC side if you can get that far. Though from the sound of it you may have already tried much of this.

[TheAntiSocializer · Accepted solution]

Hey everyone! I just noticed this thread, so I wanted to jump in here and state that I'll be locking it. The reason being that we currently have another thread about this same topic being looked into with our internal team. This way we're able to keep all information under one umbrella for everyone to find and keep most up to date with.

If you're running into this issue at the moment, I'd suggest heading over there in order to post your experiences or any information we may be able to use. to help our team.