Forum Discussion

ryan.mcgaughy's avatar
ryan.mcgaughy
Honored Guest
1 month ago

Static IP bug?

New to using Meta Quest, but notice the UI appears Android-based. I'm trying to connect my Quest 3 device to my network using a static IP address however tcpdump shows no traffic coming from the device. When set to DHCP, I do see the BOOTP/DHCP frames sent. Other android-based devices do not have this problem and I can't find any references to similar issues in these forums.

Other forums did have the suggestion of assigning the address before connecting to the network, but that showed the same behavior. Any recommendations?

Revised: Asked an LLM about this and it reported this is a quirk in the TCP/IP stack for Quest. Has anyone fixed this??

3 Replies

  • steve_40's avatar
    steve_40
    Honored Visionary
    1 month ago

    It is indeed Android based.

    I've never heard of issues using a static IP with the Quest, it's usually the other way around - users have resolved wifi connection issues by switching from DHCP to static IP.

    As this might be a recent bug, you can report the issue using the headset Quick Settings>Report Problem.

    • ryan.mcgaughy's avatar
      ryan.mcgaughy
      Honored Guest
      1 month ago

      Multiple LLMs report this is a known issue in Quest (once again, works on other androi-based devices). Apparently the network stack won't initialize unless it receives an ACK packet. This should be easily testable and I would suspect, easily fixable.

      I ended installing dnsmasq and being done with this.

       

      Since I'm washing my hands of this, my initial (untested) idea was running this:

      echo -n "$binary_dhcp_ack" | nc -u -w1 <client_ip> 68

      • steve_40's avatar
        steve_40
        Honored Visionary
        1 month ago

        I actually tried setting the wifi to static on my Quest 3 today, and as soon as I change it from DHCP to Static, it won't let me save the settings, the button just greys out.