Netduma Fraser

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

The bufferbloat test isn't the best way to determine values, 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. Doing the screensharing is more bandwidth intensive, that's why following this guide and instructions is better as you make your network essentially as bad as it could possibly get and then apply settings incrementally to determine what best brings your network as close as possible to its baseline.

Yes playing on a further away server is likely to worsen your jitter. No, the Geo-Filter and your bufferbloat test are not connected. The Geo-Filter shows game servers you connect to, it is highly unlikely to show the bufferbloat server you're using. The bufferbloat server could be anywhere, that's the point, doing the test at different times of the day could have you connecting to different servers and therefore getting different results. This is why I as well as Darkness said not to put too much emphasis on its results. Yes it is testing your network utilizing a server for the test. Here is an analogy for you. Your ping without bufferbloat is like driving your car on an empty road, you're going to a location and you know how long it will take you to get there, for example 20 minutes. This could be your baseline ping for example 20ms. Your ping with bufferbloat is like driving your car on a road with traffic, you're going to the same location and you know how long it should take you to get there (e.g. the 20 minutes), however due to the bad traffic it actually takes you 40 minutes to get to the same destination. Your ping here could be 40ms for example. In regards to the server the bufferbloat test is using, without a destination to test it against you can't get a ping value or a destination to drive to. Now imagine your place of work changed depending on the time of day and the time you start work changes as well therefore it could take you anywhere from 10 minutes to 1hr to get there. Would you be so confident to say that it takes you 10 minutes to commute to work everyday? Without knowing the server the bufferbloat test is using your results cannot be 100% trusted. That's why the pingplotter suggestion is better, you know the exact server you're using, you do a test to establish your baseline ping (ping without bufferbloat) and then apply traffic and your ping raises, just like road traffic extends your journey time and then you apply Congestion Control to limit the effect that traffic has on your ping. There really isn't anything else we can advise honestly: You've established it's an issue without the R3 - that automatically eliminates us personally from needing to troubleshoot with you We've advised you select the closest possible servers, this will help lower the ping and improve stability (jitter) We've advised you on how to effectively test and set your Congestion Control percentages to lower your ping and improve stability when bufferbloat would ordinarily apply

You can still use the radius but you should cover servers you know roughly what you will ping to (use Ping Heatmap) so you can select the next lowest ping servers. The further away the servers are the higher ping they'll have and the worse they'll play.

Good to hear! I've given you Early Access https://forum.netduma.com/forum/151-netduma-r3-early-access/ if you'd like to try that to see if DumaOS allows access again.

I didn't say you had it set there but the outer limit of your radius is in Utah which is almost the other side of the country from you and there is a server in that location so if I had to guess it's going to be at least an extra 20ms if you were on that server. Also given the timezones within the US, you're covering two other time zones who are up to 2hrs behind you so based on the times you mentioned it being worse you're covering around their peak time. So playing on those servers before the time you mentioned might be great, in which case, playing actually on servers closer to home during that time frame might play better. Also, whether you play on the Florida servers because of 'sweats' or not, they are going to be the best servers for you, we can't make the further away servers play more like closer servers so at the end of the day your issue is the connection and your radius setup is not conducive to having a good connection.

Added you to the R3 Early Access. We're aware Ping Optimizer isn't 100% reliable and the moment and will be resolved in the next firmware. Why do you think the Geo-Filter isn't working? It's unlikely that it's on your side, this happens every year, there is a slowdown after the first couple of months of the new year, into summer and then once a trailer for the new CoD happens people jump on again to get practice in. Lots of players around the beta time and more so between the beta and launch, aided by any new seasons of the previous CoD and Warzone like has just happened within the last week or so. Usually but not always there is a slowdown sometime between launch and Xmas, then when people get it for Xmas there is a big influx of players, new and those returning due to having time off for the holidays.

Your eyes can do about 13ms so you literally can't perceive that difference. You're selecting a server further away than where you're located so the game stability is going to be lower, it's unlikely the jitter that is getting you but people who have a lower ping that live closer to the server. Use Ping Heatmap, identify the next lowest ping server and force that one instead. At the limit of your radius you might be getting a server almost on the other side of the country.

You're posting in an R3 topic that's why, for the R2: https://forum.netduma.com/forum/144-netduma-r2-early-access/

12 isn't the best but it's certainly not going to hugely negatively impact your game, if you do everything else to ensure you're connecting to the closest server, have it setup to limit the bufferbloat then you shouldn't notice it too much. Given you've changed IPs and it's happening direct to your modem (ruling the router out as a culprit) then it's likely something less easily resolved such as the wiring inside/outside the home or to the cabinet/exchange for example.

No we don't but good question!

What was the jitter amount they detected, were they not concerned with the amount?

They've asked if the R3 is handling PPPoE or VLAN or DHCP identifiers at all?

Apologies, I think I've misunderstood you, you're using an OpenVPN client on the devices themselves right? In which case there isn't really much on the router that would slow down the speeds other than the usual speed settings, you said it happened a few months ago, did you change any settings around then? How long does it take to slow down to 20Mbps, right away, after minutes, hours? Is there any pattern you can see such as when using heavy bandwidth applications, other people getting home and using devices etc?

There is a cloud update mid release currently that should help with this, you should have it by the end of the week

There is a cloud update mid release currently that should help with this, you should have it by the end of the week

They're just referring to the game servers that would be within your radius in that above quote, not to do with the bufferbloat testing servers. He is saying to find the lowest/most stable ping server within that radius you've set (or outside radius if applicable) and then just force that server so when playing in the future you will get the server you want every time and not suffer from the randomness of getting any server within your current large radius. What they're saying regarding the bufferbloat test is that it's not necessarily the best test to base your results on as depending on when you're using it etc you may be testing using a server that is very far away, in which case your results will also be bad. 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 and will give you a good Congestion Control value for your connection.

Thanks for letting us know, it really is a weird one, if I hear anything about it from NTGR I'll let you know