NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
XR500 LAN IP DHCP glitching out
So occasionally (Usually 3-14 days uptime), the router stops assigning LAN IPs. Usually first, I can no longer access the DUMA OS interface from LAN. Then the internet stops working and I can't visit...
That_GamerYT I usually recommend doing so from the interface if you have access and the button if for some reason you don't
I'm on Traffic Prioritization and I noticed someting new. Whenever I add a rule that's "Basic" or "Advanced" it asks me to choose the traffic type. I'm adding a game so I chose Gaming/Voice. What do the other options do that's different? Also, if I check apply to WAN, will it still apply to my LAN too?
The traffic type specifically applies to QoS over wireless, this doesn't affect wired devices. The wireless standard eseentially includes different priority channels so we take advantage of this for QoS. Apply to WAN appends the priority tags to priority traffic as it goes out the WAN, it's not necessarily measurable whether the next hop will do anything with this priorirty tag, but there's no harm in trying it!
Alright so the beta definetely fixed the IP assignment glitch. However, this time, although my devices still had IPs (And still had access to the Router from LAN), I lost internet access (And I'm pretty sure I lost local communication as well because my PS4 share play lost connection when that happened). What's werid is that when this happened, I was playing a game, and I had traffic priotritization on that game. My game was still connected, but any other device/service wouldn't work. As soon as I disabled that traffic prioritization rule, my game instantly lost connection. I then changed the DNS server from "1.1.1.1" "8.8.8.8" "1.0.0.1" to "Get Automatically from ISP" and then the connection came back on. I'm not sure why this happens, but it's kind of weird. This on the beta though so this is expected. The Router still has internet connection because connection benchmark still works.
Thanks for letting us know!
Do you still notice this issue if you completely disable QoS from the three-line menu in Congestion Control?
I'm not sure why DNS would've had an affect here but perhaps change it back to what you had before so we know we're only changing one variable at a time during troubleshooting.
