Netduma Fraser

We can't release something that is not ready/available once it is it will be released. I realize it is frustrating but it is coming

Expected this week

The router isn't a live service product so if you're having an issue it'll be on your router or a bug. If you test using a wired PC do you get the same low speeds?

Where did you find that was the case? For that kind of game TCP should absolutely not be used, I'd find it very hard to believe they were using it but no you can't find out what your next match is. Try other percentages for Congestion Control, 70% is the recommended starting point but may not be the best for everyone.

If a game shows your location like CoD it should change

SteadyPing doesn't ping the server, that stabilizes the connection, it's just the normal ping function that pings, it's something we'll be improving, I believe we know a reason why it happens

Switch their port to another then use 3074 for yours, then reboot and check whether the features then work better for you

As this is your first post I'd suggest making a topic with your issues and we can help you there

I believe it's already selectable on the R3

Thanks for letting us know your experience, as you've returned it I can't really troubleshoot it with you but perhaps after updates you'll consider us again

Updates are coming, I don't know what order fixes/improvements are coming at the moment, depends on the difficulty of the issue/solution

You can find it here: https://forum.netduma.com/forum/106-latest-firmwares/ Not sure what you mean, .23 was made before the holidays, it wasn't pushed to routers, that close to the holidays it would have been a risk to do so. That's why I manually gave it out and monitored, it hasn't seemed to cause any issues. New firmware is still on the way. New firmware is on the way, I don't know if all fixes will be in it or they'll be doing multiple over the coming days/weeks

If you try the ports again, leave the source as the default and just change the destination. If you're wired use normal, wifi use gaming/voice. You're welcome!

That looks fine, do you know what the DNS of the VPN is? Enter that in the VPN Setup menu and it should be fine then. Devices can also cache IPs so worth rebooting the device you've added to double check.

Glad to hear it's sorted, thanks for the update

Should be pretty quick really, no longer than 5 minutes really, the router won't be connectable the whole time it goes through the process. Did it upgrade successfully?

You're welcome. That would be interesting to know, do keep us posted once you can try it.

Ah weird haha! Great to hear though. Doesn't happen too often, would be best to update to the latest https://forum.netduma.com/topic/50710-new-r2-firmware-33280/

If it's connected its fine but how have you added the devices specifically as that's important for how the VPN treats it, if not setup correctly the VPN may not apply to them.

Do you have another console connected to the router? It could be another device using the port which is why it can't be selected

From the screenshot you provided there is a section called DHCP Reservation under LAN Settings. Not sure if it will list devices or not so you can see the IP but if not, copy the WAN IP from Settings > WAN on the R3 and then enter it there.

What firmware version are you on currently? Do this: Disable GeoLatency Disable PingAssist (set it to 0,0) Enable Strict Mode Disable Fast Search Then restart game or wait 10 minutes (in the lobby in the game). If that doesn't work, reboot PC/Console and it should work then - keep this in mind when you play. Also: 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 any better.

It could be Adblocker, disable that, do websites load correctly then? You probably don't need it if you have internet now. 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.

The above should help with the Geo-Filter. In terms of the disconnects, if you give the R3 a DHCP reservation on the other router, then reboot the R3 does that prevent the issue happening again?

If you notice it again please get the ID and we can correct it and should help with preventing you connecting to it again