Netduma Fraser

I'll see if I can get a change log together when the next firmware becomes available

At this point I think it's just worth adding your PC with the Games Console service, it'll prioritize the game regardless of the port it is using and you won't need to figure it out either

What new update specifically? What do you see when trying to login?

Set the same static IP information on the box as well then for the R3 and lets see if that stops it

Glad to hear you were able to solve it, thanks for posting your solution!

That would be up to Telstra, if it's something you'd like to see then let them know!

I've given you Early Access for the R3, try the new firmware we just posted on Friday and see if that's any more stable for you.

That's fine, to make the R3 have a static IP to hopefully prevent this lease being a problem you'll need to do this on the right hand side - WAN > Network > Static. Check the WAN IP for the R3 on the System Information page then put in the Settings like this: IP (the WAN IP on the System Information page) Subnet Mask 255.255.255.0 Gateway (the IP address you use to access the box) then apply and reboot, wait a few minutes and see if the issue happens again.

I think the ping was probably correct and the server was undergoing heavy load at the time which is why it was higher in game than on the Geo. UPnP is enabled by default yes, in most cases I'd generally suggest just leaving it on to avoid any issues. The security updates are for any vulnerabilities that have been reported in general to the router industry and fixed before they become public and they don't have anything on UPnP so it'll be fine!

Do try the new one, it should be more stable overall We released .236 in Early Access on Friday

We've not seen the error come up again on newer firmware, are you still seeing this issue?

That's good in a way, not sure what the intended behavior is there, I'll check, thanks!

Not a Nintendo Switch but a network switch - one that provides more LAN ports

It's really the same answer for anyone who has higher than expected bufferbloat results on one of those sites - you may not have found the values that work best for your connection - the R2 and R3 are completely different hardware and software so what works for one may not work for the other. Those sites are also simulated tests of how your connection would react under load. A real world test using PingPlotter for example may provide you better real time results.

Okay so you want the rules the other way around, the source port as 1-65535 and then the destination as the game port and it should work

Are you using a switch in your setup by any chance?

I've given you early access: https://forum.netduma.com/forum/151-netduma-r3-early-access/ that firmware will definitely fix the Steady Ping re-enabling itself. If you check the Geo-Filter when loading the game initially do you notice anything being blocked on the map?

Not super easy no, can you provide a screenshot of the rules you've made? Ah good to know, we do want to expand into other categories of games and see how we can help them!

That's pretty good considering we didn't think it was working much at all!

Look up the ports for the game and then you can use that in conjunction with the bottom of this guide to get them added: https://support.netduma.com/en/support/solutions/articles/16000077073-dumaos-optimal-settings-guide-qos Unless it's a highly requested game from the community it is unlikely to be tested to be honest, I've not heard of the games or have had anyone request them before but I will add them to the list if the team do have some extra time in future to test the games.

I don't have any specific information on this so I'll check and get back to you

I will chase again, thank you

I'm not a developer so I have to pass them on to one to take a closer look

Is this with the latest version we put out yesterday? Steady Ping should be disabled now so that shouldn't be it - are you seeing high ping on the Geo-Filter when this happens or just in game?

Can you provide a screenshot of your DHCP page please? What firmware version are you using?