Netduma Fraser

Traffic Controller is essentially a parental control feature, it's not a prioritization feature, by making a rule here you're superseding the Geo-Filter - presumably you're allowing all traffic to the device when the Geo-Filter is trying to restrict traffic - you're essentially telling the router to do opposite things at the same time. You just need Traffic Prioritization on the QoS page.

I don't think anyone has requested this game as it's not our demographic and we tested it many years ago and it didn't work with the Geo-Filter and just caused you to get penalties so we just left it alone. I'll ask the team to test it for use with SmartBOOST, Steady Ping etc.

It has been requested before and it was something we were looking into at one time, I think once we've got the R3 to a place we want it that's probably something we can revisit.

That's weird, I've not seen it before, I'll pass it on just in case though. Is there any pattern you can see regarding when you get the disconnect at all?

Glad to hear it's working better for you now! Two things to keep in mind for a new update, if you're having an issue that you weren't previously it's always good to do an update. Also settings that may have worked on a previous version may not be the best settings on the new version so you may need to fine tune - particularly with QoS.

Well done, thanks for helping!

You can try the above but otherwise it is very normal to get a worse NAT when using a VPN

I think you may need an SFP+ module/converter so you can connect it to the R3

Are you referring to Traffic Prioritization on the QoS page or a rule you've made on the Traffic Controller? If the latter, that isn't a prioritization and that's why it's not working. You want the specific prioritization option at the bottom of the QoS page.

Yes that one should work

It's certainly possible, especially if you had a device that connected via ethernet and WiFi at different points, they'd each appear as a different device. Glad it's still working!

There is no specific video for it but you need a VPN subscription from a 3rd party provider that can give you the OpenVPN or Wireguard VPN files which you can then enter into the router

That's entirely up to the devs, if they can squeeze it into the next update they will

Spikes that can't be eliminated by QoS are otherwise essentially impossible to counteract so it's the best solution to keep your connection stable

It really depends on your connection and the severity of spikes/jitter you usually get, based on yours simple should be sufficient except in those cases where it can't cover the big spikes - it depends how often those big spikes happen, if it's frequent then it may be best to use expert but your overall ping will be higher then.

If you're getting the same issue on two different ISPs, no one is using the internet/QoS is enabled and you're forcing local servers then that very much sounds like a game issue. I would not be surprised if a lot of people are returning to warm up for the new CoD beta and putting pressure on the servers

With Congestion Control that can be found in Ping Optimizer > Advanced.

Added, you can find it here: https://forum.netduma.com/forum/144-netduma-r2-early-access/

I'd contact them about the static IP then as it's clearly not working as it should

We're full steam ahead with the DumaOS 4 port for it so that will be the next update coming

We're doing our best to push them towards a release

Sign up for Early Access here: https://forum.netduma.com/topic/39415-introducing-early-access/ and let me know when you've done that and we can get you on that version instead which may be more stable for you.

I'd suggest testing with downloads while following: https://bit.ly/bufferbloat-test start with a high value e.g 95%, test, decrease 10%, test, decrease 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. Important to note that Download/Upload on CC don't have to be the same value & you may have a better experience with differing values. This is more of a real world test as you're actually doing traffic you would normally do. Once you get that sweet spot you shouldn't get the issue any longer.

If it's not in the change log it won't have been added - we're focusing on a disconnect issue at the moment, which as I'm sure you can agree takes priority hence why there hasn't been a firmware for a little while.

It's not broken, your connection spiked higher than Steady Ping was set to cover