Netduma Fraser

That's not something we can help with as the purpose of the router is to get the best connection possible so we'd always advise selecting the closest servers

You can do all that with 1Gbps and the R3, more powerful hardware wouldn't be needed for that - Netflix for example recommends at least 15Mbps for 4K streaming, some places suggest 25Mbps so just the 1Gbps is capable of running 40 - 66 4K streams at a time - I wouldn't suggest it of course but I'm just breaking down how 1Gbps is plenty for your actual use case.

You'll need to experiment further with the Congestion Control percentages and see what works best for you

No you don't need to do that as bandwidth will be shared among devices based on need

Could you grab the ID of that lone server please? It's likely an anomaly but could be significant and a reason you're not getting a game. I notice you're not on the Early Access update currently, have you tried on that version to see if you get the same issue?

Glad to hear you got it sorted! DMZ isn't a state you put the router in, you put a device into it. You should definitely put the R3 in the DMZ on your ISP modem/router (if that device has WiFi) as that will ensure internet traffic goes through to the R3 unimpeded. Depending on how your ISP modem/router implements this (if applicable) you may need the IP address of the R3. This can be found on the WAN Settings page on the R3 or in the connected device list on your ISP modem/router. The other way that won't always be necessary as #1 should be enough would be to put your gaming device in the DMZ on the R3 - this should only be done for a console, never a PC. You can do this in Setting > Port Forwarding > Add Device DMZ and choose your console from the devices list.

I'm slightly colour blind so you'll have to tell me, if you click the # button on the RGB controls and enter 6 f's ffffff does it appear more white to you then? It looks white to me

You can re-upgrade to the same firmware version, that may work, otherwise you should be able to downgrade yes to the the public version

Added

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.