Netduma Fraser

It's two days worth of logs but it is quite long so I may miss something, what port stuff did you do exactly? Were you unable to access immediately after that? Were you using the Geo-Filter/VPN/Traffic Controller prior to the issue? It seems to be cycling through features trying to clean them up/delete rules but seems to be stuck in that process so quite possible a setting or rule addition has become corrupted somehow sending it in a cycle. Factory reset from the hardware button, hold for 30 seconds, release, wait 4 minutes then access then upgrade to the Early Access version as soon as you can and monitor from there.

You had Ping Assist disabled before which you've now enabled, disable that and keep Geo-Latency disabled, restart then try again

We've responded via email, we can continue there

Okay if you could grab the logs immediately after it next happens we can investigate further

If that is the case then changing the provider may help which it sounds like you might be doing, otherwise nothing unfortunately unless IP databases update

There are only two firmware versions I believe and the latest one just has a security change so shouldn't differ much from the other version

What is the model of the modem/router the R3 is connected to and how have you set that to ensure all traffic flows to the R3? E.g R3 in its DMZ, modem/bridge mode Are ALL devices connected to the R3? Have you entered those speeds into the router? How have you setup Congestion Control? How have you setup SmartBOOST? Where are you checking the download speeds? What speed are you getting on a wired speedtest.net test? What platform are you playing on and how is it connected, via ethernet or WiFi?

That's quite a common PlayStation issue, replacing the ethernet cables you're using is a good idea and most likely to resolve it

I've given you Early Access: https://forum.netduma.com/forum/151-netduma-r3-early-access/ Please upgrade to that version and see if you continue to have these issues

As above turn off Geo-Latency, reboot then try it again. If it can't ping or if the server ping method shows as traced then it's unlikely to be able to apply Steady Ping.

That's really great to hear! Thanks for the update and I do apologise for how long it's taken, it's a testament to your persistence that its on the router now. I do want to thank you for being so patient and polite as well, it would have been very easy to show frustration over this amount of time and you didn't, I personally really appreciate that.

They're pinging different servers in different locations so the ping will be different. Where are you measuring packet loss? What is the model of the modem/router the R3 is connected to and how have you set that to ensure all traffic flows to the R3? E.g R3 in its DMZ, modem/bridge mode

Added - it has been removed temporarily

It won't be HybridVPN, what's the time frame roughly when it happened? Then I can match it up to the correct entries in the log

Go here: http://192.168.77.1/dumaweb#!/support and you should be able to upload the firmware there to upgrade

What web browser/device are you using to access? Can you access the pages using the DumaOS app?

Added - it has been removed temporarily

When roughly did it occur so I can match it in the logs? What settings have you changed between now and then?

If you're not the party leader then you don't need the Geo-Filter so you can just disable it

The side menu should still be clickable and the pages that aren't having the issues should still load. Logs are in Settings > Troubleshooting. First upgrade to the Early Access version here: https://forum.netduma.com/forum/151-netduma-r3-early-access/ If it still happens after that then grab the logs please

If it can't ping the server then it won't be able to apply Steady Ping. Game servers don't respond to ping requests so this can happen. I also see you didn't follow the instructions fully as the PC has still been added to the Geo-Filter by selecting CoD but it should auto add as a console after changing the PC device type in the Device Manager. If you didn't understand that part just let us know.

What firmware version is this on specifically? Ideally if you could grab the logs when it happens we can investigate further

Could you try to connect to one of the games you have trouble with and then grab the logs from settings please? Hopefully it will have some insights there

There was nothing at that time causing it, is this on PlayStation by any chance that it's happening on?

If you could provide the logs when this issue happens we can try to determine the cause