Netduma Fraser

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.

In DHCP Advanced change the DHCP lease time to 10000 reboot from the interface and then see if it happens again please

Congestion Control, turn both percentages sliders to 100%

The QoS you're looking for is in Ping Optimizer > Advanced The Geo-Filter shows you active connections and therefore you will only see the server you're connected to at the time - you will not see servers like how Ping Heatmap shows you. Disable Geo-Latency in the Geo-Filter settings and that should stop you connecting further away.

If you can't get internet through the R3 without PPPoE being set on it then what you've done is fine

I don't think its in bridge mode, take a picture of the page you enabled that please but yes leave those settings as they are

I don't know, I would reach out to your place of purchase for more information or contact Netgear support directly. I don't think they would do any maintenance though, it would be a replacement if they were to do something

Just because the ports are intact doesn't mean they can't be faulty. As I've mentioned, those are the only causes, there is nothing else that could cause that to happen. The XR is not picking up connection information from the modem, this could be the XR or the modems fault. If you've checked with another modem then it will be the internet port on the XR that is faulty. There is nothing that can be done via software to fix it if that is the case.

If you switch the modem to bridge mode then DHCP, UPnP & Firewalls do not need to be disabled on the modem. Either it's not properly set in bridge mode if it's allowing you to change those settings or you can just leave them enabled - the R3 doesn't have a bridge mode for example so whatever you thought you did to set that isn't the case so double check the modem is actually set to bridge/modem mode. I would still remove the cloned MAC address change.

I didn't confirm it was a problem on our end, I said it could be faulty hardware which just being the software partner of NTGR we wouldn't be able to do anything about. I do understand the problem, the only potential causes are: Faulty ethernet cable connecting the XR to the modem Ethernet cable not plugged into the correct ports (should be XR internet/WAN port to modem LAN port) Faulty LAN port on modem Faulty WAN port on XR Static being selected on XR for Internet Setup instead of automatic DHCP being disabled on the modem All of which I feel we have covered except maybe DHCP having been disabled on the modem. I think the last attempt should be double check everything is plugged in correctly and everything I've mentioned is set correctly and then lastly if needed to factory reset your modem, wait a few minutes, factory reset the XR, wait 4 minutes then complete the setup wizard and see if you get internet. If it's not working after that then it's likely faulty ports and not something we can help with

See if you can access this page: http://192.168.77.1/dumaweb#!/support to re-upgrade the firmware and see if it works better then.

Don't rely on the in-built router speedtest. For a variety of reasons this can report incorrectly. Do a speedtest.net test with a wired PC if possible, what do you get? Ping Heatmap pings all servers the game has, that's its only purpose. The Geo-Filter shows you active connections and therefore you will only see the server you're connected to at the time. Fortnite is a weird one as it only tries to connect you to a server when it's actually loading you in to the pre-game run around lobby area & so that's the only time the router can block it which may result in a longer wait to get returned to the game search lobby. It may be faster to toggle filtering mode off, search, wait to see where it shows on the map/what it pings & then quit if needed and re-search until you get the server you want. Yes when you add your device to the Geo-Filter you select the game I would suggest overall that when using a PC, delete it from the Geo-Filter, go to the Device Manager, click your PC and change the device type to a PlayStation. Go back to the Geo-Filter and re-add the PC, it should add as a console instead. This will mean you can filter different games without switching it all the time. It will allow you to filter games not listed (if those games can be filterable) and is overall more likely to work consistently in my opinion.