Netduma Fraser

Cover Japan in addition to where you want servers and try again

Do this: Quit the application/game/client completely Remove device from the Geo-Filter Give PC PlayStation Device Type in the Device Manager Resync from the Geo-Filter Map menu Re-add the device to the Geo-Filter Set up the Geo-Filter how you like Wait 2 minutes Boot up application/game/client

I'm saying there is no specific cause from the router for why that would happen if no settings are different - they are trying to counter act VPNs though which may have something to do with it. You're more likely to be able to force the US with the Geo-Filter than with the VPN

There is no router specific reason for it if you've made no different settings between the two devices on the router, likely down to just using a VPN, especially over the weekend

Have you got any other WiFi 6 devices you can use to test with? Set the mode for 5GHz to 2400Mbps I think it is, then see if you get better results then

As above, it is normal, your connection quality is not going to improve with a VPN, in 90% of cases it will be worse.

I suspect it's more like it's not reporting it and then it's reporting all the traffic at once.

The internet provider won't affect the Geo-Filter in that way, are you covering Japan as well as that may be needed as they use relay servers.

It's not a different cloud system so that's good, I think it should be next week

Disable Geo-Latency & Ping Assist from the Geo-Filter settings, reboot the PC, then try again please

Try these suggestions: Disable Smart Connect, give 2.4/5GHz different names and apply - you'll want to connect to 5GHz specifically for speeds Use a WiFi analyzer to find the least congested channel and change to that 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 _ | | _

I can't see the first video, could you upload it again? If it's not speedtest.net could you provide a video of it happening there also please? Do you see the same behavior when downloading a game for example?

Fair enough, at least that's something, I'll see if the team can look into it.

What about using PingPlotter guide though rather than the website? What about in game are you seeing these results reflected there?

Really glad to hear you found the solution, thanks for the update, no worries at all, any questions/issues just let us know. Have a great weekend!

Previously did you have the R3 in the DMZ on the Plusnet? Have you got any devices in the DMZ on the R3 or made any custom rules like in Internet Rules etc? I've given you Early Access to see if that improves it for you: https://forum.netduma.com/topic/58424-new-r3-firmware-dumaos-40645/

With what I've mentioned no it won't make your performance any worse, as long as you keep all devices connected to the XR.

So with your expected speeds set you can't eliminate it just by reducing Congestion Control?

Okay so it's on the R3 and should go out to the R2 next week, sorry about that but it at least we've finally got it on there

Take the Huawei out of bridge mode and remove PPPoE from the XR and have the Huawei handle it instead. Put the WAN IP from the XR System Information page into the DMZ on the Huawei instead. With the XR handling PPPoE QoS won't be working correctly so this should help with the issues you're having. Having a static IP doesn't effect your connection quality. Try what I mentioned and see if it helps.

It's just a router but it does have PPPoE & VLAN so you should be able to do it. Set your speeds manually and adjust Congestion Control manually instead of relying on the test which isn't 100% reliable at the moment.

SmartBOOST is set how exactly? It's not an on/off scenario 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

That was awhile ago right unless they've said something more recently? I thought it was working a bit better now especially with Geo-Latency?

Okay interesting, thanks for letting us know, I've only heard of a couple instances since the R3 launch so perhaps a bad batch from the manufacturer

He'll be looking into it more tomorrow I believe