Netduma Fraser

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.

I'm not sure when a fix will be if it'll be in the next one or not but as far as I can tell there isn't anything you can do about it - I have the same issue as well, just have to wait for the 30 seconds

The max 100 issue was likely due to an ethernet cable, swapping that out for another that is a Cat5e or higher cable should then allow it to go higher. Reboot your ISP modem/router, wait 2 minutes then reboot the R3, wait 2 minutes then access and you should get internet. We haven't forgotten, we will get a collection sorted, sorry for the delay on that.

That means something else is likely using port 3074, if you disconnect whatever that device is briefly then reboot the Xbox it should then be available to select

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.