Netduma Fraser

Okay so it'll be that particular server that is under load, otherwise if it was anything on your side the Geo-Filter would reflect the same spike. In that scenario add the server to the deny list and force another server.

When this happens check the Geo-Filter ping, are you seeing the same spike in latency at all?

It's less needed but I'd still advise it, you never know when an update may happen, plus you have so much bandwidth and gaming uses 1Mbps or less generally that you're not losing out by doing so.

We don't have an ETA and we're not sure yet if it will be possible to do so or not. We'll add it back so it can be used with Steady Ping/so you can ping and see servers in the meantime.

Yep Games Console - Normal (WAN)

You won't get internet until you're able to complete the setup wizard. While connected to the router via a wired Windows PC, open command prompt, type ipconfig press enter and then post a screenshot of the results here please.

They should actually show up but they may appear as offline on the Device Manager but you can still add them to Geo/SmartBOOST and they'll apply

How did you do the reset? What do you see when trying to access? Can you access via the mobile app?

Do a factory reset as it's a big change in firmware, I'm also sure this was already fixed on that version

It's not available yet. You can get an idea of what it will include from this post https://forum.netduma.com/topic/51612-new-xr700-beta-firmware-33363/

I don't think that's possible currently, it's like YouTube which we also can't block, the ads are served on the same URL as the video/stream which makes it very hard to block on the network side. It is something we're looking into to see if it is possible though.

Please do the above as a workaround, we'll be testing it on PC and put out a cloud update to rectify it as soon as we're able to.

Glad to hear that worked! How often is it happening exactly? What firmware version are you on currently?

Check the IP on the PC itself and then check the device you think it is on the Device Manager, do the IPs match? How have you added the device to the Geo-Filter?

Disable that option and add your device manually to Traffic Prioritization and see if you get a better experience that way.

Cancel it, reboot the router, wait 4 minutes before accessing then try again

Not everyone gets the option to upgrade right away, it's a slow rollout to ensure there are no major issues that could take down the entire customer base. Let us know how you get on.

You're very welcome, have a great weekend!

Your radius is way too big, if you want that low ping you'll have to reduce it to cover the servers that you know you can ping low to. You can use Ping Heatmap to ping the game and find where these servers are then change your Geo settings, once you've done this restart the device/game and you should get lower ping servers then.

Do you need to use Option 61on the R3 in that scenario though, is that why you can't connect?

Two options really, you can do ports: Source 1 - 65535 Destination 1 - 65535 TCP/UDP which will prioritize the entire device. Second option is changing the phone to a PlayStation in the Device Manager, then you can add it with the Games Console service which will essentially prioritize the entire device apart from general web traffic.

There is a more up to date firmware you can be on: https://forum.netduma.com/topic/56107-new-r3-firmware-40236/ but also: Disable GeoLatency Disable PingAssist (set it to 0,0) Enable Strict Mode Disable Fast Search Use Simple instead of Custom radius 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.

In Settings > Accessibility you've enabled the option to convert charts to tables, that's why it's appearing written out. Disable that and it'll go back to normal.

Remove the device from the Geo then re-add it please and see if it appears again. If you have a browser based Adblocker, disable it/whitelist the interface and make sure you're connecting to the interface via HTTP rather than HTTPS.

Great to hear that, thanks for the update!