Netduma Fraser

Added

Thanks for the report, I will pass it on to the team to test

Just enter the config: client dev tun proto tcp remote 149.22.82.28 7770 remote 149.22.82.28 8443 remote 149.22.82.28 443 remote-random resolv-retry infinite nobind cipher AES-256-GCM setenv CLIENT_CERT 0 tun-mtu 1500 mssfix 0 persist-key persist-tun reneg-sec 0 remote-cert-tls server auth-user-pass <ca> -----BEGIN CERTIFICATE----- MIIFnTCCA4WgAwIBAgIUCI574SM3Lyh47GyNl0WAOYrqb5QwDQYJKoZIhvcNAQEL BQAwXjELMAkGA1UEBhMCQ0gxHzAdBgNVBAoMFlByb3RvbiBUZWNobm9sb2dpZXMg QUcxEjAQBgNVBAsMCVByb3RvblZQTjEaMBgGA1UEAwwRUHJvdG9uVlBOIFJvb3Qg Q0EwHhcNMTkxMDE3MDgwNjQxWhcNMzkxMDEyMDgwNjQxWjBeMQswCQYDVQQGEwJD SDEfMB0GA1UECgwWUHJvdG9uIFRlY2hub2xvZ2llcyBBRzESMBAGA1UECwwJUHJv dG9uVlBOMRowdelightfulDVQQDDBFQcm90b25WUE4gUm9vdCBDQTCCAiIwDQYJKoZIhvcN AQEBBQADggIPADCCAgoCggIBAMkUT7zMUS5C+NjQ7YoGpVFlfbN9HFgG4JiKfHB8 QxnPPRgyTi0zVOAj1ImsRilauY8Ddm5dQtd8qcApoz6oCx5cFiiSQG2uyhS/59Zl 5wqIkw1o+CgwZgeWkq04lcrxhhfPgJZRFjrYVezy/Z2Ssd18s3/FFNQ+2iV1KC2K z8eSPr50u+l9vEKsKiNGkJTdlWjoDKZM2C15i/h8Smi+PdJlx7WMTtYoVC1Fzq0r aCPDQl18kspu11b6d8ECPWghKcDIIKuA0r0nGqF1GvH1AmbC/xUaNrKgz9AfioZL MP/l22tVG3KKM1ku0eYHX7NzNHgkM2JKnBBannImQQBGTAcvvUlnfF3AHx4vzx7H ahpBz8ebThx2uv+vzu8lCVEcKjQObGwLbAONJN2enug8hwSSZQv7tz7onDQWlYh0 El5fnkrEQGbukNnSyOqTwfobvBllIPzBqdO38eZFA0YTlH9plYjIjPjGl931lFAA 3G9t0x7nxAauLXN5QVp1yoF1tzXc5kN0SFAasM9VtVEOSMaGHLKhF+IMyVX8h5Iu IRC8u5O672r7cHS+Dtx87LjxypqNhmbf1TWyLJSoh0qYhMr+BbO7+N6zKRIZPI5b MXc8Be2pQwbSA4ZrDvSjFC9yDXmSuZTyVo6Bqi/KCUZeaXKof68oNxVYeGowNeQd g/znAgMBAAGjUzBRMB0GA1UdDgQWBBR44WtTuEKCaPPUltYEHZoyhJo+4TAfBgNV HSMEGDAWgBR44WtTuEKCaPPUltYEHZoyhJo+4TAPBgNVHRMBAf8EBTADAQH/MA0G CSqGSIb3DQEBCwUAA4ICAQBBmzCQlHxOJ6izys3TVpaze+rUkA9GejgsB2DZXIcm 4Lj/SNzQsPlZRu4S0IZV253dbE1DoWlHanw5lnXwx8iU82X7jdm/5uZOwj2NqSqT bTn0WLAC6khEKKe5bPTf18UOcwN82Le3AnkwcNAaBO5/TzFQVgnVedXr2g6rmpp9 gdedeEl9acB7xqfYfkrmijqYMm+xeG2rXaanch3HjweMDuZdT/Ub5G6oir0Kowft lA1ytjXRg+X+yWymTpF/zGLYfSodWWjMKhpzZtRJZ+9B0pWXUyY7SuCj5T5SMIAu x3NQQ46wSbHRolIlwh7zD7kBgkyLe7ByLvGFKa2Vw4PuWjqYwrRbFjb2+EKAwPu6 VTWz/QQTU8oJewGFipw94Bi61zuaPvF1qZCHgYhVojRy6KcqncX2Hx9hjfVxspBZ DrVH6uofCmd99GmVu+qizybWQTrPaubfc/a2jJIbXc2bRQjYj/qmjE3hTlmO3k7V EP6i8CLhEl+dX75aZw9StkqjdpIApYwX6XNDqVuGzfeTXXclk4N4aDPwPFM/Yo/e KnvlNlKbljWdMYkfx8r37aOHpchH34cv0Jb5Im+1H07ywnshXNfUhRazOpubJRHn bjDuBwWS1/Vwp5AJ+QHsPXhJdl3qHc1szJZVJb3VyAWvG/bWApKfFuZX18tiI4N0 EA== -----END CERTIFICATE----- </ca> <tls-crypt> -----BEGIN OpenVPN Static key V1----- 6acef03f62675b4b1bbd03e53b187727 423cea742242106cb2916a8a4c829756 3d22c7e5cef430b1103c6f66eb1fc5b3 75a672f158e2e2e936c3faa48b035a6d e17beaac23b5f03b10b868d53d03521d 8ba115059da777a60cbfd7b2c9c57472 78a15b8f6e68a3ef7fd583ec9f398c8b d4735dab40cbd1e3c62a822e97489186 c30a0b48c7c38ea32ceb056d3fa5a710 e10ccc7a0ddb363b08c3d2777a3395e1 0c0b6080f56309192ab5aacd4b45f55d a61fc77af39bd81a19218a79762c3386 2df55785075f37d8c71dc8a42097ee43 344739a0dd48d03025b0450cf1fb5e8c aeb893d9a96d1f15519bb3c4dcb40ee3 16672ea16c012664f8a9f11255518deb -----END OpenVPN Static key V1----- </tls-crypt> into the config box on the VPN page and enter the credentials of proton vpn in the appropriate boxes and see if it will connect.

