Netduma Fraser

Great to hear it's working now, thanks for the update!

HybridVPN isn't implemented yet but will likely come in the next firmware. I don't know anything about the VPN you're using but if it provides you with wireguard or OpenVPN configuration files it would work

Added

I'm sure it would be possible yes but most games do already have some sort of networking data you can enable in game, especially the esports type games so I don't know how beneficial it could be. I will add it to the list though, would definitely be a really cool addition to our portfolio.

Probably yes, they're more enterprise level so will definitely have a PPPoE option

It's not a contradiction, we get a build, it goes through testing, if it passes then it can be released, if it doesn't then fixes have to be made and it has to be built and tested again. Rinse, repeat until it's at a stable place to release.

That won't be the IP you access the repeater interface from though correct? You're still connecting from the WAN side when you're directly connected to the R3 WiFi as the repeater WAN port is connected to the R3 LAN port. I mean the devices connected to the AP, what IPs are they getting.

No there isn't as you will have deleted the router doesn't have a record of it. No specific recommendations, if you already have another router that should handle it fine.

The longer search times may be because of the season 2 update, potentially servers are more full than normal. That indicates the server has been allowed, either by us or by you, have you added it to your allow list? Are you in a game when it appears or just searching? If the latter it'll be an authentication server which is why we've allowed it as it'll be required for online play.

Could you clarify what you mean device ports but not game ports?

Maybe try the above. Generally downgrading firmware you will get a worse experience as it has less experiences. We're not giving out any ETAs on firmware anymore. Great to hear that, thanks for the update.

No it's a DumaOS 4 exclusive feature

Oh I see, well Geo-Latency is just a different method of filtering so you're essentially swapping between two filtering methods when disabling it. One or the other may work better for you. Steps 2-4 by default are already set that way.

See if this helps: https://forum.netduma.com/topic/54072-router-stops-working-no-access-to-r3/?do=findComment&comment=400311

If it's the one we are aware of then yes it would likely fix it. This "The beam i had on somehow connected to 2.4 but i had to be connected to 5 to see it within the app" is the workaround for the issue.

That can be resolved without a reset but that will fix it. It occurs when you deleted the device from the Device Manager when that device was added specifically to the feature. Without the device being connected to the router the feature is looking for a device that isn't there and errors. So either a factory reset or connecting the device back to the router again under the same conditions will get rid of the error so with the same name, device type and connection method i.e. 2.4/5GHz or via ethernet. Likely PPPoE then, if you have another router handle it instead of the XR I suspect you'll get higher speeds then.

He left before I could get an answer but I suspect he hasn't been able to do it yet, he'll get back to me on Monday

It's a test from the device and its connection method at that time so it makes sense the result would be worse. I'd stick with the settings you made when wired in as it would be better for the whole network

Expert relates to the Ping Optimizer test specifically. You'd have to re-enable SmartBOOST to adjust the Congestion Control sliders, if you're wanting full speeds then they should be at 100% but it won't combat bufferbloat set like that.

That's really strange, what phones are they exactly? Good results, well done!

If you go to the above then click system logs then at the bottom click download

What do you mean exactly? I didn't mention any features that aren't currently implemented

Try connecting it to the guest WiFi then use you phone on the normal WiFi and see if that works. Pretty sure it's the issue we know about

The connection should re-establish itself after disabling, if not then reboot and you should be good.

How is the stabilizing of the ping being weird? Geo-Latency is just a different method of filtering. Disable GeoLatency Disable PingAssist (set it to 0,0) Enable Strict Mode Disable Fast Search Then restart game or wait 10 minutes (in the lobby in the game). If that doesn't work, reboot PC/Console and it should work then. 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