Netduma Fraser

No worries! Yes absolutely, they're essentially VPNs and they create encrypted tunnels between you and the destination so the router won't be able to tell properly what it is connecting to. Is that something you're using?

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

Doesn't detect or aren't getting internet? Can you provide a screenshot of the LAN settings page please?

Sorry a bit of a long one but hopefully this gives you a good oversight and will help in figuring out what is happening. Allowing or denying could have impacts on your ability to filter if you allow/deny the wrong ones. Everyday filtering you don't need to add any servers to allow/deny except in these possible scenarios: Allow: Adding friends Adding servers that had a good connection that you may like to play on in the future - it won't necessarily make you connect to it more but if your radius would ordinarily block it then you could still connect Adding servers you suspect are authentication/required servers i.e. servers that appear blocked when running a console speedtest, servers that appear blocked when you're unable to sign into a game etc Deny: Blocking servers that have given you a bad connection - this will prevent you connecting to it again but remember there are multiple servers clustered in a singular location so it can appear as though you're connecting to the same place but it will be a different server in that location. So in these scenarios, if you were to allow a server that's outside your radius you could connect to it regardless of your settings, that might go against what you're trying to achieve. If you've denied a server that was actually an authentication/required server then this may prevent you playing at all or playing in a specific region. There is a possibility as well that if you've denied/allowed the wrong server that the game could relay you to a server outside your radius that would normally be blocked - this isn't something I've seen for CoD though. If you're blanket allowing anything in your radius and denying anything outside your radius that's not the best way to do it and could definitely lead to issues - anything inside will be allowed and anything outside will be blocked anyway, just temporarily. The only authentication servers I am aware of for CoD are in Ireland and Washington so I don't think the Amsterdam server is one. From your screenshot you've manually allowed a server in Ireland - an authentication server - that is correct. There are two other servers, the server you're playing on and then one that is allowed in France - not one that has been added to the allow list though. So what that tells me given that I can't see where you've placed your filter is that very likely one of the following things have happened: Geo-Latency or Ping Assist are enabled or Strict Mode is disabled The Geo-Filter wasn't enabled prior to turning on the console/game The Geo-Filter radius/settings were changed while already on the game but the game/device wasn't restarted after doing so, therefore it still thinks you can connect to the servers you were able to before Filtering isn't enabled You have set an Internet Rule to allow ALL traffic to the device thereby bypassing the Geo-Filter restrictions After looking up the ID of this Amsterdam server I can see it belongs to Cloudflare and as far as I am aware they don't use this for the gaming or authentication servers so I'm wondering if you've changed your DNS manually to 1.1.1.1 / 1.0.0.1 and the Geo-Filter is picking it up, hence why it's always showing as being connected, in which case it's more likely that server in France is the game server in your screenshot but the other aspects would still apply anyway. If you have allowed/denied something you haven't/have been blanket allowing/denying then a good thing to do if you want to of course would be to remove all the servers you've allowed/denied and see if the issue still occurs. Last but not least I've given you access to the Early Access firmware which is a big one for fixes/QOL changes including some made to the Geo-Filter so if it is caused by an actual firmware issue (which I think is unlikely) then it would probably be fixed by this version: https://forum.netduma.com/topic/60946-new-r3-firmware-dumaos-401147/

They said they'd look into it but we've not got anything back as of yet, we'll chase them, sorry for the delay!

Are you using the original power supply for the router? Is it connected to an extension or direct to an outlet? If an extension please try direct to an outlet.

In a previous topic you mentioned you had fixed it, have you been allowing/denying more servers since that point?

Set the LEDs to disabled, reboot the router from the interface, wait 4 minutes, enabled the LEDs, reboot the router from the interface, wait 4 minutes then see if it works please

I don't have an ETA on it but it will update automatically when done

What do you mean the netgear page? It should take you to the interface. I see you've got Adblocker enabled in your browser please disable it and try accessing again

The issue is they're updating it frequently at the moment so it's getting out of date really quickly. We will update it again. You can still use the Geo-Filter to force the servers you know give you the best ping.