Added https://forum.netduma.com/forum/144-netduma-r2-early-access/

If your download ping is that good and your jitter is that low then I doubt the upload ping will actually be that high. Testing on waveform will likely show you different results

What do you mean by a drop in performance and instability, how is this presenting exactly? How long do the connection drops last/does it recover itself or do you need to reboot? Are ALL devices connected to the R3? What are the speeds you pay for/receive? What are you getting normally through WiFi and what do you get when the issue happens? Is it affecting ALL your devices connected to WiFi or specific ones? You've mentioned only WiFi so presumably you don't have this issue over ethernet? Have you given the R3 a static/reserved IP on the BT router? Try these suggestions: Use a WiFi analyzer to find the least congested channel and change to that Experiment with the widths to see what gives better results Ensure it's in an elevated position - not on a metal surface Ensure there aren't any electrical / wireless devices e.g headphones etc within close proximity ~3 feet if possible Set the antennae to this position _ | | _

Try these suggestions: Split the bands, give 2.4/5GHz different names and apply - so you can connect specifically to 5GHz if you haven't done that already Use a WiFi analyzer to find the least congested channel and change to that Experiment with the widths to see what gives better results Ensure it's in an elevated position - not on a metal surface Ensure there aren't any electrical / wireless devices e.g headphones etc within close proximity ~3 feet if possible Set the antennae to this position _ | | _ How have you set the TIM to ensure all traffic flows to the R3? E.g R3 in its DMZ, modem/bridge mode Are ALL devices connected to the R3?

Ping Assist should be disabled when trying to force servers. Is your radius excluding the Frankfurt server? That is the primary way to prevent yourself to servers you don't want

We haven't specifically tested the game or the console as far as I am aware so we can't say for certain whether it would work. In theory if it is P2P it should work just fine but they may not appear in the correct location on the map. Can't comment on the timeout question really as we've not tried it but if they have a ping limit then it may throw an error or just not allow you into any games there. Those features don't specifically help people get into high ping games without issues.

Do let us know how you get on!

I'll make a request to the team to see if they can add it

Sorry to hear that but at least you've got a working solution and you could take your anger out and make it look better!

I've given you Early Access so you can upgrade to that version to see if it helps: https://forum.netduma.com/topic/60946-new-r3-firmware-dumaos-401147/ If not please provide a log from the router when the issue next happens Great keep us posted!

I wouldn't have thought it would affect download as well so it may be more to do with how the test is performed. You could perform a big upload and do a ping test alongside and change the percentages to see if it is actually affecting it like the test says.

I've added you both to Early Access where you can see the massive change log for the firmware also: https://forum.netduma.com/topic/60946-new-r3-firmware-dumaos-401147/ It's primarily a bug fix/stability update so I think it's quite stable based on feedback so I'd suggest upgrading to it. I haven't seen that issue so it would be good if you could upgrade and then let us know if that continues.

It would be a necessary server, usually if you're in the EU you would see one in the EU although it can from time to time be located in the US. It's possible it's mislocated also, if you ping it you could tell.

it doesn't work for everyone, we are waiting for NTGR to provide a solution

Pretty certain that's the cloud issue causing you to be unable to match with French/EU servers, however it's impossible for you to get 35ms ping to the US server so for whatever reason there is a mislocated server there that you can connect to so that one will be elsewhere in Europe, it's not actually a US server. Move it around and see if you can find a proper US server - you should be seeing at least 70ms to one.

Yeah that bufferbloat test or using PingPlotter with those reductions in percentage is a good way to fine tune it. Don't use the in built test, depending on the available servers/where they are in relation to you they can provide abnormal results.

It looks like unloaded your jitter is around 3ms so you're not going to be able to get it better than that as that's the inherent stability of your connection. So I don't really think there is much if any room for improvement there. I would suggest forcing some servers further away, although you'll get a slightly higher ping the server load may be less allowing for a more even experience.

No specific reason why it would work on one but not the other necessarily but I would suggest you return the R1 in all honesty as it is very old and hasn't received cloud updates for some time so is out of date in that regard and could be contributing to your issue

You're on the beta where there are issues getting off of it, you'll have to try this version first, if you can upgrade to it then you can upgrade from there https://forum.netduma.com/topic/60122-new-xr1000-beta-firmware-dumaos-33688-upgrading-fix/

Good to hear you got it sorted, thanks for the update!

I've given you access to the latest firmware to try to see if that helps https://forum.netduma.com/topic/60946-new-r3-firmware-dumaos-401147/ Did anything in regards to settings or setup wise change on that date? What is the model of the modem/router the R3 is connected to and how have you set that to ensure all traffic flows to the R3? E.g R3 in its DMZ, modem/bridge mode

Did you manage to upgrade successfully?