Netduma Liam

So you're not seeing any icons on the map at all? What device are you playing on? Could you double check that device is definitely connected to the XR1000 and it hasn't connected to the upstream router/modem? This may happen if using Wi-Fi. Could you please provide a screenshot of how you've got Geo-filter configured exactly?

Hey, did you by any chance remove the ListenPort field from the config file? While trying to reproduce your bug, I've noticed ListernPort is essential, otherwise it'll throw this error. To provide an update: We've successfully reproduced your issue internally and we're now working on fixing it with a developer.

OK, let me raise a ticket with our VPN dev and see if he can find any reason as to why that's not working, it looks perfectly fine to me. I'll get back to you.

Have you posted your message here from a device connected directly to the R2? Do you know the model of the Arris? Is it a router/modem combo (Has Wi-Fi) or is it a pure modem (Does not broadcast a Wi-Fi network)?

Yeah looks like the R2 has given it an IPv6 address but it's not being used. Can you confirm if you've ever had an IPv6 address on the Xbox when connected to the R2?

Does it work again briefly after you reboot? If not, can you paste the config file here? Make sure you remove you remove the private and public key before you paste it.

To clarify, you've previously had IPv6 on the Xbox when playing through the R2? Is that correct? In Device Manager, click on your xbox, does it show as having an IPv6 address there?

I don't appear to be able to access your R2. Have you posted your message here from a device connected directly to the R2? If so, could you please see if you're able to access your modem's interface and put the WAN IP of the R2 in it's DMZ? Let us know if you have any issues doing this and also let us know the exact make and model of the modem if possible.

Are all devices losing connection or is it just specifically devices that are connected via Wi-Fi? Are you able to access the DumaOS interface when the disconnection occurs?

It should still show in the logs. You could perhaps experiment changing the DNS server to a different DNS in the country you're VPNing too. Otherwise if you could grab a log next time you come across the problem that'd be really helpful.

Interesting, I'll check with the team if it's whitelisted for any reason.

Do you see anything in the logs in System Information around the time that it occurred? Could you perhaps click the three-line menu in the top left of logs and download them, then send them over to us?

Excellent, thanks for confirming. That's great to hear. Do let us know if you have and further questions or issue in future.

Copy the wireguard config you've currently got setup in Hybrid VPN and paste it into a notepad. Save that notepad file as something like "wireguard_config.conf". Make sure you save it as .conf and not .txt. Then, download the WireGuard client from here: https://www.wireguard.com/install/ Then on the WireGuard client, import the config file you saved earlier and see if it works. If it doesn't, we know we still need to work on the config file.

Can you download the Wireguard Desktop client and verify that the exact config you're using in Hybrid VPN is working in the desktop client?

I'm afraid we don't have an ETA for this fix, it may however be something we can resolve over a cloud update in which case it shouldn't take too long, but it's hard to say until the team have been able to deduce exactly what the cause is.

I've looked into this and we did find issues with Connection Benchmark on the particular DumaOS version you're currently running. Let me speak to the team and see if there's a newer firmware version we can get you upgraded to. I'll get back to you!

What are you seeing when you try to load the interface in another browser? Could you try doing so from an incognito/private window so we know cache isn't the culprit? Are you getting any errors when trying to run the Connection Benchmark? Could you clarify which firmware version exactly you're currently on?

As a test, could you disconnect the WAN cable from the R2 and try again? Unfortunately it may require a few resets again to verify.

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?

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.

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.