Netduma Fraser

Ah, I remember. If you don't reply to the topic after a suggestion we don't know whether you're still having issues or not, if you reply there then we can continue troubleshooting

It may take a few days for the spikes to settle but that's a good start! We're still improving the Benchmark results on the XR routers so I wouldn't worry too much about that currently and go on feel or use PingPlotter, saturate your connection with downloads/streams etc and experiment with CC % to see what brings the ping down as much as possible.

It has been awhile since new firmware has been available, shouldn't be much longer before another version is released. Apart from the UPnP issue which is more visual there hasn't been many recurring themes from what I can see. If you're having an issue please make a topic and we'll be happy to help.

Can you provide a screenshot of the QoS page as you have it set currently please?

Okay might be fixed in a non released version then as I know it has been fixed, in the meantime I would advise you look up the channel/WiFi requirements for the US and choose a region that has those same requirements

What firmware version are you on currently? I believe this was fixed in the latest .394

Can you provide a screenshot of a completed Benchmark test please and a screenshot of the QoS page as you have it set currently

They are support forums so you will only see people having issues so that can give a false sense that there are only issues but there are many people not posting because they don't have said issues

I think that's a good idea, the baseline is quite spikey so once that is resolved your overall performance should improve. In WAN Settings change NAT to Open and see if that resolves the issue with the cameras

Did you enable the option on guest WiFi for the devices to be able to interact with your network? Under what conditions were the PingPlotter tests done?

I think a good test to see if it is your settings is to play during off peak times when the servers are generally under less load then play with and without and see what the experience is like.

Great to hear that and thank you for the update!

That is all that is needed thank you, Liam will have to connect on Tuesday now, no need to do anything on your side or be by the router

Did you do the PingPlotter test again with the new modem? Try making a guest 2.4GHz just for the smart devices and see if they're able to connect to that

That's port forwarding, follow the specific steps here: https://forum.netduma.com/topic/38675-hybrid-vpn-for-warzone-no-longer-connecting-via-open-vpn/?do=findComment&comment=332646

From the screenshot put the source ports in start and end and then do the same for the destination as well

Now you have access again, try this again: While connected via ethernet, disable WiFi entirely, reboot the router from the interface, wait 2 minutes, access, enable WiFi, change the channel, apply, reboot from the interface, wait 2 minutes then see if it's more stable from then on. Also, set reserved IPs for all devices between .2 - .99 and then reboot from the interface and wait 2 minutes

I would suggest so yes as there is no need to prioritize twice

All servers appear to be pinging correctly so I don't believe so - have new servers been brought online/offline that we need to check for?

Yes that would be 6 rules but you will likely not need the 88 or 500 rule. If you're playing over WiFi then Gaming/Voice, if playing over ethernet pick Normal - regardless I would suggest enabling Apply to WAN as if your ISP supports priority tags you may have an improved performance. No need to reboot, they will work when the console goes on. It is quite possible that not all the rules will appear to be used - it depends specifically on what they use during a game and what may be used occassionally.

If you're trying to do solo games in Destiny then it won't work and that isn't the purpose of the Geo-Filter. Battlefield it somewhat works but due to their matchmaking design the Geo-Filter doesn't historically work well with many of the BF games. We haven't specifically tested Warframe so I couldn't comment on that one. Can you provide a screenshot of your Geo-Filter page please?

12-20ms isn't too bad really but that would be down to the ISP most likely. Do try with saturating the network and trying different percentages to get the graph down as much as possible and you should notice a difference.

So nothing was saturating the network at all? I can't see the values exactly but it doesn't look too bad as a baseline

Hey, welcome to the forum! We haven't specifically tested the game as far as I'm aware but it should work so yes in theory you would be able to force that server. Yes you can enable/disable the Geo-Filter very easily.

Yes it has the same outcome regardless. You can disable Strict Mode to disable filtering but if a server is misclassified as a peer you may still get the error every so often. Otherwise just disabling the Geo-Filter the main way under the device can be done.