Quest 3 Sometimes Gets Stuck on “Obtaining IP Address” with Mesh Wi‑Fi

0
0
Asked By MellowCedar42 On

For the past few weeks, my Quest 3 has intermittently failed to connect to the Wi‑Fi from our Linksys MX5500 mesh system. It gets stuck at "obtaining IP address," although it connects normally to the Wi‑Fi broadcast directly by the modem. Other devices have no trouble using the mesh network, and the headset sometimes connects successfully on other days. Both the router and headset support Wi‑Fi 6, so compatibility should not be the issue. I've rebooted the mesh node and tried switching between randomized and device MAC addresses, but neither helped. The problem started after several years of trouble-free use, with no recent headset software changes besides installing games. What could be causing this, and what can I try to fix it?

2 Answers

Answered By BrightHarbor6 On

A dedicated Wi‑Fi 6 access point or router would usually be the most reliable setup for VR, but given your layout, try troubleshooting the existing node first. Restart the whole mesh system, not just the satellite, and check its DHCP settings and connected-device list to see whether the Quest is being assigned an address. If possible, temporarily create a separate 5 GHz SSID or disable automatic band steering. You could also test the headset close to the main mesh node; if it works there but not from the side-house node, the problem is likely roaming, signal quality, or that node’s radio rather than the Quest itself.

Answered By SilverPine_27 On

This may be an issue with the mesh system rather than the headset. Some mesh setups handle the Quest poorly, especially when steering devices between 2.4 GHz and 5 GHz or when both bands use the same network name. Other devices may reconnect without you noticing, while the headset can get stuck during DHCP and fail to obtain an IP address. Check whether the MX5500 has band steering, client steering, or roaming-assistance settings that can be disabled temporarily. Also make sure the mesh firmware is current and that the headset is connecting to the main LAN rather than a guest or isolated network.

MellowCedar42 -

A separate router isn’t really practical here. The fiber connection enters the main house, while I’m in one of the side houses, so I depend on the mesh node for coverage. The mesh otherwise works well and my ping is fine.

Related Questions

LEAVE A REPLY

Please enter your comment!
Please enter your name here

This site uses Akismet to reduce spam. Learn how your comment data is processed.