Unable to connect to PC via WiFi AirLink

[Sajgoniarz]

I recently upgraded my home network with Mesh System (AiMesh from ASUS) and since then Quest 2 is no longer able to connect to PC despite listing it, when PC is wired to node.
if i connect PC to main router via WiFi then AirLink is able to connect, however lag makes it useless.
Problem is not existing in another applications connection to PC ex. Virtual Desktop.
Meta, please fix it.

[MetaNinjaTurtle]

Hey there @Sajgoniarz!

Thanks for posting on the Meta Quest Community Forums!

What I think your issue might be is that whenever your PC is connected via ethernet to a node, the node acts a secondary router, so it creates their own separate network. Suppose node A is under 192.168.1.0 whereas Main Router subnet is 192.168.0.0, so airlink might be having a hard time configuring to and connecting to the PC as it can't find the main network, i.e. the main router.

Here is an image of what I assume your current network is:

What you could do is configure your Mesh nodes as Internet Access Points, which allows them to act as extensions of your main router under the same network, that way you should be able connect your Quest 2 to your PC without having to connect to the main router as your whole mesh network would be under the same network that the main one is in.

E.g. This is what the network would be when setup as IAP:

So all the devices are under the same network of 192.168.0.x so pretty much any device should be able to be connected and found in your network.

Here is a link on how to set it up using ASUS ai mesh -> Link

Here is also an article by ASUS -> Link

Here is also a reddit thread I found which might be able to further help you out -> Airlink and Mesh Network

Thanks and hope this helps!🐢

[Sajgoniarz]

Hi!

Thanks for the answer, however that's not the root cause.
All my endpoints are in single /24 subnet and second router is operating in AiMesh Node.
I actually came here after reading the Reddit threat you mentioned, because the only working configuration seems to be wired connection between router and node and it's not an option for me.
Since other software have no issues with wireless mesh configuration the conclusion is simple - there is a bug in Quest Link drivers.

 

[MetaNinjaTurtle]

Hey there @Sajgoniarz!

I understand, I appreciate that you've already tried it, and I'm sorry that it didn't work for you.

My assumption is that the issue could also stem from the router models itself as well, from the reddit thread seems like majority of users who resolved their issue or aren't encountering any are using TP-Link mesh routers. Possibly in future driver updates more router models and manufacturers could be included, so stay tuned for it!

For now, I'd like to ask you to send our engineering team a bug report, you can do so by following the steps here: Submit a Bug Report

Please be as descriptive as possible when filling out the bug report to give our team as much information as possible to look into this issue you're encountering!

If you need to contact our support team for further support or any other queries you can contact them here.

I understand this may not be the answer you're looking for but I appreciate your understanding and thank you! 🐢