Netduma Fraser

I'm not sure what guide you're following but the point of TFTP is to install the new firmware before it has booted up, once the light turns white it has booted and therefore will not install the firmware correctly. Use this guide: https://kb.netgear.com/000059634/How-do-I-upload-firmware-to-my-NETGEAR-router-using-TFTP-from-the-Microsoft-Windows-Command-Prompt?article=000059634 and try again

If the router is dead it wouldn't be able to give you an IP properly, I believe you're supposed to issue the TFTP command before that happens - did you give your PC a static IP as detailed in the original TFTP guide you followed? If not that is why it is not able to send and work properly.

The only other thing I could advise would be to unplug the router from power for 24 hours, that can sometimes bring it back to life, if that doesn't work then it sounds like it may be bricked then unfortunately, you can try contacting Netgear support to see if they have any other troubleshooting methods.

Did you confirm that the router had upgraded successfully before rebooting the router? Don't do a 30/30/30 reset, it's meant for very old routers and can damage newer routers. Unplug the router from power for 10 minutes, plug in, wait 2 minutes, attempt access, if it doesn't work hold the reset button for 30 seconds, release, wait 2 minutes then try access again. Otherwise you can try using nmrpflash, it is not an official method and so not something we can help with directly, therefore make sure to read the instructions fully https://github.com/jclehner/nmrpflash

New firmware isn't available yet, we're working on it, once available I'm sure it will resolve the issue. You can reboot like that but ideally you would do it from the interface by clicking the 3 dots icon top right of the interface. You can enter random numbers between .2 & .49, when you've set them all you need to reboot so the devices can then use the IPs you've set.

It would be better to continue topics you've made previously to let us know if our last suggestions have worked or not as we're likely to recommend things we may have already suggested before when you create a new topic. New firmware will resolve the issues we're pretty sure, working on the specific cause currently but in the meantime, 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 2 minutes and see if that stops the disconnects.

It's worth noting that bufferbloat occurs when your network is saturated, with your speeds and with QoS enabled this wouldn't happen, especially if you're just gaming, in which case you would not experience spikes like that in game. Traffic Prioritization can also interfere with that test. Best bet is to use PingPlotter, according to this guide, while downloading (specifically this, HD videos will not saturate your connection due to your speeds) http://support.netduma.com/support/solutions/articles/16000074717-how-to-test-your-internet-ping and experiment with the percentages to find what keeps the ping as low/stable as possible on the bottom graph.

We don't generally give out any ETAs but you can check this page for firmware progress: http://support.netduma.com/en/support/solutions/articles/16000132677-dumaos-firmware-progress

Which one specifically? Warzone?

Correcto, use el enrutador ISP y siga los pasos que mencioné anteriormente y será mejor, luego puede utilizar QoS correctamente para mejorar su experiencia. Esa prueba no importa demasiado, ya que bufferbloat solo ocurre cuando todas sus velocidades están siendo utilizadas, a sus velocidades es poco probable que suceda.

Para aclarar, ¿está utilizando el enrutador ONT o ISP?

Haga que el enrutador maneje la VLAN, coloque el XR en su DMZ. Deshabilite WiFi en ese enrutador, luego todos los dispositivos se conectarán al XR, todo el tráfico irá directamente al XR y luego podrá usar QoS. Si haces todo eso no habrá nada negativo

¿Ha vuelto a ONT > XR con la VLAN de manejo de XR?

Personally I would normally recommend Classified Games because then it is only prioritizing what needs to be prioritized. Using the other methods will sometimes allow unnecessary things to be prioritized, saying that I know a lot of people like specifying ports so really it's just whatever works for you and your connection!

I can reproduce this so I'll pass it onto the team to fix, if you're playing on that server the Geo-Filter should give you your live ping to it

I suspect you've been doing a lot of streaming/downloading or some other high bandwidth application which would account for the received packets being a lot higher than transmitted

When you click on the server it should open a panel underneath the main panel showing the IP and ping, you may need to scroll down, does this appear?

¿Incluso reducir la asignación de ancho de banda y compartir el exceso deshabilitado? Share Excess debe estar deshabilitado, de lo contrario no funcionará.

Puede usar la asignación de ancho de banda para sortear eso, otorgar un pequeño porcentaje al dispositivo y luego deshabilitar Share Excess para cargar y se limitará a esa velocidad

Haga que sus porcentajes de control de congestión sean muy bajos: la gente lo recomienda

Con sus velocidades, es poco probable que experimente congestión local, en cuyo caso experimentar con porcentajes puede no hacer mucha diferencia, pero podría intentar acelerar para reducir la velocidad. Algunos creen que este contraataque retrasa la compensación.

Con sus velocidades, es poco probable que experimente congestión local, en cuyo caso experimentar con porcentajes puede no hacer mucha diferencia, pero podría intentar acelerar para reducir la velocidad. Algunos creen que este contraataque retrasa la compensación. Podemos continuar en su tema: https://forum.netduma.com/topic/39188-qos-priorización-de-paquetes-call-of-duty-en-consola/

Podemos continuar con su tema si tiene más problemas. Sin embargo, una actualización no solo reducirá su ping a los servidores

La actualización fue una actualización de seguridad y mantenimiento de Netgear, no hay cambios por nuestra parte. Si sigue lo anterior, podemos investigar más sus problemas.

On PingPlotter the main thing to focus on is the bottom graph and you're not receiving packet loss there and your connection is quite stable!