Oculus Quest has no Internet when on Pi-hole DNS

Help Community Help
,
1

Please follow the below template, it will help us to help you!

If you are Experiencing issues with a Pi-hole install that has non-standard elements (e.g you are using nginx instead of lighttpd, or there is some other aspect of your install that is customised) - please use the Community Help category.

Expected Behaviour:

Oculus Quest would use Pi-hole for DNS and all other Quest functionality would be maintained. This is on a Quest 2 VR headset running version 37.0.0.147.109.346379382. Pi-hole is version 5.8.1, FTL is version 5.13, and the web interface is 5.10.1. This is running as a docker container on a QNAP NAS.

Actual Behaviour:

Oculus Quest 2 gets an IP address but can't connect to the Internet (browser doesn't work, and the Quest UI explicitly says it can't connect to the Internet, but it is connected to the Wi-Fi network). When I switch the Quest network to static (and setup the IP address manually), it connects to the Internet right away. Then I switch back to DHCP, restart the headset, and have Wi-Fi but no connection to the Internet. Lather, rinse, repeat. Then I tried using a static IP configuration BUT used manually added the IP address for the Pi-hole DNS (10.15.15.3). No Internet as far as Quest is concerned. I would have tried browsing to a local IP address (such as the Pi-hole server), but I'm using our guest Wi-Fi network due to its relatively short passcode, as opposed to the code for our normal Wi-Fi that I had to remove to do these tests (that passcode is 63 characters, totally random, and is super-hard to enter in Quest just the one time, so no way I'll enter it a bunch of times while doing this troubleshooting, and the guest network is otherwise normal except it can't access any local addresses, only the Internet... when it works).

My guess is that there is some address that the Quest must access in order to activate Internet access for the rest of the applications on the headset, and Pi-hole is blocking that address.

Debug Token:

https://tricorder.pi-hole.net/Rm4zcIKt/

2

I'm a bit confused: I posted this issue in the "Help" group. The "Community Help" group is specifically for people who have an issue with a custom setup. I don't have a custom setup. Yet the issue was unceremoniously kicked into this group.

Am I missing something?

3

Forgive a stupid question... Is this not the issue here? If a device on the guest network cannot see local addresses, then surely it is just sending it's DNS requests into the abyss?

1 Like
4

Well, yes and no.

Currently, you are correct (and I should have caught that). The Wi-Fi router will indeed keep the guest clients from seeing the Pi-hole DNS server (at least in the current configuration).

But... originally I had the Quest using the standard Wi-Fi network (the one with the 63-character passcode), and that one was choking.

So, you bring up a great point... how to re-test the network connectivity of the Quest headset without having to re-enter that absurdly long code more than once (it is SUPER painful to do even under good circumstances).

The ball is squarely back in my court. I'll re-group and see if I can find a way to get the code in a copy-paste situation, or see if it is possible to change the guest network so it allows access to the Pi-hole server. I'll post the results when I have some...

5

@PromoFaux : I figured out a way to cut-paste the code (good thing), AND was also able to change my guest network (temporarily) to allow it to talk to the rest of the network. Once the guest network was opened up, I'm now finding the Oculus is getting to Pi-hole and seems happy. Then I put it on the standard Wi-Fi network, and again, it is still working fine.

Dunno what was the original network difficulty that started me down the rabbit hole, but looks to be no more.

Thanks!

6

This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.