Netduma Fraser

Some good advice above, a few things, depending on what the firmware changes you may need to find values that work better on that version - the same values may not necessarily work on every firmware version. SmartBOOST priorities can impact the test so best to remove them, find what works then add them back after. Now as you live by yourself and you're not doing any downloading at the same time as gaming you actually may not need to fine tune QoS as much as you have a lot of speed.

Glad you managed to get it sorted. Do try the suggestions above and see if that helps at all.

You shouldn't be able to get games like that then, are you actually getting games that way? Okay that'll be why then, the basic steady ping adds up to 10ms ping so if yours is fluctuating 15-20 you should use expert. The maximum that can be set is 80ms - this is the target ping so the ping you want to have, not the buffer amount. So with your average 60-80ms it should then work better with it set to 80. If you do get above 80 like you mentioned sometimes happens then it won't be able to prevent those fluctuations/absorb it.

Did you make sure to restart the game and wait after making the change as mentioned in the first reply?

Just to be certain, do the above in terms of cabling, then reboot the giga, wait 2 minutes then reboot the R3, wait 4 minutes then check again please

Just engage in support with us, it's cheaper, plus as it's a DumaOS issue rather than a specific NG issue we'd be in a better position to help. Access using 192.168.1.1/adv_index.htm that should allow you into an unstylized version of the settings pages, this should allow you access long enough to upgrade to this firmware (if you're not on it already) https://forum.netduma.com/topic/51611-new-xr500-beta-firmware-33535/

I don't have all the technical details on it but from what I know have two addresses on the router for it, the main one and then a backup, if either of those aren't working for whatever reason, e.g. under heavy load, down for maintenance or they simply stop using that server etc then the feature wouldn't work.

To the router I mean, it occurs when you deleted the device from the Device Manager when that device was added specifically to the feature. Without the device being connected to the router the feature is looking for a device that isn't there and errors. So either a factory reset or connecting the device back to the router again under the same conditions will get rid of the error so with the same name, device type and connection method i.e. 2.4/5GHz or via ethernet.

All you need to do then is set it to Do NOT VPN these services and it will apply it to the entire device/the things connected behind it. You will see a bandwidth hit by doing this though.

https://forum.netduma.com/forum/144-netduma-r2-early-access/

If you're exclusively using 5GHz that is probably why, it can be easily impacted by obstructions, 2.4GHz is more stable generally

Usually 1-2 working days to most countries. I don't know if there will be a beta or not, I think we settled on potentially just releasing it publicly on the forum for people to try and then we'll push it to routers gradually so essentially there is a 'beta' period as any issues could then block a wide rollout. We will be looking into it, I believe it's related to IPv6 or SmartBOOST being enabled. I responded to you on this in another topic I believe. Are they definitely the same servers? They would say denied at the top when you ping it. Could you clarify? If it's within your radius it is allowed and you can add to the allow list.

Are you using purely Ping Assist then when that happens? What is your average ping without steady ping enabled and what does it fluctuate by? You may need to use expert for Steady Ping to set it higher to account for the fluctuations

Thank you, I'll get the team to take a look at it.

Good advice above. Also if you have a device in the DMZ you may not be allowed to port forward at the same time.

The site will work yes, it'll use a different server than what is provided for API purposes. Measurementlabs is cheaper than using ookla which is quite expensive

Have you tried the Early Access firmware to see if you get the same issue?

How are you connected to the router on this device, WiFi or ethernet? Do you notice the connection go down when this happens?

Use the simple mode instead of the custom/drawing method, does it work better then?

It is something we're looking into and should be fixed shortly. In the meantime if you have one device connected on 2.4 and the other on 5GHz it should work correctly

Good to hear! What app version are you on? You should be able to check on the phone settings or the app store for it

Yes you've done that correctly

I would just suggest prioritizing gaming as above, all other devices will be fine, you don't need to prioritize them. If you prioritized everything then effectively nothing would be prioritized if you see what I mean.

Thank you for the report, it YT, FB & GC what you were using at the time then when you noticed the incorrect reporting of usage? What is the model of the phone?

That doesn't make any sense really, I don't know why it would result in that behavior, I will pass it onto the team to try to reproduce. Thanks for the report!