Killerelite06

What happens if you disable filtering on the Netduma router before opening FragPunk?  If it works, then a required server is getting blocked and the Netduma team simply need to whitelist it 

I would like to request the ability to specify custom IPv6 DNS servers and possibly support DNSSEC/DNS over TLS.

Hi Everyone,
We’ve been working hard behind the scenes to get a new update with new features and stability fixes out to you.
 
Important Note:
You may see "Critical Error: Failed to load minimum required components" after upgrade.
Please ignore this message and refresh the page by pressing CTRL+F5. This will reload the page wihout cache.
 
Changelog:
Behavioural Identification is a new feature which identifies traffic based on the way it behaves. This allows us to categorise and prioritise traffic which hasn't yet been added to our DPI database, ensuring day one support for new games. It can also assume and categorise encrypted traffic based on the way that it behaves, which means that, for the first time ever, we can prioritise Gaming, Streaming and Video Calls even while you're using a VPN! New Themes have been added to DumaOS, you can now pick from Traditional Red, Gamer Green, Baby Blue or Cherry Pink WPS Support has been added. Press the WPS button on the back of your R3 to start pairing mode for 2 minutes. Translations have been added to the UI, you can now set your DumaOS to Chinese, Dutch, Spanish, French, Hungarian, Italian, Polish, Portuguese, Turkish and German. If there are any incorrect translations, you can report them in the change language page. LAN Disconnections have been fixed, you shouldn’t be getting random drop-outs for wired devices anymore. Ping Optimiser has been overhauled and should be quicker and more stable than before. WiFi Auto Channel Selection has been improved, you'll get better speeds over WiFi. PPPoE VLAN compatibility has been fixed, you can now use both PPPoE login and VLAN tags at the same time and everything will work. Memory leaks have been fixed, your unit should no longer have to restart because of memory build up. LAN IPs were sometimes not being assigned before, this is fixed now. Many various frontend fixes. Various Stability and Security Fixes There are more new features coming this year that we've been working on as well. Keep your eyes peeled and we'll hopefully share them soon!
You can install the firmware via Settings > Troubleshooting > Upload Firmware, and upload the file below:
DumaOS-R3-4.0.540.sig
We will be pushing this via the One Click Update over the next week or so.

Have you tried ping assist? Make your filter size as small as possible, turn off geo-latency, and adjust the ping slider to around 35ms so it should find the same server as your xr500. *It might take longer to find a game*

Ten years ago today, we launched Netduma.
When you’re in a startup, you spend most of your time looking forward. Rarely, if ever, do you look back. Learn from your mistakes, don’t dwell on them, keep improving.
But today, we want to pause for a moment. It has been a decade, after all.
The Beginning
We launched Netduma from Iain’s parents' kitchen. Our website had just gone live, selling the Netduma R1—our first router. It was no wallflower. Frankly, it looked a bit like a fire alarm, only had 2.4GHz WiFi, but the software Iain had built was unlike anything else out there.
We sold out of those first R1s almost instantly. The e-commerce site Iain’s dad had hurriedly put together held up well. Our logistics process? Not so much. That led to many all-nighters as we worked through the order backlog.
When you’re a startup, it’s impossible to be good at everything. But to make it, you need to be exceptional at one or two things. We had two. As gamers, we knew firsthand how much lag sucks. And with Iain’s brain, we could actually do something about it.
Soon after, we moved into our first office (to the relief of Iain’s parents, whose house had begun to resemble a factory floor). We hired our first full-time employees. Word spread about what our software could do.
Bit by bit, month by month, we levelled up. We improved our software. We grew our team. We made mistakes. We learned from them. We kept going. And we repeated that over and over.
The very first Netduma office.
Looking Ahead
Fast forward to today. Our tech stack has evolved from fixing lag in games to fixing all bad Internet - for work calls, video streaming, and everything else. We’re partnered with British Telecom, Telstra, NETGEAR, Nokia, Genexis, and Mercku, with more partnerships to announce next year. Just a few weeks ago, our Service Provider business won the Scale-Up of Network X award.
We’ve got a great team, great customers, and great support around us. And we’ve managed to do all this without any investment, putting every penny we made back into R&D to make new features (more on that further down).
If you’re reading this, you’ve likely been part of the journey. Whether it was buying one (or all!) of our routers, helping on the forum, or telling us how we could improve - you’ve made a difference. Every piece of feedback, the good and the bad, has helped shape who we are today.
None of this would have been possible without the support we’ve had along the way.
Thank you.
But here’s the exciting part: we’re just getting started.
For the past few years, we’ve been working on two groundbreaking features. When we first envisioned them, we weren’t sure they’d even be possible. One fixes bufferbloat once and for all, with no downsides. The other pinpoints the root causes of poor Internet performance, whenever they occur. These features are set to shake up the industry and will be announced early next year.
While it’s great to look back on the past ten years, we’re even more excited about what’s ahead. A huge thank you to our elite team in Cambridge, our incredible partners, and everyone who has supported us along the way.
Thank you,
Luke, Iain, and the entire Netduma Team
P.S. If you haven’t yet bought our award-winning Netduma R3 router, which runs the very latest Netduma software, you can use the code ‘10Years’ for 10% off—this week only.

