Netduma Fraser

Fuerce algunos servidores diferentes que están un poco más lejos de usted, incluso si tienen un ping más alto, pueden ser más estables

So the connection re-establishes itself automatically without a reboot or anything like that? If you haven't rebooted since the disconnect could you grab the log file from the System Information page on the router and post it here, that should give us an indication of what is happening. What router is it you're using?

I'll add you to the list for when we expand the group.

Hello, welcome to the forum! I would recommend going through our optimal settings guides here: https://support.netduma.com/en/support/solutions/folders/16000090646 for Destiny 2 you'll want to have strict mode disabled on the Geo-Filter - it is enabled by default. On the router go to Settings > Administration > Firmware Update and you can check for new versions and update there.

The Geo-Filter doesn't impact the connection in that way so it's more likely that you would need to adjust it to get a better server, perhaps the one you were playing on was under heavy load for example.

Lorsque ce message apparaît, cela a fonctionné, attendez simplement 1 minute, puis actualisez la page. Essaye ça: Quittez complètement l'application/le jeu/le client Supprimer l'appareil du géo-filtre Donnez le type de périphérique PC PlayStation dans le gestionnaire de périphériques (si sur PC) Resynchroniser depuis le menu Geo-Filter Map Ajoutez à nouveau l'appareil au Geo-Filter avec l'option manuelle Configurez le géo-filtre comme vous le souhaitez Attendez 2 minutes Démarrez l'application/le jeu/le client Ensuite, voyez si cela fonctionne mieux.

Je veux dire, attachez vos conseils de jeu au modem, avez-vous le même problème ? Allez sur la page Informations système puis dans le menu du panneau Rapp ≡ changez les tentatives à 5, redémarrez depuis l'interface, attendez 2 minutes avant d'accéder et voyez si cela fonctionne alors s'il vous plaît.

Of course, I'll add you to the list!

Fonctionne-t-il directement avec le modem/routeur de votre FAI ? Accédez au R1 à l'aide d'un PC et non du navigateur mobile. Pour ce message, redémarrez à partir de l'interface, attendez 2 minutes puis accédez et il devrait se charger.

Reboot the router from the interface, wait 2 minutes and then try the same config again please

