Netduma Fraser

The answer is in what you've said, you're suffering from peak time congestion with your ISP, it's nothing to do with the R3 and it can't counteract it. You would have the same issue using another router as well. The only real "solution" would be to switch to a less common provider that would be less oversubscribed in your area.

There are only 2 ways to resolve this error: Factory Reset Re-connect the device that you deleted from the Device Manager back to the router via the same connection method (ethernet, 2.4GHz or 5GHz), give it the same device type and name. Then the error will disappear.

Ignore the speed test on the router and just go off the third party speed tests as they will be correct, you're getting pretty close to what you'd expect through the router. Make sure you've entered your full speeds and check whether Congestion Control is applying in Ping Optimizer > Advanced.

Disable Geo-Latency & Ping Assist, reboot the PC and try again

It doesn't appear to be related to your last issue, there were a lot of errors in that log and not so much in this one. Okay no worries, it may be the log doesn't have much in the way of helpful information currently. Do the factory reset & upgrade and we can go from there, will also help to be on the latest

Do this: Quit the application/game/client completely Remove device from the Geo-Filter Give PC PlayStation Device Type in the Device Manager Resync from the Geo-Filter Map menu Re-add the device to the Geo-Filter Set up the Geo-Filter how you like Wait 2 minutes Boot up application/game/client

It's pinging servers for me, resync the cloud on heatmap and try again please

Congestion Control can be found in Ping Optimizer > Advanced and is one of the main features used to combat bufferbloat/lag - has this been setup? (If you have run Ping Optimizer it would have changed the settings here) If so, what values is it using for download/upload? How have you setup SmartBOOST exactly? Re-enable the Geo-Filter, ensure Geo-Latency and Ping Assist are disabled, then start the game and see if it works.

Reboot the Sky Hub, wait 2 minutes, reboot the R3, wait 4 minutes then check again

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?