Netduma Fraser

Steady Ping won't always be able to stabilize a game, we're working on a new ping method which may be able to help increase the consistency. The tighter you restrict the longer it will take you to get games so do consider encompassing a few servers within your radius and the speed of getting games should be much faster.

I believe in older firmware versions it did apply to other things as well but on newer firmwares it should just apply when gaming/when you're connected to a game server

That message means you've already added the same device with another service and the contents of those services are conflicting with each other. Try this: Quit the application/game/client completely Remove device from the Geo-Filter Give PC PlayStation Device Type in the Device Manager (if on PC) 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 Then see if it works better. What is the model of the modem/router the XR is connected to and how have you set that to ensure all traffic flows to the XR? E.g. XR in its DMZ, modem/bridge mode How have you setup QoS?

Added

You already have access https://forum.netduma.com/forum/144-netduma-r2-early-access/

Try it just with your ISP router for awhile, do the same tests you'd normally do when you'd normally do them and see how it performs, if you notice those speed issues still

Bufferbloat is caused by your network being saturated which is more prevalent when other devices are being used - if you yourself were just gaming there wouldn't be any bufferbloat. 1 download though for example can saturate your network and cause bufferbloat. Do let us know how you get on

Are your speeds usually up and down a lot? I.e. does the connection generally appear to be unstable rather than consistent?

While connected to the router via a wired Windows PC, open command prompt, type ipconfig press enter and then post a screenshot of the results here please. Holding the reset button in the back of the router for 30 seconds, then wait 4 minutes before accessing the interface

What game are you playing? Is it just kicking you from the game or internet also? If you disable the Geo-Filter does it continue to happen?

If you disable the Geo-Filter or QoS fully does it continue?

Can you take a screenshot of what you're referring to please?

Done!

I've given you Early Access, please see if the firmware there helps at all https://forum.netduma.com/forum/151-netduma-r3-early-access/

Well not pointless, all other features would work, prioritizing should still work well but it just wouldn't be able to counteract any usage from other devices. A separate line is a good option but then you wouldn't need QoS as much either as you'd presumably just connect your gaming device to it.

Good to hear, do keep us posted!

The abuse report, the IP is from Google so definitely not being attached. Some routers are very sensitive regarding what they consider an attack but the router has a firewall so you're perfectly safe. Grab a log from where it's disconnecting now please. Also reserve an IP for the affected devices on the R3, hopefully that will keep them connected.

Added, please let us know if that helps your issue - don't use that firmware though, use the one pinned to the top of the Early Access sub forum

The x20 will function as normal and that should then allow the PC on the R3 to get an Open NAT. QoS will not be very effective because it can't control 99% of your network in this setup, it would be mostly for the Geo-Filter.

Added

Added

Hold the reset button in the back of the router for 30 seconds, then wait 4 minutes before accessing the interface, go through the wizard and you can change them there. If needed after the reset the default credentials are admin / password

I'm waiting to hear back from Telstra with an update and then I'll let you know

Port forward ports 1-65535 source & destination, TCP & UDP to the R3, that will act essentially as a DMZ function

The DMZ is fine, now check if you still see the issue through the R3