It's not possible for you to SSH into the router. Can you access via routerlogin.net?

You can use code GAMEON10 for 10% off

Upgrade to this version please and see if it continues https://forum.netduma.com/topic/60946-new-r3-firmware-dumaos-401147/

People focus too much on that test IMO, it's not a definitive indicator that you'll have great games. Did you try forcing different servers to see if they play any better?

Added

If you've just tried in 10% increments from 100% try in 10% increments from 95% as you might find a higher value that works better but ultimately every connection is different and so there isn't a definitive guide to what percentage works best. Some people like to really heavily throttle to 10% for example. People do tend to heavily focus on the results of that test as a mark of how good their connection is but I'd suggest going with what you feel when playing, if 50% gets good test scores but it's miserable to play on then it's not worth it. Alternatively this is what I'd suggest doing if you have the time to really experiment: Follow this guide https://support.netduma.com/frequently-asked-questions/legacyfaqs/test-your-ping/ while downloading & start with 95% for Congestion Control (set to Always), check results, decrease by 10%, check, decrease by 10% etc, until you get to a value that is pretty good & then try 5% either side of that value to see if it can be improved. Download & Upload on Congestion Control don't have to be the same value & you may have a better experience with differing values.

I think that's the best you're going to get it seems - the difference between fully disabled/on in terms of the available router resources appears to be impacting the available speed, given nothing else has changed this will be unavoidable I think. You may get different results depending on the time of day but otherwise I think that's what you're left with. The bufferbloat will have increased as although QoS is on it's not actually active until you lower the Congestion Control percentages/set it to Always or Auto (will only trigger when Traffic Prioritization is triggered). So to have the most available speed set CC to Auto, setup any Traffic Prio rules and when they trigger CC will trigger with whatever percentage you set, otherwise you'll get 'full' speeds like what you're currently receiving with it set as it is now.

Okay so speedtest.net results look like they're where they should be so that's good. Now re-enable QoS, keep Congestion Control at 100% & Never. Reset bandwidth allocation - click the button anyway even if its equal. Ensure share excess is enabled for Bandwidth Allocation in its menu (it is by default). Ensure you don't have any manual rules added to Traffic Prioritization. Then do speedtest.net again, what speeds do you get?

Its like the normal filtering, servers inside your radius are allowed, outside are blocked but it just does it using a different approach. It can also help to prevent any cases where on games where the game ends and you can just stay in while it puts you into another sometimes you can get kicked to the lobby if it would be outside your radius usually but instead it would keep you in. So sometimes you can get games outside your radius if the game is persistent in wanting to put you in it.

Well that's great to hear! Do keep us updated!

The only other thing I can think of that you may or may not be using is Armor, if you have it enabled then disable it please. Also no devices have been connected back to the V Hub now its out of modem mode right? As that would negatively impact the speeds through the XR.

Hi.... So I did everything. I connected everything to the Netduma R3. I solved the streaming problem; previously I couldn't watch movies in 4K. I set the TV to 4-star property with generic web application and maximum priority with 5 stars to the console. I connected with the console and when I go into the geo filter to see the ping for the game eFootball it always gives me 61 / 67 ms (Paris or Frankfurt server). If I instead set the game to FIFA 25 on the ping map screen, I can see servers with 56 ms (always Frankfurt or Milan). But can I choose a different server than the one for eFootball, considering that the ping is lower? Thanks for the reply. Great to hear that! They're not the same servers so your routing to them may be different even being in the same location or they may be setup differently, be under less load etc which allows you to ping better to them. So it doesn't matter if one game shows you a better ping than another, you'll only be able to get the ping you get to the servers the game you play provides. Did you connect the console direct to the TP Link to check the ping you're seeing in game so we can get a baseline of what is possible?

Upgrade to this version please and see if it continues https://forum.netduma.com/topic/60946-new-r3-firmware-dumaos-401147/

Just to double check, are you doing all these tests via WiFi? What are you getting via ethernet?