NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
DunePilot
Apr 21, 2019Aspirant
Can't check Enable QoS box on RAX80 Web UI
Setup is 1G xfinity service, Netgear CM1150V modem, Netgear RAX80 Router, Router on 1.0.1.56 Firmware.
I'm having random 5 second lagspikes/packet loss in games and want to enable QoS. In the www.routerlogin.net setup I can click on QoS under basic or advanced and look at the page, I can run the speed test, I can select the auto config but I cannot actually turn on QoS, the enable QoS button is available but no amount of clicking will put a checkmark in that box. The box is not greyed out.
I have tried with 5 different web browsers, the box is unlocked but cannot be selected in each browser.
Is this a known issue with 1.0.1.56 Firmware and will there be an update soon, should I roll back to 1.0.1.40, is a new firmware coming soon or perhaps is it another issue? Thanks.
7 Replies
Sort By
- DunePilotAspirant
If you aggregate the lines for 2GB then it turns off QoS. Surely that is not working as intended. Rolled back the firmware while on the phone with Tech Support after letting them log the issue. I still couldn't enable QoS after firmware rollback, went back to latest firmware and then factory reset. Was able to turn QoS on, but aggregating the two ports (WAN aggregation in settings) turns QoS off and makes the QoS button unclickable.
Hard to say - in general (Netgrar's) QoS does not make any sense on Internet connections with these bandwidth, it will create an impact on the performance. Potentially - and now I'm on a wild guess - the embedded dedicated data stream processor where this QoS is run can't deal with that bandwidth (or it was simply not easy enough to redirect the [most likely again Linux bonding] software aggregation port to it).
Netgear, and just about everyone else, recommends disabling QoS on Internet speeds much faster than 300 Mbps. That's a bit slower than the original advice, but as you say QoS puts a load on the router, so implementing it seems to be a pointless exercise.