Netduma Fraser

Even if it's not a double NAT, a strict NAT could make searching harder. Okay keep us posted!

Good to know, keep us posted!

Added

We can send new antennae if necessary, however, it is likely it's just that it's come apart instead of breaking, check the video to see if that applies + how to fix. If that's not it please provide a picture of how they're broken please antennaepop.mp4

The only thing to do really in this situation is reboot to get it loading again. It is vital that you close the interface after rebooting and wait at least 4 minutes for it to complete the boot process

Go to the System Information page, on the Rapp panel click the icon and change the retries to 5. Reboot the router from the interface, close the tab, wait 4 minutes then access and see if it loads

Do you require VLAN or PPPoE for a connection? I've given you Early Access so you can try that firmware and see if it works better for you https://forum.netduma.com/forum/144-netduma-r2-early-access

Added

Added

We'd have done some cloud updates over that time but nothing that would specifically disrupt the search. Whats your NAT status? When you're not getting a game zoom out fully on the map to see if there is anything else that appears blocked/when Geo is disabled zoom out to see if there is anything else allowed. You're not using a VPN are you?

What do you mean by constant, how often is it happening? At least from the limited log it looks like your public IP changed which caused it. 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

There isn't much in the log but could you disable UPnP and see if the issue continues please?

Good to hear! I'm sure it will, its still really solid hardware

You won't be able to get DumaOS back on it now so you will be stuck with the DD-WRT firmware unfortunately

There is some useful information here: https://support.netduma.com/docs/dumaos-4 There is a quick video from us here: https://www.youtube.com/watch?v=9Dd1VVUz6II There are also longer/more in depth tutorials/videos on YouTube from other customers

That is located in the US so: If the Geo-Filter is enabled and covering Cape Town and the servers are shown in the US then disable Geo-Latency & Ping Assist, restart the Xbox then try again. If the Geo-Filter is enabled and covering Cape Town and the servers are shown in Cape Town but has a ping like a server in the US then add it to your deny list, keep doing that, the more you do it the less you'll get them and the more Cape Town games you'll play. Give us the IDs of those incorrect servers and we can get them corrected.

Disable Steady Ping, that will raise your ping. Also if you're just letting the Geo-Filter connect you anywhere then your ping will be higher, you should use it to connect the closest servers, where abouts are you located? There is no need for them to contact us, it would just introduce an unnecessary middleman and delay support given they don't have access to make changes on your router/see how the router is set etc.

It is prioritizing the console, that's why its good to have the device added as well as a backup. It's detecting Valorant as Video/Streaming incorrectly but it still is being prioritized, however we are testing a cloud update currently which will have further improvements for Valorant detection in it. Did you have the main router handle PPPoE and put the R3 in its DMZ? Are disconnects on all devices or are you just getting disconnected from the game? Are you using the Geo-Filter? If so do you have Steady Ping enabled and are you forcing the closest servers to you?

Added

Sounds like the ethernet cable connecting the R3 to the Asus is the limiting factor, switch it out for another and test again. Also having devices upstream may impact the speed you get for the Xbox, not that it needs a lot of speed for gaming

Don't change Ping Assist, keep that at zero then just cover Texas by moving your location and adjusting the radius. If you're in France then the ping will be high and likely unstable to a server that far away

You'd have to click on them individually. I may have missed some but these aren't game servers and can be removed: 1750030 17500L0 175010S 17501GF 175025T 175041N 17505GK 17505GY 17505HZ 17506NU 17507DV Q0483B Q048IF Q0496B Mislocated: 175NVOF should be California None that are required to be allowed at least, are you having the same issue over the weekend when the player count is higher?

Added

Added

You mentioned you were able to downgrade previously/that you can access settings so you can do so from there. Otherwise routerlogin.net/adv_index.htm will take you to a version of just the NTGR settings pages. 3.3.535 is the DumaOS version, 2.3.2.134 is the firmware version, it is correct