Netduma Fraser

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.

What device are you playing on exactly and what are your Geo-Filter settings? If you manually ping instead of letting it auto ping do you have better success?

I think at this point it would be best to factory reset to eliminate any variables and just adjust Congestion Control and see if it adheres then

The Steady Ping graph won't show unless the server is pingable so that's normal in that situation. What is your average ping and how much does it normally fluctuate by and then what did you set Steady Ping to?

Could be the above. What ping are you seeing on the Geo-Filter and in game? 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 the Geo-Filter/Congestion Control/SmartBOOST?

The team will look into it, do try the above in the meantime

I think the best thing would be to take some time going through the optimal settings guides here which will help you: https://support.netduma.com/support/solutions/folders/16000090646

The R2 will be getting DumaOS 4 at a later date, in which case this will be less of an issue

Thanks for posting your solution!

That's very enough, I'm pretty confident peoples experience will be a lot better on the next update

Disable Auto Ping then click on the server to ping it manually

The fix is coming next week and the CPU will be much lower then

If you turn on the console then wait 30 seconds before doing anything on it, then go to the game etc does it work then? We are aware of an issue in a delay to connect so it's properly what is happening here

As above, MTU really isn't going to do much for you at all. In terms of WiFi: Split the bands, give 2.4/5GHz different names and apply - you'll want to connect to 5GHz specifically for speeds Use a WiFi analyzer to find the least congested channel and change to that Experiment with the widths to see what gives better results Ensure it's in an elevated position - not on a metal surface Ensure there aren't any electrical / wireless devices e.g headphones etc within close proximity ~3 feet if possible Set the antennae to this position _ | | _

That is really weird, I don't know if it's due to a router setting or not but that doesn't sound like it, however I'll see if the team can try to reproduce it.

Sure! Does that mean that other servers ping normally, just not those 4?

Why don't you record a little bit of gameplay that showcases a scenario in which you think you should have won a gun fight but didn't and then we as a community can tell you whether we think it's lag or something else. As you're not sure what it is I think that would be the best way.

As above it can be found here: https://forum.netduma.com/forum/106-latest-firmwares/

They all have a working Geo-Filter, we'll still make improvements but if you're having issues I'd suggest making a topic and I can help you there.

In the console network settings from the screenshot there choose alternate port selection and choose 3074 and it should work better

No there hasn't been an update yet. HVPN may come in 1-2 weeks but that is an estimate not a guarantee.

You don't have to activate QoS, you just needed to set your proper bandwidth, disable QoS again and it'll be higher. However, as you're using PPPoE it's unlikely you'll get 1000/1000. If you can have the ISP modem/router handle PPPoE instead of the R2 you'll get higher speeds.

Uninstall the app then re-install it and it will work. You also have to be directly connected to the R3 WiFi. By super hot how do you mean? There is plenty of ventilation, is there a lot around it? You don't need to restart it, the CPU will drop, it won't run all the time that high, it will fluctuate. Update will be next week

Okay thanks, I'll pass that onto the team

Could be a memory issue caused by the CPU issue potentially which is preventing you accessing, in which case it'll be much better on the update next week