Netduma Fraser

Ping Heatmap doesn't influence the servers you connect to though, just allows you to view where they are

It won't be this year but I will make another request for the new year

Added

I need more information than that to determine a potential cause such as What is the model of the modem/router the R2 is connected to and how have you set that to ensure all traffic flows to the R2? E.g R2 in its DMZ, modem/bridge mode Are ALL devices connected to the R2? What are the speeds you pay for/receive? Have you entered those speeds into the router? How have you setup Congestion Control? How have you setup SmartBOOST? What game are you playing? What platform are you playing on and how is it connected, via ethernet or WiFi? How have you setup the Geo-Filter? What times of the day are you playing where you notice this?

Yes the one pinned to the top of the sub forum

I believe they're just making it so that connecting via a VPN and having a high ping is blocked so it'll force you onto different servers. Also the Spanish server is one of the hardest to force, it doesn't always seem to be available so it may have nothing to do with the VPN at all

In terms of prioritizing traffic, I can't speak to any other router and how they do things, just what we do. We use deep packet inspection to determine what you're playing and when, it's not all an automated process, we do need to add games. There is also more that will be coming surrounding this that I can't speak on at the moment. You can suggest games and provide data for it that will help but I can't give you an ETA on when/if it might be added. Based on what your circumstances are, I don't think you really need much in the way of features by the sounds of it, even using the XR500 you were only using 1 small feature and that's it essentially. At the end of the day, you don't have many devices fighting for bandwidth, sounds like you're generally playing games together so you're not going to be using much bandwidth then and when you do need more bandwidth for a download you won't be gaming and so any additional ping introduced is kind of irrelevant. Feeling 'fluidity' is kind of a subjective thing, there are no stats that are available to support that feeling all the time and thus it's hard to say, enable this, disable that and it'll be fluid 100% of the time. The best thing to do is to achieve the best ping you can with the features available, see how it feels, if it doesn't feel right you can adjust. It's more trial and error rather than one size fits all. Hardware on routers is really a marketing move, as long as the software is optimized then it doesn't matter - we've put DumaOS 4 on our previous slower hardware R2 router after using the R3 to develop the software in the first place. The hardware on any of the routers is more than sufficient, your usage/devices are not particularly taxing for the routers to deal with. As you want to achieve feel more than anything just play around with all the features, use Congestion Control, try SmartBOOST and different ways to prioritize your device, even reserve bandwidth for those devices, try port forwarding, the Geo-Filter etc. It seems to me that actually you're starting with a bit of a luxury - you don't actually seem to have many lag issues. In which case you can quite leisurely experiment with everything to find the best for you. A feature will arrive in hopefully the new year that would take the only real negative out of using Congestion Control so you'll definitely have no real reason not to use it when that's available. Anyway, I hope that's an alright answer for you, some people don't like the experiment answer but there are so many variables when it comes to networking that it's extremely difficult to provide a one size fits all setting - hence why all our features are pretty open and allow you to tweak how you want to set it up.

Thanks for the update so far, do keep us posted!

The test for jitter is just to the server that Ping Optimizer uses and that could change for a variety of reasons, jitter to that doesn't necessarily mean you'll have jitter to the game server. Utilizing Congestion Control properly though should keep the wide variance to a minimal

It does need to be lowered below 100%, especially with your lower speeds, it's a necessity really. I'd suggest testing with downloads while following: https://support.netduma.com/frequently-asked-questions/legacyfaqs/test-your-ping/ start with a high value e.g. 95%, test, decrease 10%, test, decrease 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. Important to note that Download/Upload on CC don't have to be the same value & you may have a better experience with differing values. This is a real world test as you'll be simulating traffic that you may normally be doing.

How do you have Congestion Control set exactly?

What percentage for Congestion Control? How have you set Traffic Prioritization? How do you have the Geo-Filter set up?

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?