Netduma Fraser

Yes exactly!

Simply changing the range won't resolve the issue, see how it goes without that switch but if it continues set the range to start at .50 and then do the reserved IPs.

You set DHCP range to start at .50? In which case assign reserved IP addresses to devices between .2 & .49 so they're out of the DHCP range, apply, reboot from the interface, wait 2 minutes and see if that stops the disconnects.

Added!

What settings have you done to ensure an Open NAT other than the one I mentioned to change, DMZ, port forwarding, port triggering or UPnP off?

We may do another beta before an official release, it depends how long it takes for us to fix any issues that have been brought up really and how stable we feel the firmware is

Siempre que el anfitrión del lobby esté usando el filtro geográfico para forzar un servidor, obtendrá la mejor experiencia

No worries, got to do what feels the best for you, we'll be doing a big DPI update soon which may help.

Force some servers further away from you with a slightly higher ping, they may be more stable and play better

El juego decide, no puedes influir en eso.

As it is new firmware and there are a few changes I would suggest fine tuning QoS for this version as the settings needed may not be the same as the previous version. For example, utilizing the Ping Under Load reading on Connection Benchmark, It's best to start with a high value for Congestion Control, 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.

Added

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

Estás haciendo una conexión directa para el chat en lugar de un servidor, no afecta tu capacidad para buscar juegos.

I can see you signed up about an hour ago, I've added you

You can only disable DPI after disabling QoS first

That's right, yes it's the latest currently, we'll always pin the latest firmware to the top of the beta forum

Plug the modem in, wait for that to boot up properly so wait a few minutes, then turn on the XR wait a few minutes then connect but generally you don't need to do that as the factory reset/setup wizard would prompt it to get internet again. You can keep the Xbox connected and turn on when ready. I think that's probably a placebo effect as there is no networking reason that would be the case.

Added, let us know how you get on with that! https://forum.netduma.com/forum/145-nighthawk-pro-gaming-beta/

Welcome to the forum! Generally when people mention having this problem in game, throttling their speeds severely using Congestion Control and forcing servers slightly further away with the Geo-Filter seems to help them. I could also give you access to the beta if you would like to try it?

Try connecting the devices via the same method so 2.4 & 2.4GHz or 5 & 5 or ethernet & ethernet and see if that woeks please

Deberá ponerse en contacto con su proveedor de VPN, ellos serían los más adecuados para realizar cambios como ese.

Welcome to the forum! Sorry to hear you're having this issue, could you please deactivate optimiser then reboot from the interface, wait a few minutes so it all boots up properly, then re-enable optimiser, then wait 5 minutes this should ensure it loads correctly. Then access please and see if that works.

Did you factory reset after your update? So it makes no difference if the console is turned off fully you still need to restart it? Good advice above to set a static IP for the console on the R2.

Is that the only entry in the log or the only entry at the time when you tried remote play?