Netduma Fraser

Great to hear that, thanks for the update!

If your Internet Service Provider (ISP) router gives you WiFi then you need to put the R2 WAN IP - found in the WAN Settings page on the R2 into the DMZ function on your ISP router. If you didn't do a factory reset after upgrading to the DumaOS 4 Early Access firmware then please do so and it will behave better after that. Do this first then the DMZ.

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 Have you done any port forwarding on the R2 or used the DMZ? What platform are you playing on? Are you using the Geo-Filter? Do you get an Open NAT with it disabled?

Have you upgraded to this version yet? https://forum.netduma.com/topic/60946-new-r3-firmware-dumaos-401147/ If not I would highly recommend doing so to see if you get any of the same issues. The fact that you need to wiggle a cable around to make it work would indicate to me that it's probably a faulty cable and replacing that would likely fix it. Can you provide a screenshot of the LAN Settings page and the logs from when the issue happens if you still get the issue on that firmware please?

So the Geo-Filter is measuring the latency to the server itself and the in game ping is showing that calculation + processing delay. All games have it but not all choose to show it in their ping calculations. As a rough guide up to ~30ms on top is okay though it can be lower so it can indicate that server is under a heavier load, in which case forcing a different server even if it has a slightly higher ping shown on the Geo-Filter might actually play better for you. It's essential the Geo-Filter is enabled before the game client (e.g. Steam etc) if on PC or the game have been launched. If you change Geo-Filter settings when you're on the game then you will need to restart the game for those changes to take effect, otherwise it will use the previous Geo-Filter settings and appear not to be working. Strict Mode should also be enabled & Fast Search should be disabled, they are by default so if you haven't changed them you can ignore it. If you have changed or want to check them can be found in the Geo-Filter menu that can be found by clicking ⋮ in the top right hand corner of the page and go to Settings. If you do these things then it will stick to the radius you've set, other than any servers on the global whitelist (for example Dublin usually) or manually allowed servers (like the Dublin servers).

What do you want it to be? I'll change it for you

Try with 70% as that's our suggested starting point and adjust from there based on how it feels/until you don't see any spikes - keep in mind that during peak times spikes like that are more likely to occur due to ISP peak time congestion. It will always try to connect to the Dublin server as its for authentication and required for online play so if you allow it you can play with the filter enabled but you will need to do so a few times as there will be multiple servers in that location. Once you've got all the ones that appear blocked there it will work. If you block a server it should keep you connected to it until that connection has been severed and then it would be blocked. It's nothing to do with Ping Heatmap, it has a pre-compiled list of servers, they have become out of date and when they do they're unable to be pinged, by default they then show N/A -1000ms because it timed out once it hit 1000ms without a response. Everyone with Ping Heatmap is seeing the same for CoD at the moment, myself included and it will stay that way until we've updated the pre-compiled list with an updated set until they inevitably get out of date again. Here are the server locations, they never change:

Okay so an issue with your ISP or game perhaps. Click your name top right of the forum and go to account settings, you can change it there

Is Congestion Control set to Always or Auto? Have you found 50/50 gives you the best results or just randomly set? SmartBOOST should be used so the devices/applications you care about get prioritized above traffic you don't care about as much, if there was something impacting your ping results then this would help it. Given the ping statistics you provided, you had a maximum of 442ms but over 232 successful packets your ping averaged 22ms which indicates that you only experienced a couple of quick spikes rather than a consistently high ping and so it was relatively stable overall with 2 packets lost at just under 1% that's quite acceptable and I assume they would have happened with those couple of spikes which makes sense. So far then it indicates it's more of an isolated incident of spikes rather than a persistent one. The logs contain entries that can look like issues but are normal processes, that's why it's best for a user not to try to diagnose issues solely based on logs, if issues are occurring that can't be diagnosed through normal means then logs can be looked at for more information by the devs but its very rare this is needed and the entries you've mentioned aren't anything I haven't seen before. For example the hostapd entry can occur when Ping Optimizer fails and that could occur for any number of reasons such as the server times out and so it can't set the correct Congestion Control percentages etc. Some can appear when it's not using a certain setting but it looks like an issue because that setting isn't active and fails, that's what I mean by verbose, we're not heavily restricting the output to the log, normal processes appear there that can seem troubling if you're not used to them. cfront & RTNETLINK errors weren't in the logs you provided but again they're not necessarily any immediate cause for concern.

Check direct to your ISP modem/router to see if you get the same issue because if you do then nothing you do on the R3 would make a difference as it wouldn't be the cause

If you've fully disabled the Geo-Filter and it's still occurring then check direct to your ISP modem/router to see if you get the same issue Yeah it's getting outdated very quickly at the moment, the team are aware and will push another cloud when they can

Very likely an authentication server is getting blocked, look on the map when that error appears, look for a blocked icon and allow it. Repeat the process as it may take a few times then it will work. If you could provide the IDs also we can get them globally whitelisted.

The R2 was sold with DumaOS 3, DumaOS 4 wasn't advertised as a reason to buy the R2, it was developed on the R3 itself and to get it on the older R2 hardware was a challenge that we didn't need to do but wanted to for our customers. We've explained why there have been delays and this hasn't just been for the R2 either. We never promise firmware because it's always subject to change, I've said many times we don't provide ETAs. The next R2 DumaOS 4 firmware would be the final firmware so the more time we take the more stable it will be overall. Also it is a support forum so there are only people posting issues here.

I did miss that part, my apologies. The logs are primarily for the devs to look at if needed and as such they're quite verbose, they contain backend entries that can look like issues but are normal processes. I doubt they specifically will be causing you issues but if it ends up that they are I can pass them on for more investigation. 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?

The dublin server is an authentication server required for online play so you may need to allow servers appearing blocked there a few more times and then it should work just fine. If you could then provide the IDs we can get the cloud updated with them.

It keeps getting out of date, I've asked the team to update it again

If it's just during peak time when it drops for example then that's just peak time congestion so I'd say leave it at your normal speed unless you're frequently playing during that time. If so or it's happening a lot of the time then setting to around 425 for the middle ground would be a good idea

It really depends how much it fluctuates, if it's significant for example frequently drops to 450 then it may be better to put in an average like 475

It's best to tell it the speeds you actually have/expect so it's working with the correct information, otherwise you are unnecessarily throttling which could have the opposite of the intended effect.

What do you mean it's not stable/isn't working exactly? How are you determining this/what are your settings? Previous version is here: https://forum.netduma.com/topic/58424-new-r3-firmware-dumaos-40645/

If you tell me why you're reducing your speeds and lowering the percentages I can best understand and advise

You don't need to lower your speed and lower your Congestion Control percentages, you should only lower Congestion Control and have you speed set as you receive/expect. Why are you reducing the speeds also? It wouldn't put a strain on the router though.

Could you provide a video of what you're seeing please with it off when enabled?

Could you provide a video of the lag you're seeing in game along with the ping you have when that occurs?

Good to hear you got that sorted. If you disable filtering so you can still see icons on the map, where does it place you when you get into a game?