Netduma Liam

Open a different browser, such as Chrome or Firefox, then go to http://192.168.1.1/. It should then load better for you. If it's a browser you've used to access the interface before, I'd suggest just clearing the cache in that browser as well.

We're not sure just yet, we're currently testing some new R2 firmware so it's in the works, but we're not close enough to give an ETA just yet.

Hey, I've responded to the topic you've created. Let's continue there.

Which features specifically are you not seeing? Let us know and we'll be able to say whether that's expected or not.

We don't have an ETA as yet, we're making some substantial changes to how Geo-filter works. Our testing has proved very promising, but it's still ultimately in development so I can't yet provide an ETA.

We've made a change via a cloud update, could you try re-syncing again and see if it updates?

Since deactivating it have you tried re-syncing cloud again? If not you'll need to do that to get the latest information.

Looks like it managed to resync successfully that time. As a side note - are you using Hybrid VPN? There's an error in there relating to it and I'm curious whether that might be causing the problem. If Ping Heatmap still hasn't resynced properly, please disable the VPN and try again, see if it works after that.

You don't need the PS5 in the XR DMZ if you've also got the XR in the modem's DMZ, so you can remove the PS5 from the DMZ. Could you please try going to Geo-filter and resync cloud from the three-line menu there. Please then download the logs again and send them over.

OK, quindi non riesce a risincronizzarsi, ma non c'è motivo per spiegarne il motivo. Abbiamo appena testato internamente e funziona. Potresti per favore scollegare l'XR dall'alimentazione per alcuni minuti, quindi ricollegarlo e vedere se può risincronizzarsi dopo?

Could you please do the resync again, then go to System Information -> Click the three-line menu under 'Logs' and download the log file. If you could please send that over to us and mention the approximate time you resynced, that'd help us troubleshoot this more.

Set Ping Assist to the maximum ping you'd like to play in-game. I'd suggest about 30-40, that might speed things up for you. We might be able to get this added to Ping Heatmap so you can always check on the servers, I'll speak with the team and see if we can get that added.

Is this for Warzone again? I can see that a few of them have stopped responding so I'll speak to the team and get them to push an update as soon as they can.

You can't add it to Bandwidth Allocation just yet, but we're currently working on a solution for that. In terms of Traffic Prio you can add it as a service. If it's not working great we may need to update it's DPI classification so let us know if that's the case and we can do that.

@CJArthur A modem replicating your traffic controller setup is currently in our endurance testing suite, I'll catch up with the team now and see if we were able to replicate the issue over the weekend.

Good feedback, thank you for that.

Thanks, there's some good info in there. I'll pass this over to a developer to investigate and we'll let you know.

Immediately after the disconnect, can you download the log file from the three-line menu in the logs panel and send them over to us?

In general, the results look pretty good as far as I can tell. Were these tests run while saturating the connection as Fraser mentioned? I'll link the guide below again for convenience. http://support.netduma.com/en/support/solutions/articles/16000074717-how-to-test-your-internet-ping

Thanks for that, could you please disable the DumaOS classified games rule, then add a new one. In the new rule, select your games console as the device and 'Games Console' as the service when prompted. After that, set Congestion Control low, down to about 40% maybe. Then set it to always. After doing this, click 'Reset allocation' on Bandwidth allocation just to be safe. Then, play some games and see how it feels. A couple of follow up questions: Do you know if you require PPPoE, VLAN or DHCP identifiers to get a connection to the internet? Are you using Geo-filter? If so could you share your configuration with us?

La solución a corto plazo es configurar VLAN/PPPoE en el enrutador ISP y luego conectar el XR a través de DHCP. A continuación, puede controlar la carga. No tenemos un ETA en el nuevo firmware, pero estamos trabajando activamente en ello con NETGEAR. Publicamos todas las actualizaciones que tenemos aquí: http://support.netduma.com/support/solutions/articles/16000132677-dumaos-firmware-progress Intente también agregar la regla personalizada a Traffic Prio como mencioné.

Just to clarify, have you reset since the upgrade to the latest firmware version? If not, could you please do so. Can you also answer a few questions for us: Are ALL devices on the network connected via the R2? Have you got any custom rules configured in Traffic Prioritisation? If so could you please share them? If not, is the DumaOS classified games rule detecting traffic while you're playing? This is indicated by a red light on the rule, and the packet counters increasing. What's the make and model of your modem?

Tenemos algunas correcciones de QoS en el próximo firmware, con suerte deberían resolver este problema. Mientras tanto, hacer que el enrutador ISP maneje la VLAN, luego DMZing el XR solucionará el problema por usted. También sugeriría crear reglas personalizadas en Traffic Prio para el dispositivo en el que está jugando. Para experimentar inicialmente, simplemente seleccione "Consola de juegos" como servicio y vea cómo se siente.

No tenemos nada que anunciar todavía, mantenemos este artículo actualizado con toda la información más reciente sobre firmwares: http://support.netduma.com/support/solutions/articles/16000132677-dumaos-firmware-progress

Thanks for posting all this information! One thing to note: Have you factory reset the R2 since upgrading? If not, please do so when possible as the latest firmware is quite a big upgrade so it's best to start from a clean slate and clear out any low-level code that could be there from a previous version.