Gotcha, thanks, I've passed it on, there are no other servers in that region so as long as you have the south covered you won't miss it

Hello everyone,

This update brings a ton of exciting new features! You can now enjoy experimental support for many new languages, customise your theme with a choice of colours, and benefit from improved loading times. Additionally, You can now easily update your R2 firmware with one-click when DumaOS 4 is ready. The new Devices tile on the Dashboard provides a clearer overview of your network, and the improved bug reporting feature makes it simpler to share feedback. We've also included numerous bug fixes to enhance your overall experience.

Please see the full changelog below.
 
The app will be fully rolled out in about 10 hours from now.

You didn't have access, try now

Jokes aside people have to realize it’s a small team and there isn’t a way to quickly lookup a fix on Stack Overflow, YouTube or GitHub so their manually searching for bugs and coding the fixes
Great things come to those who wait  

Jokes aside people have to realize it’s a small team and there isn’t a way to quickly lookup a fix on Stack Overflow, YouTube or GitHub so their manually searching for bugs and coding the fixes
Great things come to those who wait  

You can use code CBASS for a small discount.

Okay thanks, I'll see if the team can gather anything from the logs

That all looks fine, when it happens could you get the log please?

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.

its all ready done but amount of light shines tru back vents looks like i have wall light mounted there 😂

It has been requested so it will likely come in future, I will ask the team to see if they can get it in the next one if it's a small job. 

Hello everyone, here is the first update of 2024 for the Netduma R3. This update is not available as a 1 click update from the interface, you will need to upgrade manually.
Please read carefully:
We have tested this firmware but not as much as we would have done normally, reason being is we wanted to get this out to people to try without any further delay SO it is possible you could see issues as with any firmware update but it's looking pretty good so far. 
This update does not fix every single issue that has been reported, it is possible that issues you may have that aren't covered in the change log have been resolved but if its not been mentioned don't expect it to be fixed.
Please do not report issues you already have that haven't been fixed in this firmware, we know what the issues are and they're still being worked on. On the other hand if there is an issue you were having that has been fixed please do let us know as that helps just as much as reporting issues.
TL:DR
Don't report issues that have already been reported and that haven't been mentioned in the change log Report whether issues mentioned in the change log and issues that haven't been mentioned have been fixed Report any new issues you've encountered after upgrading Changelog:
Improvements to stability of upgrade process (memory issue should be fixed) Improved performance during high bandwidth usage Fixed a bug when disabling multiple devices in Adblocker Added ability to select individual server in Ping Heatmap when servers are grouped together Improved reliability of Speed Test Reduced CPU usage of certain services that were causing ping spikes Various frontend styling fixes Firmware removed while we work to fix issues.

Alright guys this topic is getting a little heated so I'm going to close it. A new update is being compiled currently, it'll get tested a little bit more, if everything looks okay I'll allow people to try it out tomorrow. 

