Netduma Liam

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?

In theory you could share the config files with friends and family if you wanted to and they could set it up on their devices, though that's more a question about your account to ask your provider. Currently yes, the change VPN location you'll need to change the configuration file in the VPN Setup.

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

We did initially have this option for PureVPN and HMA, however with the frequency that modern VPN providers modify their config files, it makes it really difficult to maintain this approach. When you say multiple users, are you referring to multiple devices on the home network? If so you can do that by adding them to the VPN traffic section. Can you also explain what you mean by unlimited access? There's no limits in DumaOS as to how much traffic you can send through the VPN.

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.

Are they still not showing if you try to access the interface from a private/incognito window? It may that it's a caching problem.

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.

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.

Hey, I've responded to the topic you've created. Let's continue there.

Which features specifically are you not seeing? Let us know and we'll be able to say whether that's expected or not.

We don't have an ETA as yet, we're making some substantial changes to how Geo-filter works. Our testing has proved very promising, but it's still ultimately in development so I can't yet provide an ETA.

We've made a change via a cloud update, could you try re-syncing again and see if it updates?

Since deactivating it have you tried re-syncing cloud again? If not you'll need to do that to get the latest information.