Netduma Fraser

Sent

Firmware will come this week, will be tested first/provided as a link to those that ask for it before it's pushed to routers

It could be local congestion, in which case if you fine tune your Congestion Control/SmartBOOST settings it could eliminate it. Otherwise if it is the issue we know about we'll get it sorted asap

You can still have strict mode on, in fact it's best if you want Ping Assist to be used exclusively. What range are you using?

It'll stay on .23

Sent

Interesting, I'll have the team look into it, thanks for the report!

Keep us posted!

It's been requested to allow going below 50% so we'll likely bring that back. For Bufferbloat you'll need to set Congestion Control to Always and then disable Speed Test Bypass and you'll get better results.

I know for Overwatch 2 at least it's one of the games that can't be filtered normally which is why it works with Geo-Latency, we'll have to test Diablo 4

Could you clarify? I'm not sure I understand what you mean

If you minimize the get dumaos entry does nothing else appear?

The R2 will be getting DumaOS 4 so not to worry!

That could just be the server, it's normal for the ping to fluctuate a little, that's precisely why we made Steady Ping so you don't get affected by it

If you do the following does it work with custom? Disable GeoLatency Disable PingAssist (set it to 0,0) Enable Strict Mode Disable Fast Search Then restart game or wait 10 minutes (in the lobby in the game). If that doesn't work, reboot PC/Console and it should work then. With Steady Ping on the minimum you can set it to is 10ms. Is that in game or Geo-Filter ping?

Sent

From the R1 it's a massive step up!

Do you have Geo-Latency on? As with it you shouldn't have any issues with chat at all. Otherwise you will likely need to add your friends to your allow list and then it should work properly

There isn't anything there other than the Fraggle attack which is a bit strange that I can see that would have caused it but just in case. In LAN Settings, set the DHCP range to start at .50, then assign reserved IP addresses to devices between .2 & .49 so they're out of the DHCP range, apply, reboot from the interface, wait 4 minutes and see if that stops the disconnects.

Try a different server closer, does that work?

Not specifically no, Alex will be catching up with everything currently so may be a few days at least

There is likely something blocked outside the radius when it happens, make sure to zoom out, if you do see something add it to your allow list then check to see if you get the same issue - you may need to try it a few times.

Great thanks, I'll pass that onto the team to have a look. Make sure to check whether you get it connected to the modem also.

It could be that problem but actually it's most likely steady ping, if you disable that is it better? Yes it is something the team are looking into currently and will be fixing.

Unplug the router from power for 24 hours, plug in, then wait 4 minutes before accessing and see if you can get internet. It may seem excessive but we have seen routers come back to life doing this. There is a launch discount for the R3 yes, I think it's about 20% off