Netduma Fraser

Fingers crossed, good luck with the move!

I suspect the longer the uptime the easier it is for the CPU to hit 100 consistently and cause issues so I don't think it'll be a problem on the new one coming

As above, Speed Test Bypass must be disabled, CC set to Always and I would suggest removing Priorities on SmartBOOST as well as they could interfere with the test.

How big are the latency spikes exactly? If CPU isn't going to 100 then I would lean towards Congestion Control needing to be fine tuned. Now that you have Upload Congestion Control it should be much easier to eliminate this. How do you have CC setup?

Great advice above, there is also Congestion Control which on the whole will prevent devices saturating (using up) all your bandwidth and therefore preventing lag

You can force central servers with the Geo-Filter yes, if you are the party leader then your friends should then be put on these servers too

It will support Wireguard yes, how would you be wanting the NAS to be connected? Via USB or WiFi/eth? If USB that won't be possible, if WiFi/eth I don't see why that wouldn't work.

What have you tried specifically? Without specifics it's very hard to me to advise steps to take

Yeah I know, it's just as a test for pinging, out of 10 games for example how many pinged vs didn't?

Any changes in the behavior?

This is my conservative estimate based on what I've been told

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

I do have a theory, could you try forcing servers much further away from you, EU if you're in the US and vice versa and see whether you get more consistency in pinging please?

I've had a look at that router, please do the following on the HA35: Disable UPnP Disable the 3 Attack Protecting options Disable SIP ALG Disable bandwidth control Give the R3 a static/reserved IP so the DMZ never becomes inaccurate See if it works better then please. Also make sure all devices are connected to the R3 - you could disable the WiFi on the HA to better achieve this and prevent accidental connections.

What web browser are you using to access? If you use an incognito window to access does it work?

Yeah we're looking into it, we can't reproduce it after the latest app update so it is hard to therefore fix

We are aware Ping Optimizer/Speed Test isn't 100% reliable at the moment and it's something the team are working on. Those features can still work, it just may not be every time. In the meantime best to adjust Congestion Control manually in Ping Optimizer > Advanced.

It might be worth posting a clip of your gameplay, if you've gone through 4 different routers and your internet connection is fine then it may be another problem. For example it may look as though it is lag when it isn't.

Great to hear you got it sorted. The ports are limited to 1000Mbps, so with taking routing into account the theoretical maximum is probably about 950 but that varies so 900 is very good.

If that's what works for you that's great!

I see you've switched between .23 and .20, did you do a factory reset after upgrading to .23? 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.

On the Geo-Filter the host of the game is the icon with the controller within it, click that when you're in a game, it will then manually ping (rather than automatically ping where the Geo-Filter pings it for you)

If they truly are authentication servers they cannot be blocked, you shouldn't be playing on them though. I'd suggest deleting all the allowed servers you've done so we can take out that variable, then do the following and see if it then works better. Quit the application/game/client completely including from the System Tray Remove device from the Geo-Filter Resync from the Geo-Filter Map menu Re-add the device to the Geo-Filter with the manual option Set up the Geo-Filter how you like Wait 2 minutes Boot up application/game/client

UPnP we're looking at, Port Forwarding works but they will appear inactive at the moment but it is working - otherwise you wouldn't get an open NAT.

Go to the System Information page and then in the Rapp panel menu ≡ change the retries to 5, reboot from the interface, wait 4 minutes before accessing and see if it works then please.