Netduma Fraser

What is the model of the modem/router the XR is connected to and how have you set that to ensure all traffic flows to the XR? E.g. XR in its DMZ, modem/bridge mode

Do you have all the ports the game uses added? I don't think those specific ones will open the NAT. Have you checked the NAT status without the Geo-Filter enabled? The Geo can sometimes cause a misreading - disable, reboot the game then check.

Good to hear, keep us posted

It automatically does this

Yes like that but the IP address is incorrect - it should be the IP that it assigns the R2 - check the device section on the movistar to find out what it is

Added

I'm not asking you to do anything on the router itself: Set a reserved IP for the router on the Movistar Do you have another power adapter you can try with

That's fine but you can access the movistar interface even when connected behind the R2 by going to it's LAN IP. There you set the static IP for the R2 - you don't need access to the interface for this. Do you have another power cable you can use with the R2 - it is probably a power issue. Can you get the logs from that link now? Disable the Geo and see if you still get that message.

Click the little arrow and then you can select English again. It is experimental but you do have the option to help with correcting any bad translations you see - we'd really appreciate it! I tried to reproduce that in Portuguese but couldn't so it won't be a translation specific issue - clear your browser cache then reload the page

No nothing to do with that - what have you done settings wise/with the console prior to it not working? Doesn't have to be specifically you changed a setting but just run me through e.g. turned on, turned off (standby) etc

If you have an ISP router (that has WiFi, not a pure modem - no WiFi) then you do so on there, you'd be setting a local reserved IP address for the R2 - not a static public IP which you would normally pay for. Do you have another power adapter you can try with?

Thanks for letting us know - you can just switch it back to English the way you changed it to Portuguese - changing the language won't make the feature not work, it's just not able to apply to every server

When I have some more information to provide I will let you know

No not that I am aware of

Can you set a static/reserved WAN for the R2 on the ISP router? Do you have it connected to a power extender or direct to an outlet? If an extender please try direct to an outlet. Otherwise do you have another power adapter you could try with?

It is a QoS feature so yes that would be the case for the prioritization SmartBOOST applies anyway. If it's an Xbox you're playing on QoS wouldn't need to be on to pass on those tags.

I've given you Early Access, please try that and see if it works better https://forum.netduma.com/forum/151-netduma-r3-early-access/

Continue playing the game using that router for a few days through until Monday and see if you get the same experience the whole time. What is your general physical setup?

Are you saying that it just does the one test rather than test, use percentage, test, different percentage etc?

It really depends, there is no set timeframe. It is possible we're not classifying traffic originating from DumaOS itself i.e. HVPN traffic isn't classified as OVPN

Added https://forum.netduma.com/forum/151-netduma-r3-early-access/

He thinks it could actually be because you're not on the beta so could you go ahead and upgrade to that and see if it appears please?

I've just updated the top part, replace that in your config and see if it works better please: client dev tun proto tcp remote us-sea.prod.surfshark.com 1443 nobind tun-mtu 1500 mssfix 1450 ping 15 ping-restart 0 reneg-sec 0 remote-cert-tls server auth-user-pass #comp-lzo verb 3 fast-io cipher AES-256-CBC auth SHA512

The only thing I can recall which might affect it is whether you're using TAP or TUN - I can't remember which one it is but at least for iOS it wouldn't work on one but would on the other so try both methods and see if you can get one to connect. I feel like it might be TAP that worked most reliably.

We know why that's happening, it should be fixed in the next version, I've PM'd you for logs.