The_Optimizer

Hi, I'm one of the backend developers.
This issue was causing small latency spikes of up to 4ms, caused by high CPU usage of the Data Usage Daemon (part of the Network Activity history feature). It's been fixed and now has 0-1% CPU usage all the time. This is coming to the next firmware, most likely next week.
If you're interested in the technical details, the issue was caused by an unneeded system call causing malloc/free for every flow measured.
Thank you for buying the Netduma R3 early!

Oh ok sweet! 😄

There aren't any specific settings for it, I think it's related to an issue we already know about so should be fixed in the next firmware I think

Thanks guys!

Oh wow thanks for the heads up @Gskillz

Hi everyone,
We have a brand new R3 firmware for you. It includes many important fixes based on the feedback we received since the launch, including addressing issues with Steady Ping and Geo-Filter 2.0 to make them more reliable. The full change log is provided at the bottom of this thread.
Over the next few days, you will be able to upgrade automatically by clicking on the 'Update Available' option in your user interface (both mobile and desktop). However, if you prefer, you can manually upgrade your R3 now using a PC or laptop by following these steps:
Download the attached upgrade file. Reboot your R3 - this is a one-off as this new firmware contains improvements to make manual upgrading smoother in the future. Go to the Netduma R3 user interface on your PC/laptop. Navigate to >Settings >Troubleshooting and then click Upload Firmware. Choose the file and then upload it. You'll need to wait a few minutes for the upload to complete.. If you upgraded to version 4.0.40 last week, we recommend upgrading to this new 4.0.41 as soon as possible. The previous firmware had a niche packet reordering bug affecting login issues for games like Fortnite. It also made Geo-Filter 2.0 less reliable. These issues are now fixed in the latest release.
R3-4.0.41.sig
What's Next?
Good news: Hybrid VPN development is complete for the R3 and is now in testing. We've redesigned the frontend for Hybrid-VPN to make it easier and clearer compared to DumaOS 3. We're excited for you to try it out! In the next few days, we'll be moving it to closed beta testing, and if all goes well, we should have it with you very soon along with fixes to make Ping Optimiser run more reliably and improved IPv6 support.
Please continue to provide us with your feedback so we can keep making your R3 experience better and better.

Changelog:
Alternative download link.
Thank you for using the Netduma R3.

This is resolved on new update, I checked (v4.0.41)

Thanks guys!

I've removed the firmware above but I think the next one will fix that for you

I would test out the latest firmware and see if that solves your problems https://forum.netduma.com/topic/53868-new-r3-firmware-4040/
 

😅 I guess I did huh. Thank you!

@The_Optimizer

 

😅 I guess I did huh. Thank you!

Hi !
You actually answered your own question! no need indeed 😁

It 's seriously weird lol. And it really does seem to work a whole better for me being a PC user playing on the Playstation setting. The geofilter is extremely consistent now. Before when I was on the PC setting, I didn't always see activity on the geofilter when I connected to games. Like the filter would often try and connect to servers during matchmaking but end up not showing any activity once I got in to a match. But the Playstation setting consistently connects me to servers. I'm not sure if the PC is in fact connecting but just not showing the data though.
I also like how I don't have to choose the game I want play when using the Playstation setting. I just select my device once and never think about it again. 

That's so weird that changing a pc to a console and a console to a pc is giving better geo results lol. Curious why that is happening, let us know what they find cus I am intrigued lol.

Actually some people are reporting the opposite way round that it plays better as a PC, e.g Changing a console to be a PC so I think there is something for the team to look at there. If it works for you that's great!

For some reason the Geo-Filter doesn't play well when the device is marked as a PC, seeing it as a game console seems to get it going. Not sure of the why, but using the picture label of PS,Xbox or Game Console is how they have recommended it. Maybe someone from their team could explain it better.

I emailed support and they sent me over a patch. I updated my R3 with the file and It solved the problem. Connected to Fortnite without any hiccups and the match was smooth. The version number I got via a file that was emailed to me was - 4.0.20 Thanks guys!

I emailed support and they sent me over a patch. I updated my R3 with the file and It solved the problem. Connected to Fortnite without any hiccups and the match was smooth. The version number I got via a file that was emailed to me was - 4.0.20 Thanks guys!