Netduma Fraser

I believe if you go back to the beta you should see it has updated, this is because it needs 3.3 for the updated cloud system. The beta update will actually be more up to date than that version even though it appears otherwise

Using it as games console should definitely work, if that's not the case then check the IP on the PC itself from network settings then on the Device Manager on the router check the device you think it is, do the IPs match? If not find the one that does, re-name it and then add that to Traffic Prioritization.

Glad to hear that, have you followed the guide?

You posted about this previously, It provides a fixed route to determine where traffic is sent to. It is primarily a feature that is used in commercial/enterprise environments. You will not need this I can assure you, it is not a feature to be used for improving your gaming experience, it's just a standard router feature.

Have you got Geo-Latency and Ping Assist disabled? If not do that and then try again after rebooting the game/client

You shouldn't have been able to do that really so it is a bug, quickest solution is a factory reset but if you don't want to start fresh there is a workaround here that someone posted: https://forum.netduma.com/topic/55901-netduma-r3-server-line/#findComment-415394

The new ISP modem/router should have come with a card or guide to let you know how to access but if not there should be a sticker on the underside with the info. Otherwise you'll have to lookup the model to find out. Modem/bridge/passthrough are options you're looking for, alternatively you can put the XR WAN IP in its DMZ to achieve a similar effect.

Disable Ping Assist, you're essentially allowing any servers up to 70ms regardless of where they are

eFootball is a weird one where they use relay servers to connect you to the game server. For example, you cover an area, it'll connect to a server within that area to then connect you to a game server outside that location. Apparently covering Japan as well can make it so it adheres more to your radius. However, it actually appears as though you don't have filtering mode enabled on your Geo-Filter or you've enabled it after loading up the game as everything appears to be connectable. Make sure you have it enabled, have it all set before you launch the client/game, disable Geo-Latency in Geo-Filter settings also, cover Japan as well as the area you want and see if it improves.

The ISP/MAC thing I mentioned is a legitimate thing and can result in reduced speeds over a few days/weeks, it wouldn't be an R3 specific issue. However, in this circumstance it's actually due to PPPoE, I've given you Early Access: https://forum.netduma.com/forum/151-netduma-r3-early-access so you can upgrade to the firmware there which may help to improve the speeds in the meantime while we look to improve the speeds ourselves through firmware related changes. Otherwise the solution would be to have another router handle PPPoE instead of the R3 in the meantime.

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? In some cases it can take time for new routers to achieve full speeds with some ISPs. If that is the case then if you copy the MAC address of your previous Asus router and set the R3 to use that MAC address instead. Give it a reboot, wait 4 minutes then it could restore your speeds.

I know, I'm just saying that would explain the BF6 hit reg. For the Geo-Filter: 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 Set up the Geo-Filter how you like Wait 2 minutes Boot up application/game/client It should work better then. Do follow the guide to optimize Congestion Control, it is much better than an online bufferbloat test, once you get good results using the guide provided you don't need to worry about the online tests as bufferbloat will not be an issue.

Glad to hear you got it sorted, thanks for the update with your solution

Great to hear that! If it were to happen again it should occur a week after you changed it

Most of the time hit registration isn't related to your ping necessarily but to how busy the server is which can then increase the processing delay for you. With BF6 you're likely to see that during the beta just with how many people are playing it and slamming the servers. Though in most cases the best thing to do is to try to force a different server even if it is slightly further away, it may have a higher ping but may be more stable. 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.