Netduma Fraser

There is no export/import feature for the entire router but it has been suggested, as well as the LEDs on/off, they're on our roadmap so we plan to implement them in the future.

With share excess off yes that is how it would work

Some people say that they find it helps with lag compensation, it's worth a try if that's something you feel you're struggling with, otherwise no need

All 3 features can be used at once if you wish to, if you're wanting to throttle specifically and the TP rule is prioritizing then disable that. You don't really need to change BA just for gaming, it uses very little bandwidth and giving it more won't make it use it. As long as it has ~1Mbps then you're good!

Congestion Control is the easiest way to limit it, if you have Traffic Prioritization running then this will supersede Congestion Control/BA so might be what you're experiencing there

Yes that's right, keep us posted!

Whenever this happens it means we need to do a Ping Heatmap update as the game(s) have become outdated, we will do another tomorrow

Everyone has a different connection, what works/doesn't work won't necessarily apply to others, even in the same area using the same internet provider. There is no way to make changes for just one game type. Can you provide a screenshot of your QoS page please?

No, there is no networking reason on your side that it would work for one but not the other so it's likely due to the server they're using for private matches unfortunately

Disable QoS fully from the menu on Congestion Control, does that make any difference?

Are people from other countries in the private matches?

Hey, welcome to the forum! In a private game with opponents you can't control the server you connect to, if you're playing EU or US for example you could get put on a server quite far from you. You can still use the Geo-Filter to identify and ping the server in a private game, then compare that with the ping to the server you get when using normal matchmaking.

¿Podría alejar el mapa para comprobar si aparecen otros servidores? Si no, ¿puede proporcionar la identificación de ese servidor? Parece estar en la lista blanca por accidente, podemos solucionarlo.

I would assume that's because it's a beast of a router hardware wise and so for the R2 for example you may need to throttle more aggresively than the 700 to achieve the same performance

Sei davvero il benvenuto, è fantastico sentirlo, grazie per l'aggiornamento!

Brilliant to hear that, do keep us updated!

Untick it and then set the same manual DNS you did on the device

The next firmware isn't too far off, I haven't had a chance to test whether this particular issue is fixed but I'll pass it onto the team to check.

Best to let Netgear figure it out I think, you've done really well to prove that there is no set way to reproduce it, well done on getting it working as well!

It's weird given in reset 2 & 3 that you started in the same way and one caused it to break and the other didn't, which would lead me to believe there isn't necessarily one way to always reproduce it

Once the 500 is done we can then proceed with the 700 and hopefully shouldn't be too long after

That is very strange, the way you've listed the steps you did, is that in order of when you did it?

Hmm interesting, any settings changes or anything to do with the devices before the error happened?

Usually this error happens when a device is deleted from the Device Manager that was added to Traffic Prioritization or the Geo-Filter, does that sound like what may have happened?

Impostalo su Sempre, ripristina l'allocazione della larghezza di banda. Per quanto riguarda le percentuali di controllo della congestione, il 70% è un punto di partenza consigliato ma non sarà necessariamente perfetto per tutti, quindi suggerirei di sperimentare le percentuali per vedere cosa funziona meglio per te.