Netduma Fraser

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

Good to hear that, thanks for the update!

This is an unusual issue, I think it would be best to do a factory reset, complete the setup wizard and don't change anything and see if you get the same issue

Game servers used are completely different to the servers the ping test uses, ping on one doesn't mean you'll get that ping on the other. The Geo-Filter doesn't impact the ping test either, it just determines the servers you connect to. We use a service for the test, I don't know the specific locations they have available - you can ignore the test, a bad result on the test doesn't mean you'll have a bad experience to the game. It's like checking how long it will take to get to a destination on a bus when you're going to drive a car instead, it can give a indication but its not 100% accurate of your experience. Your speedtest ping is 5ms which is great so you don't need to worry about the ping test on the router. Use the Geo-Filter and get the closest possible servers to you with the lowest ping possible.

The internet provider or type of internet you have wouldn't impact the functioning of the Geo-Filter, it sees the same connections and filters the same way regardless. What could potentially be happening is the new provider you're using has IPs that were bought from other locations and the locations haven't properly updated in IP databases, leading the game to think that you're actually somewhere you're not. In which case it's trying really hard to connect you to a server it thinks should be good for you but actually isn't. It's quite rare to see that but it is possible.

I've given you Early Access, see if that version works better https://forum.netduma.com/forum/151-netduma-r3-early-access/

In the Installed Rapps panel on that page click and change the retries to 5, reboot from the interface, close the interface, wait 4 minutes before accessing and see if it's any better then. You can't disable any Rapps and you would have to go back to pre-DumaOS which I wouldn't recommend. Try what I said, if that doesn't help, re-upgrade to the same version and see if it works better.

I think it'll be this week now, at least that's what I'll push for