Netduma Fraser

What other settings for the console specifically have you made on the router, e.g. internet rules, port forwarding, DMZ etc? Also check the IP on the console itself, then check the Device Manager on the router for the device you think it is, do the IPs match?

I'll have to pass it on to the team and wait for their conclusion I think

Delete the rule from prio, close the game and steam completely - including steam from the system tray, then make the rule again, then start up steam and the game and see if it works then. If not, does it work with DumaOS Classified Games enabled?

Added you all, you can find it here: https://forum.netduma.com/forum/153-xr1000-beta-forum/

I would generally say that if it's not broken don't fix it. If the only thing you're interested in is deleting devices then I would just take the 5 minutes you'd take to upgrade and delete the devices instead and keep the reliability you have right now. This is a beta version after all so stability may not always be possible.

You can try the above method or try to downgrade using routerlogin.net/adv_index.htm and see if it works that way

We'll have a new firmware pretty soon once the team are back from the holidays that should resolve it for good

Reboot your modem, wait 2 minutes, then reboot the R3, wait 4 minutes then check to see if you get a connection. If not, do you know if you require anything like PPPoE/VLAN/DHCP identifiers to get a connection?

I know you said you did these steps but you're not doing the PC/Console workaround so if you could just run through this so you have it setup that way and see if it's more consistent please: 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 with the manual option Set up the Geo-Filter how you like Wait 2 minutes Boot up application/game/client

Not seen any evidence to suggest they're doing this no, other games like the football games are using some relay servers but not on CoD as far as I am away. Other than the VPN thing they referenced which I think they only did due to connection I don't think they've done anything else. We'll keep an eye on it of course.

Could you try using a different browser such as Chrome/Firefox/Opera in incognito mode and see if it works then please?

It is, it's been a busy end of the holiday period and of course people have been off as well so I don't have any news yet to share

Thank you very much and Happy New Year to you too and to everyone else!

It'll be in the new firmware that'll be due soon once the team are back

I'd recommend having a look at this guide which will help you understand how the Geo-Filter works https://support.netduma.com/docs/dumaos-4/geo-filter/

There is no possibility that the router would be causing you to jump servers at all, I wonder if it will be better now in the new year as everyone will be going back to work/school shortly and so less stress on the servers

Yes it does work but also keep in mind hit detection isn't the purpose of the feature, it's to ensure all devices can use the internet without impacting each other and you can prioritize gaming/devices which will give you a better experience. Is the ping still low when using it? Experiment with how you're prioritizing it, e.g. the device itself, gaming, selecting the game, call of duty content etc

How did it make it worse exactly?

That's the thing, they were connected already, I need entries for when they connect. Just forget the WiFi network on a few devices and then connect again and then grab the log

That's a good idea, remove any potential factors and test again! I'll reply there

Don't connect the switch again Connect other devices to WiFi Get the log Post it here Then I can compare a working device log with a non working device log

Just those ports please and see if it works

Added

Not sure what you mean, so it is getting you a game and a server? Are you seeing an icon within your radius when playing?

Can you make two port forwarding rules, 3074 for one device, 3075 for the other then start up the 3074 device first, then the second and see if it happens again