Netduma Liam

When downloading an update and not connected to the VPN, can you check Traffic Prioritisation and see if any of the rules show as detecting high priority traffic? This will be denoted with a red light on the rule.

I'll double check with the team and get them to move it if not.

So when you manually block the servers, it takes a while for them to actually be blocked? Does this mean if you search for a game again right away, you still get connected to these servers? Can you check the ID of the server before you block it, then check the ID of the next server you connect to to verify that they are not the same?

That sounds pretty good to me! The only other thing I might suggest trying would be to actually disable DumaOS classified games (If the PS5 is the only device you game on) and instead add a new rule, select the PS5 as the device and 'Games Console' as the service. See if things in-game improve after that.

OK, can you paste the config file here so we can check it? Make sure you remove the Private key and the public key before posting it though.

Welcome to the forum! Thanks for raising this, we are aware in some games this is the case and we're working to resolve it for a future update. It shouldn't however affect your matchmaking, are they outright not getting blocked at all? Are you getting servers outside of your radius, or are the servers inside your radius just not performing very well?

Who's your VPN provider? Have you downloaded their Wireguard VPN configuration files or are you trying to use the OpenVPN files? If so, unfortunately that won't work.

I think it may be worth trying it yes, it doesn't quite make sense why you're not able to see anything on the Geo-filter map.

That's odd, how are you testing the speeds, through the in-built Connection Benchmark or through a third-party speedtest such as speedtest.net?

You can leave those blank, or simply put 192.168.77.1.

Apologies for the delayed response, I'm discussing this with the team as we haven't been able to reproduce the problem as yet. We're going to look into it further and see if there's a way we can generate more load for Traffic Controller to handle and see if that can cause it to fail. It's a rare case so it's taking longer than expected to reproduce. We'll keep working at it, apologies for the inconvenience caused.

Por lo que parece, solo tienes tres dispositivos conectados al XR1000. Si todavía hay otros dispositivos conectados al módem ascendente, el XR competirá con ellos por el ancho de banda y no obtendrá el rendimiento total. Además, el XR1000 tiene puertos ethernet gigabit, por lo que solo podrá alcanzar velocidades de gigabit.

Were there any changes/upgrades made that led to you seeing this error message? If you've rebooted/upgraded the firmware, you will see this for a few minutes while the R2 boots up. If it's been longer than that, try clearing the browser's cache and refreshing the page.

Open a different browser, such as Chrome or Firefox, then go to http://192.168.1.1/. It should then load better for you. If it's a browser you've used to access the interface before, I'd suggest just clearing the cache in that browser as well.

We're not sure just yet, we're currently testing some new R2 firmware so it's in the works, but we're not close enough to give an ETA just yet.

Which rule is this referring to exactly? The error message is appearing because you haven't selected any ports to be in the group. Perhaps if you could let us know your use case here, and why you need to set this up, we can offer some more help in getting it working for you?

Nice! Yeah the R2 has gigabit ethernet hardware so it'll handle that just find. You may notice throughput is closer to around ~900mbps, but that's very common, most gigabit devices won't actually pull the full 1000mbps.

We don't have an ETA for the next firmware I'm afraid, we keep this page updated weekly with our latest progress on each firmware: http://support.netduma.com/support/solutions/articles/16000132677-dumaos-firmware-progress The most previous beta firmware for the XR700 can be found here: https://www.dropbox.com/s/1yxwq75k726hkgw/XR700-V1.0.1.34_Dumaos3.0_6.img?dl=0

We don't know, it'd be something they've configured on the server side so we don't know that sort of information. If you can connect to the Eastern servers, that may be your best bet.

OK, once they can actually provide config files, it should be much better for you. If you have any access to a Linux system, or are able to create a Linux VM/Install WSL (Windows Subsystem for Linux), I'm sure we can work out a way of getting you a config file to use in the mean time. If you're interested in having a go, check out this article I found: https://forum.openwrt.org/t/instruction-config-nordvpn-wireguard-nordlynx-on-openwrt/89976

That shouldn't happen, although if it's does you can pretty much always get the connection back by just removing the power cord from the R2 for a couple of minutes, then reconnect it.

This one looks to be a security update, the latest firmware with all the new DumaOS changes is still having remaining bug fixing done so it's not quite ready yet. Shouldn't be much longer now though!

Thanks for letting us know, we'll take a look.

When the problem occurs, do you have access to the DumaOS interface? If so, could you please download a copy of the log file from the three-line menu in System Information -> Logs? Also, please go to Device Manager when this occurs, click the three-line menu in the top left of the map and switch to table view. If you could then send us a screenshot of the top table, that'd be helpful.

Thanks for this, leave the DMZ disabled now. With IPv6 disabled, could you please now go and disable QoS completely again and check if that improves the speeds?