Netduma Fraser

The Ping Optimizer servers may not always be available and so can fail sometimes, we're rewriting the feature as well currently. So would recommend changing Congestion Control manually for the moment. However, I've given you Early Access so you can see if it is more consistent on that firmware: https://forum.netduma.com/forum/151-netduma-r3-early-access/

It's not necessarily a thing we can add - do you see it working for normal CS2? Have you ever seen it work for Faceit servers?

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 Are ALL devices connected to the R3? What speeds do you pay for/expect and what are you receiving? Where are you testing the speeds?

I mean at least in the screenshot above you won't be able to connect to anything. To force a server you wouldn't use Ping Assist, you'd have that on 0 and then just the radius over the server you want to connect to.

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

In the Early Access sub forum - do you mean the RGB?

I suspect that could be due to the console taking the ports needed - if you turn on the PC first does it then show Open?

The fact you're getting timeouts after the first response indicates there is more than one hop which could indicate you do have a CG-NAT. If this is the case the only solutions are: Secure a static public IP from your ISP - this is something that they would usually charge for Change ISP to one that doesn't use CG-NAT

Based on the Ping Heatmap pings and your forum profile it looks like you're in Bangladesh not in the EU and so you're probably hitting a ping limit - the game isn't going to want to connect you to servers you're going to have a minimum 200 ping to. We also can't guarantee you'd be able to force servers that far away from you.

Have you ever had an Open NAT with the internet provider you're on currently? It sounds like you're on a CG-NAT which there is a test for at the bottom of this article https://support.netduma.com/en/support/solutions/articles/16000076587-dumaos-optimal-settings-guide-open-nat

Thanks for that, I'll pass it on, factory reset or do what is needed to gain access then get on the one we posted today and see if that is better.

The in game ping should be higher than the speedtest ping, is that not the case? Are you connecting to a super close server? You might be being lag compensated in which case forcing a server slightly further away with a higher ping might provide a better experience.

Do keep us posted, you could also disable filtering which would allow you to still see servers/where you connect to which will give you an idea of if you're able to connect normally

On the Geo-Filter or Heatmap - you won't always see the servers on the Geo-Filter and the Italian servers are amongst the Spanish servers in that they don't always seem available

Can you provide a screenshot of your Geo-Filter page showing what you see when you get connected to this server please?

Added

You have access already

Did you make any specific settings for the PC to get an OpenNAT previously? Where are you seeing that ping, on the Geo-Filter or in game?

It will be possible, apart from the power light. Once main issues are resolved we can look into these nice to haves

That's great to hear. If the console is showing as having an Open NAT then you will have an Open NAT overall - the device can't have an Open NAT but the game have moderate for example, it doesn't work that way, it will be a misreading

Disable the Geo-Filter then launch the game, does it appear open then?

If you unplug the R3 from the modem and then try to access the R3 can you access then? If so I'm not sure what has happened but does sound like the bridge mode is preventing access for some reason. I'd suggest just doing the DMZ mode really - they both perform the same function essentially

We need to do an update, I believe the testing server it's using is out of date and as the server was hardcoded we need an update to change it. I'd suggest changing speeds/Congestion Control manually for the moment.

If you've rebooted the R3 then it's quite possible the WAN IP has changed, double check the WAN IP then check the IP in the DMZ, if needed update it and then it should work again

How is it you're on .170 when you've not been added to Early Access? Disable GeoLatency Disable PingAssist (set it to 0,0) Enable Strict Mode Disable Fast Search Use Simple instead of Custom radius Then restart game or wait 10 minutes (in the lobby in the game). If that doesn't work, reboot PC/Console and it should work then.