Re: wifi is unstable (2024)

Hi everyone;

I have a Quest 3 and cannot connect the the wifi (it's a freebox, french internet provider).

Steps i took to troubleshoot :

1 - I did manage to connect the quest to my cellphone via hotspot.

2 - I factory reseted the quest and retried to connect to the freebox via passwords and QR code.

3 - I trued to connect the quest via the phone app.

4 - Rooter was rebooted, i was in the same room etc.

5 - We have all other devices connecting without problem to this rooter.

Thanks for your help

Tony_

• Labels:
• Meta Quest 3

In response to Jiphou

In response to polozmrd.udatny

0Kudos

In response to TheLegend27

Thanks for responding.

Software update 50111670059300510

Version 67.0.0.562.356.6184855700

Runtime version 67.0.0.565.358.618485551

I'm using a BT smart hub dedicated to VR, directly connected to my PC. 2.4ghz is off, so 5ghz only.

My Quest 3 drops out frequently. Sometimes it will be half an hour, sometimes it will be 10 minutes, but it will ALWAYS do it after no longer than half an hour. It just seems random.

My Quest 2 will stay connected, in fact, I don't recall ever having a disconnect with it in two years.

In response to TheLegend27

@paul.frampton.754@samebeatThank you for getting back to me with that. I just forwarded these reports to the team, so hopefully I'll have more info soon on what the next steps are.

Technology, at a certain level of sophistication, is indistinguishable from magic. - some wise guy or something probably

0Kudos

In response to TheLegend27

For now it seems I succeeded solving the issue following the advices of@BlackCat, I modified the mode of my router TPLINK Archer that was in AP to put it in normal router mode. So my configuration is the following:
1-A server from my FAI feeds a local network of all my connected devices in wifi 5, 5Ghz wireless as well as in LAN under a 192.168.0.xx adresses network using a DHCP addressing mode. It’s local adress is 192.168.0.1
2-it feeds also by RJ45 cable from its built in Ethernet switch the WAN of a TPLINK Archer router dedicated to the wireless interface with the Q3 as well as the LAN RJ45 Gbit interface with my high end PC for PCVR flight sim using Virtual Desktop.
3-)This Archer is seen under the general local network at a fixed adress 192.168.0.191 through its Mac adress. It is itself configured separately as a 192.168.1.1 dedicated router and is not using its own DHCP capability to communicate with the LAN cable connected high end PC but also through a fixed stable adress at 192.168.1.167 using the PC Mac adress.

4-The Q3 is then connected wirelessly to the TPLINK using also the Q3 Mac adress and a fixed adress in the TPLINK dedicated network 192.168.1.143. Wireless link is done in wifi 6E at 6Ghz only in 802.11ax with only 2 clients, 1 LAN is the PC 1 wireless is the Q3. Channels are 160Mhz auto (PC)

i played DCS 3 hours without a single disconnection with this configuration while I had generally 2 or 3 per hour while the TPLINK was in AP mode. Of course for multiplayer game I had to change my server port forwarding that was directed formerly straight to my PC to my router TPLINK and use a NAT forwarding of port inside the TPLINK toward the PC for these same ports (also adding this ports allowance in the windows firewall but it was already done before ). I will make more test duration next days and keep the community informed of the result. I am under the V66 firmware (last stable FW distributed in France)

0Kudos

0Kudos

i had to factory reset and can't enable PTC anymore so, back to having a q3 that doesn't work 😞

some news sources are claiming v67 is out, though there's no update tohttps://www.meta.com/en-gb/help/quest/articles/whats-new/release-notes/. any idea when we'll actually be able to get v67 / back into PTC with the fix?

0Kudos

In response to Jiphou

Glad it worked. Even if you thanked the wrong user 🙂
What would be much more important is that meta notices this. Because it's definitely not the quest's fault. The most important note is: the problems occur when the internet router and quest are in the same subnet. and disappear if they are not. So similar to the restrictions in a guest network.

Despite solving the problem for me... I'm still interested in Meta recognizing the problem. so that this solution is not torpedoed in a subsequent update.

0Kudos

0Kudos