Netduma Fraser

Added https://forum.netduma.com/forum/153-xr1000-beta-forum/

Those issues would have been resolved by now for the most part by updates, don't forget it is a support forum, you're only going to see issues here, not the people who aren't having issues. Did that resolve the issue for you? Without accessing to get the logs from DumaOS not really. If you are behind on an update that fixes it then that would sort it.

We'll need some more information, do you get the same high ping directly connected to your ISP modem/router for example? Are you using the Geo-Filter?

No you're not able to do that as above

Good to hear, thanks for the update!

It's unlikely to be a widespread issue otherwise lots of people would have mentioned it by now, do this process and check again: Quit the application/game/client completely - that means from the System Tray as well, so the Xbox App shouldn't be there Remove device from the Geo-Filter Keep it set as the PlayStation 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 See if it works better then. If not I've given you Early Access you can upgrade to, to see if it works better on that version https://forum.netduma.com/forum/151-netduma-r3-early-access/

I can't see any of the smaller numbers in that second picture at all

I'm not sure I understand, what do you mean the parameters are always low, can you clarify?

Instability in what way?

Disable the Internet Optimiser, reboot and then enable it, reboot then check if you can get access please. If there is an update available that should also get you on the latest.

Why do you need to keep rebooting/resetting, because you get a bad bufferbloat value? It's just about fine tuning your Congestion Control percentage. I don't think you should rely on the bufferbloat test, it's not full proof. Follow this guide https://support.netduma.com/frequently-asked-questions/legacyfaqs/test-your-ping/ while downloading & start with 95% for Congestion Control (set to Always), check results, decrease by 10%, check, decrease by 10% etc, until you get to a value that is pretty good & then try 5% either side of that value to see if it can be improved. Download & Upload on Congestion Control don't have to be the same value & you may have a better experience with differing values. This is more of a real world test as you make the connection as bad as possible then find the settings that make it the best as possible in that scenario.

Are you seeing anything blocked on the map when this happens? With the Geo-Filter disabled is it working?

I've given you Early Access so you can try that version to see if it works better but with the Geo-Filter enabled do you notice a blocked icon on the map? (Zoom out fully) If so, add that to your allow list and try again to connect, does it work then? https://forum.netduma.com/forum/151-netduma-r3-early-access/

Added

Added https://forum.netduma.com/forum/144-netduma-r2-early-access/

While connected to the router via a wired/wireless Windows PC, open command prompt, type ipconfig press enter and then post a screenshot of the results here please.

Can you access using either http://192.168.77.1 or http://dumaos at all? Can you access via ethernet or via a different device using WiFi? Can you access using the DumaOS mobile app?

Good to hear, thanks for the update! No there isn't unfortunately

Added https://forum.netduma.com/forum/144-netduma-r2-early-access/

I added you when I replied previously, the previous links would work now https://forum.netduma.com/forum/151-netduma-r3-early-access/

I think fine tuning Congestion Control in the way I mentioned would get you a better result, try that out and if not we can try to dive deeper into it

That's fair enough but I think it is likely to perform better, you can always downgrade back to the version you are on

Added https://forum.netduma.com/forum/144-netduma-r2-early-access/

Yes absolutely. It could potentially but if you're already prioritizing the gaming device then it would already be covered. Game servers don't always respond to pings and like game servers not every hop along the route to the server you're testing will respond to pings either, that's what you're seeing there, it isn't an issue or anything that needs to be resolved, you can just ignore that entry.

Added