Netduma Fraser

Do this:
Quit the application/game/client completely - including the game client from the System Tray - important! Remove device from the Geo-Filter If you're on PC then give it the 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 To force servers you need to do the following:
It's essential the Geo-Filter is enabled before the game client (e.g. Steam etc) if on PC or platform (e.g. Xbox, PlayStation) or the game have been launched. If you change Geo-Filter settings when you're on the game then you will need to restart the game for those changes to take effect, otherwise it will use the previous Geo-Filter settings and appear not to be working.
For settings ensure Ping Assist and Geo-Latency are disabled in the Geo-Filter menu that can be found by clicking ⋮ in the top right hand corner of the page and go to Settings.
Strict Mode should also be enabled, it is enabled by default so if you haven't disabled it you can ignore it. If you have disabled it or want to check it can be found in the same Settings menu as above or in Settings > Troubleshooting > Advanced > Developer Options depending on your firmware version. Fast Search should also be disabled which it is by default so can be ignored if you haven't changed it, otherwise this can be found in the same place.

Okay so you don't need it. Correct, you have a very good ping so the game doesn't need to do anything to compensate

nope geo filter on .1147 does not filter out fraser  but im still trying different
setting will let you know what works 

Awesome. All sorted and back on track. 
Any issues i'll get back to you.
Many thanks guys.

I've mentioned it a few times but we've been working on some big features which has caused delays with updates and not just for the R2. When the R2 was released it came with DumaOS 3, we never indicated at the time that meant it would get full compatibility with the next iteration of DumaOS but we're doing our best to give you what we can of it considering DumaOS 4 was developed on the R3 and the R2 hardware is significantly less powerful than the R3. I understand it's frustrating but it's likely the next update for the R2 will be the last so we need to ensure we get it right. NTGR mark their routers as End of Service when they feel the need to do so, there is nothing we can do about that unfortunately and we don't get 100% of those routers cost to continue development like we do with our own.

We don't have any servers that would appear on the Geo-Filter/block you from playing, it's an authentication server for the game, you've done the right thing to allow you to play and we'll take the ID and add it to our whitelist. They change/update their servers frequently so sometimes this happens.

Yes that's correct, thank you and you!

Up to you, but If all devices are sitting behind the R3...
You could remove the BT Smart Hub from the equation i.e. WAN line directly into the R3 and pop in the PPPoE creds. That's what I do with my BT/EE connection. 
See what works better for you hit reg wise (i.e. BT homehub handling the WAN or the R3)
 

For the older games they do tend to start reducing the amount of servers available so that's likely what is happening here. If the Geo-Filter doesn't see them then they're not actively available unfortunately

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

Obrigado 

Thank you all for the support.
I just wanted to share what finally fixed the speed issue for me.
I removed the cloned MAC address (I had previously entered the Huawei router’s MAC) and re‑entered the original Netduma R3 MAC address in WAN > Advanced.
After a reboot, my speeds immediately returned to 350–400 Mbps.
Everything is working perfectly now.
 
Thanks again to everyone who helped!

Thanks @Netduma Fraser

Thanks and you!

Thanks Hope u have a Good Day.

Thanks for the update! So if like you said the fritzbox doesn't arrive by the time the service goes live and you want to connect the R3 up (presumably to an ONT?) then you'll need to use PPPoE. If you want to use the fritzbox and connect the R3 to that then the expose host option is essentially the DMZ which would mean that the fritz handles PPPoE and the R3 doesn't, it will just ensure you don't get any NAT issues using the two together. Pretty straightforward for the exposed host option, just entering the R3 IP or MAC address as far as I am aware but any issues with any of it do let us know!

The interface does not work properly with https, however, it's a local address, inaccessible from the internet (unless you enable the option to make it accessible) and so https isn't needed

No worries, that's exactly what this kind of support is for so you can answer when it is convenient for you, we'll keep answering if you do. What do you mean by "picture of the speed test run from my cellphone, after being able to get online via Ethernet port, but not via WiFi" are you saying you have an ethernet adapter for your phone that you were using?
The firmware doesn't go back if you factory reset, it will stay on the one you're on but you won't be able to miss that you've factory reset correctly if you see the setup wizard instead of the normal interface. Okay keep us posted!

Added

Thanks for the comments, I'll pass them on the team for when this is considered

General errors like that I don't always trust because all it's really telling you is it wasn't able to connect and there could be another reason for it BUT If you're getting a DNS issue then that is a problem, basically DNS is what turns a URL for example netduma.com into the IP address that you use to connect to that website. So if that's not working properly then it means that entering google.com into your web browser for example it wouldn't know what IP to connect to/access to then display the correct information back to you. If that is the case the ISP should be able to sort it quite easily, either from a new modem (if this is the issue then wiring is less likely and now more likely the modem) or something they can sort remotely. 
I understand your frustration on that, they have their script they have to go through and they will go through it regardless of what you say. Your best bet is to go through the motions, tell them the issue, do/feign doing if you've done their suggestions before (make sure to leave enough time in between so they can be certain you've done it) and let them go through all the steps they're required to ask you. If they can't fix it with those basic suggestions which is likely then they will either want to send a tech out which as you've mentioned isn't viable, hopefully explaining that they will (or ask to be) escalate(d) to a tier 2 or 3 tech. They will have more knowledge and should hopefully provide more targeted support/be able to identify the cause and solution. Also absolutely do not mention another router - it's vital you're clear that this issue is experienced when directly connected via ethernet from your PC to their modem - not saying they will but some may use that as the excuse to get you off the call if they don't know what the problem is. 
Good luck, I hope you can get it sorted and would be interested to hear an update on how you get on!

That's great to hear, thanks for the update! I would suggest staying on your current version as I cannot guarantee the kind of stability for your issue that you're looking for on that version at the moment.

We don't give out any ETAs but if we were to release .645 publicly it would be using the exact same version of the firmware you're on now. If we made any changes to it we'd release it with a new firmware number.

You don't need PPPoE to connect the router to their ONT, you can just connect them and it should work unless they've specifically put measures in place to ensure you use their router connected to the ONT. You can just connect the R3 to their router otherwise.

@JOSHR3ll try this command as one command please instead:
await duma.RPCHandler.PostRPC({rapp:"com.netdumasoftware.config",method:"set_web_setup_done",params:[true]});
await duma.RPCHandler.PostRPC({rapp:"com.netdumasoftware.config",method:"set_setup_done",params:[true]});