NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.

Forum Discussion

kell90's avatar
kell90
Aspirant
May 06, 2022

Nighthawk XR500 traffic prioritization feature not loading after switching to Starlink

Model: XR500
Firmware: V2.3.2.134
OS: Windows 11
-----------------------------------
Hello,

I recently just switched ISPs (Xplornet to Starlink) and I believe I have everything set up mostly correctly. However, one thing that does not load on my DumaOS QoS panel is the Traffic Prioritization settings - where I would normally specify ports on devices that I wanted to skip the queue. The router has been updated and factory reset. I have tested with both ISPs and this problem only occurs on Starlink. 

HOWEVER, if you notice in the "Traffic Overview" section, it shows that packets are being prioritized - so it's as if the default profile is being applied, but I just can't edit it at all. 

 

Here is my setup:

I saw that one Redditor suggested, "My guess would be it needs to have a public IP on the WAN interface. If you're behind Starlink's router or on CGNAT, you don't have that, maybe that disables [the traffic priority menu]. Perhaps [Netgear] feels it makes no sense to prioritize packets if you're behind NAT(s) that will interfere with that".

 

So yeah, the feature seems to work, but I can't manage it manually. Any ideas?

17 Replies

  • Your ISP wouldn't dictate whether the feature loads or not, I suspect that is a coincidence. Reboot the router from the interface, wait 2 minutes then try accessing and see if it loads correctly please.
    • agent47isn1's avatar
      agent47isn1
      Guide
      I recently got starlink the beginning of last month and finally got the Ethernet adapter about 2 weeks ago. Only problem I've had with my router (XR450) was when I updated it to the latest firmware my IP address changed from 192.168.x.x to 10.0.0.1 and I'd lose connection and regain connection within minutes of each other. Other than that every tothing else works like it should even opening ports needed for our consoles.
      • kell90's avatar
        kell90
        Aspirant

        Hmm strange. My internal IP did not change, it's still 192.168.x.x

    • kell90's avatar
      kell90
      Aspirant

      Did not solve the problem, unfortunately. I've tried various restarts and refreshes, yet this problem only persists when connected to Starlink.