Netduma Fraser

You should be able to access it via 192.168.1.1 - changing the name doesn't make it inaccessible, does the IP work to access it? Whatever the name you changed it to you should be able to access it with that

An update has been pushed that will fix it, 25% of people will have it now and it will auto rollout slowly so that by the end of the week 100% will have the cloud update. This is to prevent any major issues occurring.

It's automatic now so every device gets what it needs. Gaming uses barely any bandwidth, giving it 100% doesn't do anything or make it use more

Yes please, grab the logs prior to reboot then you can reboot

Try this: Quit the application/game/client completely Remove device from the Geo-Filter Give PC PlayStation Device Type in the Device Manager (if on PC) 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 Then see if it works better. You won't be able to stabilize/ping every server unfortunately but we're working on a new ping method which may make this more reliable in future.

Can you check the CPU/memory usage at the start and provide a screenshot, then continue to monitor it as it drops and get successive screenshots please so we can see if there is a correlation.

It may just simply be that it's a new game and at this time of year ISPs and game servers are under load anyway. 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. How have you setup SmartBOOST/Congestion Control?

Added

There isn't a logout function on DumaOS 4 currently

We haven't specifically tested the game so while it can work, it's not optimized for it. It's likely in both cases that it is trying to connect to a server outside your radius, in terms of the chat, if you disable it once you've forced a server then it should allow you to chat, then you can re-enable it once it's working and you should then be able to continue filtering from then on and the chat should hopefully continue working. Probably the best solution though is if you see a blocked icon on the map (zoom out) when you're playing, add it to your allow list and it should work then - you may need to do it a few times, there is likely multiple servers for it.

You already have access: https://forum.netduma.com/forum/151-netduma-r3-early-access/

Yeah it's a London cluster that has been whitelisted by mistake, it's being rectified currently

You have to be signed in to view it, are you doing that?

You ask them for the OpenVPN configuration files or specifically ask for the OpenVPN config files for whatever server it is you want to connect to. You should have your username/password credentials already when you sign up.

It's the relay servers they're using causing it, we will look into it but may be no proper fix. Geo-Latency on the DumaOS 4 beta is the only thing that may make it happen less.

Added

As long as they provide you with the OpenVPN configuration files to connect to them then yes they should work

What do you mean by wrong server? What do you see on the map when you're in a match?

Is it that you're not getting a game or you're not seeing one within your radius?

Added

Go to the main forum and look in the testing section at the top and you should see if there, go in that way

Don't use the polygons, try with the normal radius instead

Added

You cannot set a ping on the Geo-Filter and expect to get a game at that ping value unless you know and have connected to games before where you've had that ping or lower - have you had that happen before? Also keep in mind due to the time of year servers will be under more strain and so the ping can rise. Can you provide a screenshot of how you have the Geo-Filter page please?

First thing to check if it's never happened before and the only thing that has changed is the DNS then disable nextdns and then check. If it still doesn't work then disable the Geo-Filter, does it work then?