Netduma Fraser

What firmware version are you on? Did this only start happening recently? Could you resync the cloud and then provide the logs please from the System Information page? If you click okay on the error can you then use the Geo-Filter as normal or does it re-appear?

Maybe I'm not understanding, you're saying it's a problem but it's normal for the downstream devices to have access to the upstream router - what is it exactly you're wanting to achieve/your usecase?

I've given you Early Access which should help, try the firmware there please: https://forum.netduma.com/forum/151-netduma-r3-early-access/ slower speeds on PPPoE is something we're looking at but should be a bit better on that version. How is the Geo-Filter working badly exactly?

I can't determine the cause just from that picture, it could be a few things: GeoLatency being enabled PingAssist being enabled Strict Mode being disabled Fast search being enabled Could also be changing Geo-Filter settings while you were on the game and then not rebooting the game before searching again - this will be why you denying it didn't work as the connection was still partially active when searching, the connection needs to be severed fully before it is then blocked. It's very unlikely we would have added that server to the whitelist.

If you're changing settings while you're on the game that will be why it's not working very well, it's best to set it up before you load up the game - if you really want to change it during then once you've made a change restart the game and then it should apply the new settings.

I've given you Early Access, please the firmware there and see if it helps: https://forum.netduma.com/forum/151-netduma-r3-early-access/ Added - if you could change your username as well I'd really appreciate it!

They use relays, it's a difficult one to counteract and may not be possible. In the meantime I've given you Early Access where using the Geo-Latency feature may help a little with filtering https://forum.netduma.com/forum/144-netduma-r2-early-access/

No, that is not possible. You can only force the server you play on.

Try accessing using 192.168.77.1 in the browser instead, can you gain access that way?

The last image is fine, you just need to access using 10.0.0.1 Where are you seeing the error, on what page? Does it happen when you load the page or when clicking a setting etc?

Not the R2, what is the modem the R2 is connected to? What about the other questions?

Any VPN configuration files you'll need to get from the VPN provider, then just replace the existing one in the router with that one

We'll look into the RGB issue, thank you for letting us know your experience with it. You can only force the servers that you play on. You cannot determine where the other players are from or who connects to the servers. There is no possible way to do that on a server based game. It would have to be a game side change that forced people to play within their own country/region.

It's difficult to see a clip and know what the cause is: 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 Are ALL devices connected to the R3? What are the speeds you pay for/receive? How have you setup Congestion Control? How have you setup SmartBOOST? How is the console connected, via ethernet or WiFi? How have you setup the Geo-Filter?

You already have access, click the link: https://forum.netduma.com/forum/151-netduma-r3-early-access/

Not sure if it works though it would be good to test - it would be the easiest way - make an Adblocker rule for a domain and put in http://www.asusrouter.com does that work?

Sorry to hear you're having this issue, I've given you Early Access so you can try the firmware there which should help to relieve this issue. Do keep in mind this is a support forum so you'll only see people who have issues generally posting here. Do let us know if trying that firmware helps. https://forum.netduma.com/forum/151-netduma-r3-early-access/

Added

Great to hear that, thanks for the update!

Please try the .402 firmware in Early Access as I think it was solved with that one

We'd had a small amount of people have this issue, did you change the RGB settings frequently? What was the last thing you did with it prior to it stopping working?

We are testing the game so will add it as soon as we can

Just to clarify, does the RGB turn on then but not right away after a reboot, setting change, playing a game etc?

I've given you Early Access, please try the firmware there and see if that helps

Being a game side implementation you can try as much as you want but it's very unlikely you'll be able to circumvent it. I imagine they're slowly rolling it out/testing it here and there so you may have some success occasionally - I would suspect that with the holidays just around the corner that they're not going to do something big like that until the rush has died down.