Netduma Liam

I'm afraid not, I asked about it this morning, there's is one bug which is now fixed, but I believe there's still a separate issue. We'll get an early access/beta firmware built when we've got more information on the issue and hopefully we can give it to some people such as yourself and you can test it. I don't have any kind of an ETA for such a fix as we're not sure whether we're going to be able to do that yet, but in an ideal world that's how we'll proceed.

Not as yet I'm afraid, I chased up the developers about it this morning and they're going to see if they can allocate more time to debugging this issue today/this week.

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.

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.

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?

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.

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.

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

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.

Looks like it managed to resync successfully that time. As a side note - are you using Hybrid VPN? There's an error in there relating to it and I'm curious whether that might be causing the problem. If Ping Heatmap still hasn't resynced properly, please disable the VPN and try again, see if it works after that.

You don't need the PS5 in the XR DMZ if you've also got the XR in the modem's DMZ, so you can remove the PS5 from the DMZ. Could you please try going to Geo-filter and resync cloud from the three-line menu there. Please then download the logs again and send them over.

OK, quindi non riesce a risincronizzarsi, ma non c'è motivo per spiegarne il motivo. Abbiamo appena testato internamente e funziona. Potresti per favore scollegare l'XR dall'alimentazione per alcuni minuti, quindi ricollegarlo e vedere se può risincronizzarsi dopo?

Could you please do the resync again, then go to System Information -> Click the three-line menu under 'Logs' and download the log file. If you could please send that over to us and mention the approximate time you resynced, that'd help us troubleshoot this more.

Set Ping Assist to the maximum ping you'd like to play in-game. I'd suggest about 30-40, that might speed things up for you. We might be able to get this added to Ping Heatmap so you can always check on the servers, I'll speak with the team and see if we can get that added.

Is this for Warzone again? I can see that a few of them have stopped responding so I'll speak to the team and get them to push an update as soon as they can.

In general, the results look pretty good as far as I can tell. Were these tests run while saturating the connection as Fraser mentioned? I'll link the guide below again for convenience. http://support.netduma.com/en/support/solutions/articles/16000074717-how-to-test-your-internet-ping

Thanks for that, could you please disable the DumaOS classified games rule, then add a new one. In the new rule, select your games console as the device and 'Games Console' as the service when prompted. After that, set Congestion Control low, down to about 40% maybe. Then set it to always. After doing this, click 'Reset allocation' on Bandwidth allocation just to be safe. Then, play some games and see how it feels. A couple of follow up questions: Do you know if you require PPPoE, VLAN or DHCP identifiers to get a connection to the internet? Are you using Geo-filter? If so could you share your configuration with us?

Just to clarify, have you reset since the upgrade to the latest firmware version? If not, could you please do so. Can you also answer a few questions for us: Are ALL devices on the network connected via the R2? Have you got any custom rules configured in Traffic Prioritisation? If so could you please share them? If not, is the DumaOS classified games rule detecting traffic while you're playing? This is indicated by a red light on the rule, and the packet counters increasing. What's the make and model of your modem?