Netduma Liam

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.

Good feedback, thank you for that.

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?

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?

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.

Thanks for posting this. It would be good if you could create a new topic with this information so we can look into this further with you. In the new topic, could you please include the below: When the connection drops, are you able to access the DumaOS interface from a device connected via wired? Do you need to reboot the R2 to get the connection back, or will it eventually restore itself? Do you recall if the disconnections occurred after a particular device started generating some traffic? Are you using any wireless extenders, powerline adapter or access points for example?

@ahmedkI've responded to your new topic, let's continue there.

Could you please try hitting 'Resync cloud' now in Ping Heatmap and see if that's better?

A few users have reported this with the XR500, we'll get the team to look into it and see why it's not updating.

OK, we're currently working on reproducing the issue so if you could set a static address on the device we'll keep working to troubleshoot the issue ourselves.

To confirm, are you noticing slow matchmaking/any other side effects of the moderate NAT type in games? I'm currently looking into the issue of remote logging with a developer, I do believe this is going to be really helpful in working out the cause of the problem so as long as you're happy to still try that I'll update you once we've come up with a solution.

The IP the R2 is getting from the modem may have changed, double check that and put the new one in the ISP DMZ if it has. That should resolve any NAT issues.

Yeah we're definitely able to access the R2 because we use your WAN IP to do so, we're just not then getting any logging back from that IP. Unfortunately those logs are related to any issues, we've noticed their frequency on the R2 but investigated and deduced that they are not caused by any particular issues as such. I can understand your decision not to use the R2 for now, however you could also perhaps revert back to the old firmware and factory reset? It wouldn't necessarily help us solve the issue but at least it would improve your experience?

Apologies for the delay, I'm back, thank you! I'm not sure what's going on here, we're not getting any logging from your R2. I'm going to get some developer input on this and see if we can work out why. After we enable logging etc, are you then changing/reverting anything in your setup that could potentially cause your WAN IP to change? Are you for example removing the R2 from the modem DMZ, or re-enabling any port forwarding rules?

I would suggest setting it to Auto-enable. That way, it will only limit bandwidth to background services if priority traffic is detected.