Try this: client dev tun proto udp remote jnb-c01.ipvanish.com 443 resolv-retry infinite nobind persist-key persist-tun persist-remote-ip verify-x509-name jnb-c01.ipvanish.com name auth-user-pass comp-lzo verb 3 auth SHA256 cipher AES-256-CBC keysize 256 tls-cipher TLS-DHE-RSA-WITH-AES-256-CBC-SHA:TLS-DHE-DSS-WITH-AES-256-CBC-SHA:TLS-RSA-WITH-AES-256-CBC-SHA <ca> -----BEGIN CERTIFICATE----- MIIErzCCA5egAwIBAgIJAMYKzSS8uPKDMA0GCSqGSIb3DQEBDQUAMIGVMQswCQYD VQQGEwJVUzELMAkGA1UECBMCRkwxFDASBgNVBAcTC1dpbnRlciBQYXJrMREwDwYD VQQKEwhJUFZhbmlzaDEVMBMGA1UECxMMSVBWYW5pc2ggVlBOMRQwEgYDVQQDEwtJ UFZhbmlzaCBDQTEjMCEGCSqGSIb3DQEJARYUc3VwcG9ydEBpcHZhbmlzaC5jb20w IBcNMjIwNTA5MjAyMDQ1WhgPMjA4MjA0MjQyMDIwNDVaMIGVMQswCQYDVQQGEwJV UzELMAkGA1UECBMCRkwxFDASBgNVBAcTC1dpbnRlciBQYXJrMREwDwYDVQQKEwhJ UFZhbmlzaDEVMBMGA1UECxMMSVBWYW5pc2ggVlBOMRQwEgYDVQQDEwtJUFZhbmlz aCBDQTEjMCEGCSqGSIb3DQEJARYUc3VwcG9ydEBpcHZhbmlzaC5jb20wggEiMA0G CSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQC30MFY2v8go65jdOYM/nHu9hlHQMbE ttdTxPIDMFuNS0UUxuHGUeJdVCtkeaDOKH3jHsGBczu1amYwphVv6A1qox1YTrzR Cbec7CaHL926VcOQQcDAPTmL+JPHhlpR21Xa+woHFGDW90LgASLAPtupXgc6LXfF wb3vVpDnkyPUp4J0DRo2+lq3UtbHaONbGx8jyzYu/kWSiLUc7X69OedoSwlmsGAC Qteki2o/b0uKTf84Ei+QEjGUquGJU+LETmo2IP55I+KuyZE6+zIiiegm25jgPDkr qlw2UrJiLCjUg4VhTdjF9/AUmT5tJbhZUGGx1/l0bGr+44ea7PmB3DELAgMBAAGj gf0wgfowDAYDVR0TBAUwAwEB/zAdBgNVHQ4EFgQUS/0UJYkd58Fwg9f2nxEcJU4Z 7q4wgcoGA1UdIwSBwjCBv4AUS/0UJYkd58Fwg9f2nxEcJU4Z7q6hgZukgZgwgZUx CzAJBgNVBAYTAlVTMQswCQYDVQQIEwJGTDEUMBIGA1UEBxMLV2ludGVyIFBhcmsx ETAPBgNVBAoTCElQVmFuaXNoMRUwEwYDVQQLEwxJUFZhbmlzaCBWUE4xFDASBgNV BAMTC0lQVmFuaXNoIENBMSMwIQYJKoZIhvcNAQkBFhRzdXBwb3J0QGlwdmFuaXNo LmNvbYIJAMYKzSS8uPKDMA0GCSqGSIb3DQEBDQUAA4IBAQCc9JV7IR8BfBrF/BQT Xg0SZMZyyMAxR2jfW9qMHKSeJuZVVjfHiqoynEgBCNbn71wZWv3OF/Thu9BJ4GiY J2Bc9nIa90D1NGYgiOVYLGXfUUqy5FgfrsWh0Go5oYm9l7W9pWfIifwsaZynkY0r TIHn32FF0H3+wZrGrEUzVL6qi+KD8iR3cBbLT+xUzulMTBp4JYaQnxpV4fZNS0Zs NrWKFWz4Iz1SSBcsnvUhfWs1aKx4yOJQx33Pc+KwpUI+meTlMjoh+AoTriooKU2M bOqLQl32y3pR0MP3fX4HDVFRylxdckEc+VryGNHQLUJiIBKBCORih/YiRhtEhpoB xmkw -----END CERTIFICATE----- </ca>

Disable IPv6 but don't enable DMZ on the R2 itself

That's all, make sure to message on Sunday by posting here with a device that is connected to the R2 so not on mobile data for example and we can grab the IP from your post

There should be more to the config files than what you have there so you're missing parts, what is the server you're wanting to connect to?

I think the best thing for us to do would be to force an upgrade through for you, could you ensure the R2 WAN IP from the System Information page is in the DMZ of your modem if applicable, enable remote support in settings on the R2 as well as disabling IPv6. Once you've done that let us know and we can push it through on Monday, so as you're experiencing the disconnects do this on Sunday night.

Hey, welcome to the forum! We need to update the configs on the basic setup so for the moment use the Advanced Setup, you'll need to get the OpenVPN configuration files from PureVPN and then paste the contents of that file in the config box. Enter your Pure user/pass in the relevant boxes and you should be able to connect.

Si vous désactivez le Geo-Filter avant de lancer le jeu, obtenez-vous toujours l'erreur ?

I'll add your name to the list!

Great to hear that, thanks for the update!

I believe it was due to a chip shortage and so the chip had to be changed - an equivalent chip was used but as the chip changed that meant changes needed to be made to the software to work with the different chip.

I'll add your name to the list!

Hey, welcome to the forum! I'll put your name on the list for when we expand the group.

It has to be set to Always, make sure you're changing download and upload. If that doesn't work then you are on an old beta version so there was a lot of improvement to be made on it and it's very unlikely you'll get that kind of spike with Congestion Control set to 70%

As it is essential for you, I'll speak to the team and see if we're able to manually fix this for you in the backend (if it's an easy fix) on Monday

I have been able to reproduce this, I think what has happened is that IP address is an IP address for a Microsoft server so I believe it is detecting that it's a public IP address rather than also a private IP address if you see what I mean. I can pass it onto the team but for the moment you would need to use a different LAN IP.