Netduma Fraser

Thanks, that's great to hear! If it's not broken don't fix it is my advice, there isn't anything super significant worth upgrading for unless you're having issues. The R3 is the first time we've our own automatic rollout and prior to that the NG routers had them but it was controlled by NG. Unless you are certain about stability, doing an automatic rollout could result in an irreversible problem or instead of a few hundred people who might be experiencing an issue (which is still a pain to manage but do-able) you have thousands at once. The firmware certainly isn't unstable or causing major issues but we like to er on the side of caution where possible. Also *generally* people in Early Access are more willing to making themselves liable to experiencing bugs for the benefit of receiving firmware earlier and so have more patience. Someone not interested in the community or anything like that just wants the most stable firmware available when their router indicates there is one and will be less patient for Early Access type firmware. I've given you Early Access in case you'd like to follow along there and try it at some point. They would have only had 5 hours prior to you asking again to work on it, they're not that fast unfortunately, it will take a little bit of time.

There are only 2 ways to resolve this error: Factory Reset Re-connect the device that you deleted from the Device Manager back to the router via the same connection method (ethernet, 2.4GHz or 5GHz), give it the same device type and name. Then the error will disappear.

What is the model of the modem/router the R3 is connected to and how have you set that to ensure all traffic flows to the R3? E.g. R3 in its DMZ, modem/bridge mode

How do you have Congestion Control setup?

You can't integrate the software into the router if that's what you mean. They have a program on PC so you can use that on a PC connected to the R2.

Grab the logs please and we can take a look

Is it always showing 1ms now or has it gone back to normal and if it is normal is it now stabilizing?

So bufferbloat is caused by the saturation of your network, with Congestion Control lowered that cannot happen any more, thus bufferbloat is eliminated. So as long as you've found the best results using PingPlotter I would honestly not worry about the waveform test as it's unlikely your ping will ever spike that high now. Also as long as you're not getting it that high when gaming you're all good, you'd just essentially be chasing an arbitrary number.

They're both using different servers so you'll get different results and while they're both providing an approximation, the best thing to do in my opinion would be testing with downloads while following: https://bit.ly/bufferbloat-test start with a high value e.g 95%, test, decrease 10%, test, decrease 10% etc, until you get to a value that is pretty good, then try 5% either side of that value to see if it can be improved. Important to note that Download/Upload on CC don't have to be the same value & you may have a better experience with differing values. This is more of a real world test as you're actually doing traffic you would normally do.

Unfortunately not, I think there is some progress but not to the point of having a firmware to release right now

You need to set Ping Assist to 0 and then it should work better

Have you accessed the interface and completed the Setup Wizard? You'll need to do that before you're able to get internet

Right okay understood thank you, I'll let the team know

Try reverting those changes then and see if it works with the steam one

I'm saying I saw the release date for the game was on the 27th September, that's why I was saying it hadn't been released yet. Do they just update the base game or release a new one?

I was seeing Sep 27th, do they just update the game or release a new one?

There was a beta for BO6 that we were able to test, eFootball 25 hasn't been released yet, once it has been we can test it.

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

It was highly likely to be spam, so it was hidden, it's also not a good idea to change those types of settings unless you know what they're doing and how to reverse them. You're relying on the results of this test but are you actually experiencing spikes of 50ms+ when playing when other devices are being used?

If it was a true network issue, you could try for 20 minutes or 20 hours and the result would be the same, unless that issue/conflict is resolved it wouldn't allow you in, unless perhaps it's not triggering a port opening but you have a port forward so wouldn't be that - did you do just that port rule we mentioned?

No longer effective in what way?

There really isn't too much that could be blocking you in this scenario, have you: Got Adblocker enabled? Done port forwarding rules? Done internet rules?

What exactly are you seeing when you try to access? Can you access using the app?

There isn't any harm in doing TCP/UDP so change it to that just to make sure

No there isn't a way to do that unfortunately, I think the only thing you could do would be to forget the R3 network on those devices and have them only have the details to connect to the XR.