Netduma Fraser

Ah I can see how that would be a frustrating process, I'm not sure if there is much we can do to improve it but I will speak to the team about it

You should still see devices connected to the AP on the Device Manager as though they were connected to the XR, they may appear offline but should still work with QoS

They should be named when they connect back, best way to avoid it overall is to give them reserved IPs in LAN > DHCP

You can delete all offline devices from the Device Manager menu icon, if they reconnect then they'll just reappear but in your scenario looks like a lot are unused

Let us know how you get on but the quantity of devices shouldn't negatively impact it. It's probably the DHCP issue, though the workaround probably isn't something you want to do 40 times but if you want to try then in LAN Setting, set the DHCP range to start at .100, then assign reserved IP addresses to devices between .2 & .99 so they're out of the DHCP range, apply, reboot from the interface, wait 2 minutes and see if that stops the disconnects.

It should wipe completely and go back to 100%, how did you do the factory reset?

This is why you should use the guide I mentioned instead as that will actually more closely simulate what your normal connection will be like rather than a 3rd party test that doesn't saturate your connection

Basically enter a local site for the destination, then let it run, look at the bottom graph so you can see your ping over time. Start some downloads, you should see the ping rises, experiment with Congestion Control as above and you should see the ping go lower again. The idea is to get it as close to the ping you were seeing prior to the downloads.

Could you try downgrading to the previous version then please and see if the issues continue?

You don't need to use both, so you can disable one or the other, whichever you would prefer to use. I've changed the password for the old account and PMd you with it.

Hey, welcome to the forum! If your base connection is having those spikes that frequently and consistently it's going to be hard to tell how much of your bufferbloat results are due to that and just settings. Also even if you get your bufferbloat down to the lowest point that spiking issue will still happen and that will be the main thing affecting you as bufferbloat only occurs when your connection is saturated i.e. all your bandwidth is being used, with QoS enabled and Congestion Control lowered that can't happen. Follow the guide here: https://support.netduma.com/en/support/solutions/articles/16000074717-how-to-test-your-internet-ping while saturating your connection with downloads/streams etc. It's best to start with a high value for Congestion Control (set to Always), say 95% then do a test, decrease by 10%, test, decrease by 10% etc, until you get to a value that is pretty good and then try 5% either side of that value to see if it can be improved. It's important to note that Download & Upload on Congestion Control don't have to be the same value and that you may have a better experience with differing values.

It's up to Netgear really but I will ask the team to see what is happening with it.

At least the time has fixed so that won't be it. Could you try putting the DHCP lease time to 10 minutes so 0 hours, 10 minutes, apply, reboot, wait 2 minutes before accessing and see if that resolves it? It seems counter productive but someone in Early Access did this and it seemed to work for them.

Well done for getting it sorted, how are you factory resetting exactly?

Do not reload the backups, if you're going to do a factory reset for an issue it's best to start fresh, loading backups can basically re-introduce issues that you've essentially saved like that last one I can tell that will definitely be because of a saved config. So you'll need to factory reset and set it up clean, it won't take long and it should work a lot better.

Latest public is .134 https://kb.netgear.com/000064857/XR500-Firmware-Version-2-3-2-134

Yes you can downgrade using the 10.0.0.1/adv_index.htm page

It should only be asking that if you've entered the login credentials wrong or press cancel on it. If you really can't get past it then you'll have to factory reset.

Reupgrade through 10.0.0.1/adv_index.htm to get access then going forward reboot in the way I mentioned or from the interface, not by pulling power

Use the IP to access rather than routerlogin.net and see if that works

You'll need to keep trying the reboot/wait process until it loads up correctly

That could be why, you do not need to unplug the power, just pushing the button, waiting 10 seconds and pushing it again will do. Do that and then wait a few minutes once it turns on and see you can access and whether rebooting in this way allows you to keep access.

Not at the moment, I'm pushing Alex to do a lot of cloud stuff at the moment so think he is a bit swamped in that regard! I will remind him again though.

How are you restarting the router exactly? By pulling the power, pressing the power button or via the interface?

So you're getting the issue now with it completely disabled before a reboot as well? We have reproduced the issue happening when enabled and rebooting.