Netduma Fraser

Great to hear that, thanks for the update!

Try this: Quit the application/game/client completely Remove device from the Geo-Filter 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 Then see if it works better. Just unstar the ones that are added on SmartBOOST.

Could you please change your username/display name? It can give the wrong impression that you're a member of staff. That's what a user has reported but I haven't seen it personally so couldn't say for certain. Cover a few servers within your radius, if it is there it may not always be available to connect to.

When it says it couldn't ping that is for a legitimate reason, some servers do not respond to pings. Is it pinging the rest of the time? We're working to improve the inactive/active showing but as you're getting games it is working just displaying incorrectly. What are your Congestion Control/SmartBOOST settings?

Okay try this, make sure DMZ is disabled, set a static/reserved IP for the device then set a port range port forwarding rule: Source start 3074 Source end 3074 Destination start 1024 Destination end 65535 TCP/UDP Does that allow you to get an Open NAT and stop the port changing on the console?

Thank you, okay so the destination port is different, if you make a port range rule: Source start 3074 Source end 3074 Destination start 1024 Destination end 65535 TCP/UDP Does that then allow you to get an Open NAT?

UPnP is being looked into, in the meantime port forwarding should allow you to get an open NAT

If the server is unavailable it may not work, if you try a few more times it should be successful

If you download the logs using the button at the top and provide it here that would be better. What firmware version are you on? What is the model of the modem/router the R3 is connected to?

Disable the priorities set on SmartBOOST as it can also interfere with the test. Not working in what way?

It really depends on your connection and your use cases, there isn't a one size fits all option really. We generally recommend 70% at auto as a starting point

I think if that's what you experienced on the 500 that's more of a fluke as I wouldn't have thought that would work. The only way this could work on the R3 is if you use Geo-Latency which should be improved now on the latest version.

Have you disabled speed test bypass?

It's been posted here https://forum.netduma.com/topic/53938-new-r3-firmware-4041

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

They can be shipped on the same day but it depends on the time of day. If you did literally just order before you made the post then it'll be sent tomorrow.

Try this link: https://drive.google.com/file/d/1LVrVjhOSJCl2eTj0wh8_Erw9ti986vzD/view?usp=sharing

You'll have to adjust a bit more, 100% does nothing, 70% is the recommended starting point but won't necessarily work the best for everyone

We are aware Ping Optimizer/Speed Test isn't 100% reliable at the moment and it's something the team are working on. Those features can still work, it just may not be every time. In the meantime best to adjust Congestion Control manually in Ping Optimizer > Advanced.

Sorry to hear that, you can email [email protected] regarding a return

Would be a good idea to start with our playlist here: https://www.youtube.com/playlist?list=PLCU0-ELvZkOqiQFGXII95B7063uASKQlO

Go to Settings then scroll down and you'll find it

Ah good point, I'll see about editing the form to allow them

It's difficult to block YT adds from a network level, the ads and video are served on the same domain

Hi all, thanks for the feedback, just a reminder, if there is a particular issue you're having that isn't mentioned in the change log then it won't be fixed, we're aware of all issues so it will be being worked on. So please keep this topic to issues you have had since upgrading to this firmware version. Makes it easier for us to then pick out any new issues and answer questions specifically related to this firmware. You can always create a new topic if you're unsure of anything. What settings were you using for NAT? What is your physical setup and how is it setup to pass traffic directly through to the R3? That's been reported, we'll take a look Thanks for the report, will pass it on.