Here's a setup video for those who have a UDM Pro and DumaOS router such as the NetDuma R3.
 

All members of our team uses this image as their desktop background. I've uploaded it here for anyone who might like to download it in either 1080p or 4k resolutions. Here is the Google Drive link:
https://drive.google.com/drive/folders/1f_i1R_y0KgComiEK5j4rBfEpLv_i4Y57?usp=sharing
 

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!

Firmware will come this week, will be tested first/provided as a link to those that ask for it before it's pushed to routers

How GeoLatency works is if the server is outside your radius it elevates the ping to it's target value, so all servers end up with the same ping. In your case you ended up connecting to France instead of the closer Saudi Arabia server for Apex because to the game they appeared the same. This will be reviewed so this exact scenario does not happen (maybe it will add a fixed percentage to the existing ping instead, but it needs an internal discussion)

I received my R3 this morning and I have to give DHL & Netduma credit for shipping the router in a single weekend (vacation days included). The box feel and design tell you this is a premium router. I can only admire the team's progress when I compare the R3 box to the early adopter R1 box.
Setup Wizard- I saw some users were having issues getting the setup wizard to work luckily I didn't encounter any problems configuring a Static IP. Even the $ wifi setup bug is fixed.
Geo filter-  Ping stabilizer is a Netduma dev team "big brain move" if you had to describe it. Mine stabilizes the ping but it still fluxutates by 1-3ms now and then another small bug is it stabilizing but failing to ping the server (Only tested on Warzone so far). The new ping assist is amazing especially if you want to target a very specific latency it is however hidden away in the settings tab 
Ping Heatmap- No complaints. I like how it shows you the best server, server stability, and spikes
SmartBoost- A set-and-forget QoS solution. No more allocating bandwidth or struggling with sliders day after day 
Network Activity - Easy to monitor how much bandwidth is getting used by what and who. All my devices show as connected so the offline device bug is fixed I presume.
Device Manager- Super easy to see network quality across devices
AdBlock- It's a hit or miss. I can see it blocking plenty of ads/tracking but it seems to struggle on iPhone.I can't see it stopping ads or popup ads. 
SpeedTest-  Accurately measured my speed on the first try
Ping Optimizer-  Ping Optimizer is currently bugged so I just manually set my values to 95%. Thank you for adding the low-latency-only mode
Wifi - It's a major improvement over the previous generation Netduma routers but it cannot provide stable service at longer distances. Is there a reason why WPA3 isn't supported?
RGB- I like the lights but is there a way to completely turn off the white LEDs also?
WAN-  I want the ability to specify an IPv6 DNS address and the recent change to DNS prevents me from forwarding DNS requests (ONT- AX88U with DNNSEC/DoT and the Netduma set to the Asus router IP). 
UPnP - This could be a one-time bug but it struggled to open port 3074 to achieve an Open Nat on CoD. 
Should port scan protection be off by default? 
 
 
 
 
 

Had a look, here is the list of issues. Some may end up being working as expected, but I mark the ones that are definitely bugs.
Siege not compatible with Steady Ping - this may be because Steady Ping doesn't provide any benefit to the game or we just don't support it yet, have to confirm this one.
Blocked servers can be hosts because of GeoLatency, but we ignore them for Host detection (to show ping) - I rewritten host detection since then but it has the same issue, this is a bug.
Geo-Filter Map stops working after a while (15 minues?) not showing any changes in connections - this is a bug (ofc) for front-end
Pinging can end up in trying to establishing a ping for a very long time showing the pulsating skeleton element - bug for back-end
Geo-Filter can't ping servers that Ping Heatmap can, especially Console devices in Geo-Filter - bug for back-end
Some servers block ping for periods of times, then allow it again - nothing we can do about this one but it probably looks confusing. Steady Ping status still displays in this case which is correct.
If there are no servers in your filter radius GeoLatency just adds more latency to the nearest server (like Apex) - expected, but confusing because the game has literally no choice but to connect to that server so you end up with higher pings.
 
Edit: Confirmed, Steady Ping is supposed to work with Siege as well. Now they know it isn't working.