Leaderboard

Hi everyone, We are excited to roll out a major new firmware update for the Netduma R3, packed with significant improvements and optimisations we’ve been developing over the last year. This is a comprehensive release. You will experience a noticeably faster user interface, improved Wi-Fi auto-channel selection, new dedicated front panel LED controls, and key memory and security patches designed for long-term stability. Alongside these broader enhancements, we have completely overhauled two core systems: Device Manager & Classification Engine We have implemented a completely new Device Classification backend that allows classification and categorisation rules to be updated dynamically over the cloud. Just as our DPI system automatically updates to support new games, DumaOS can now recognize and categorize newly released smart devices as soon as they hit the market. To help make Device Manager as accurate as possible, users can now optionally report incorrect classifications directly to us. This reporting is purely opt-in, fully anonymised, and directly helps improve detection accuracy for all users. You will be asked if you want to participate the first time you make changes in Device Manager, and you can easily change your preference at any time from the Settings menu. Geo-Latency We have fine-tuned Geo-Latency to work more reliably with our currently supported titles, while expanding support to include more games, such as Battlefield 6. We have also reduced its footprint under the hood to improve overall system performance. Behind the scenes, we have been working hard on several exciting new DumaOS features that we are almost ready to share. Expect to hear more about those very soon. Thank you for your patience in waiting for this new firmware, and thank you for being a Netduma customer. DumaOS-R3-4.0.1510.sig Full Changelog:

Hi all! App version 1.3.20 is now available on the App Store & Play Store for iOS and Android. Here are the changes since 1.3.15: Update to support Android v35.0 Support Android 16KB page size requirement Update iOS min target version to 12.2 Added Developer Options page Netduma R3 Front LED toggle support Handle WiFi Merge/Split flows with more than 2 wireless bands Improved UI performance Added Report Core dumps toggle Fixed Netgear Auth error shows up as DumaOS not running error Fixed Factory Reset never ends Fixed Polygon that is only a line can be saved in Geofilter Fixed Bad layout of Factory Reset item on Troubleshooting page for languages with longer text for it's button Fixed CPU graph not accurate (shows a tiny bit less than it should) Fixed Sometimes Setup can be stuck on splash screen forever after finishing Fixed Stats for Nerds page doesn't display anything in some cases Fixed Early redirect between hardware setup and regular setup and setup is still displayed after finishing setup Fixed UI sometimes doesn't load after Factory Reset or on UI exceptions Fixed Logout from units properly Fixed SmartBoost Stats for Nerds page doesn't display apps/categories properly Fixed Many translation fixes Fixed Geofilter server page immediately hiding in some cases - and in strict mode Fixed RGB Controls crashes when incorrect hex value is set Fixed Going back from add custom router causes crash on iOS Hide SmartQoS manual allocations page by default

Was searching #NETDuma on X looking for ideas to get the most out of my R3 and I swear TODDzillaInLA was taking over the search results 😂 Kept seeing MW4 clips, NETDuma tags, and his setup popping up everywhere, so I had to check it out. Pretty cool seeing someone consistently posting gameplay while actually using the NETDuma stuff. Now I'm curious what everyone else is running on their R3 for COD. Always trying to squeeze out every little advantage possible 😂

https://test.libreqos.com/advanced/

Outstanding work as always team 😃👊

To be honest, the NetDuma community isn’t really a typical customer base. We’re more like passionate enthusiasts with a mild addiction. We complain, we debate, we push for more… and yet we’re still here. That says something. We appreciate that updates for the R3 are in progress, and it’s good to hear they’re substantial. But there’s another thought that many people here share — some openly, others quietly refreshing the forum every day. We’re not just waiting for firmware. We’re waiting for the next level of hardware. If a more powerful next-gen router — call it an R4 or whatever it ends up being — were announced tomorrow, I genuinely believe a huge portion of this community would upgrade instantly. Not because of marketing pressure. Not because we’re being manipulated. But because we believe in the idea behind NetDuma, and we want to see it running on hardware that truly matches its ambition. Sometimes the frustration you see here isn’t negativity — it’s anticipation. People don’t get loud about products they don’t care about. The reason discussions get heated is because expectations are high. Give us DumaOS running on seriously powerful hardware, with proper headroom for the future, and that wouldn’t just be another release. It would be a statement. We’re not angry customers. We’re impatient supporters. And that’s a good problem to have.

Can't believe it's been 11 years since I joined the forum , during that time I have had the R1 / R2 XR500 with R2 OS and now the R3. Today my R3 is plugged into my Asus RT-AX88U Pro , Just a little bit on the Asus : Rock solid piece of kit with great WIFI coverage and a good amount of gaming tweaks within the OS including various different types of QOS , on average we have around 22 wired and wireless devices connected to the Asus no issues ever . Only the Xbox is a wired connection to the R3 , I have flip flopped from both routers over the last few months and always go back to the R3 from a connection perspective it just feels much better , for me it is best in class it does what it is supposed to do from a gaming / connection perspective . HOWEVER - I had some time over the Xmas break off work and decided to plug the R3 directly into my ONT , so all devices connected to the R3 as it is designed to do , BTW just to say I think the OS on the R3 is excellent from a visual perspective and provides so much information and options to fine tune , much better than the Asus in my opinion , the following is what I experienced over a full week : Daily drops in WIFI or internet connection longest period of connection 1.5 days before I re boot WIFI would not reach as far as my Asus , ring door bell and Hive would not function correctly Family complaints Gaming was even better Where I am going with this ? Is this a hardware or software problem ? , I have tried to live solely on the Netduma router previously but it never delivers on a stable connection as my default network router when everything is connected to it . If it is hardware issue hen I for one would be willing to pay more to have an Asus type performance with the Netduma OS . I know we have had the Netgear experiment but not sure that is still an option mine died a long time ago . In closing I love the Netduma OS , it is back now plugged into my Asus and in my opinion gives me the best gaming connection on the market without doubt . It is just not capable of being a default network router managing all devices . You could I suppose without being dis respectful call it a one trick pony ..... but hey it's one hell of a trick . .

You just admitted it lag spikes when using it though??

It's right there bro. Right before your eyes. "Slightly above average". Read it.

Hi everyone was wondering if anyone else is experiencing shooting first and dying first? I have att fiber 1000mbps internet plan and live in Los Angeles. I’m experiencing an issue where in most cases I know I should be winning gunfights where I’m shooting at someone and I immediately get deleted in less than a frame. I’m a very competitive player and always the aggressor but seems like I’m dying to casual players where I feel like the servers are favoring them if that makes sense. This also happens with rainbow six siege as well and I play on console and sometimes PC as well. If anyone else is experiencing major lag compensation and desync please help. I’m averaging at 3ms ping because I know live in Los Angeles and call of duty servers are located here if that makes sense so I guess being closer to a server handicaps you and favors ppl with bad connection? Please help

Update: turning off geo latency fixed it. Thanks guys.

Hi! Its working now thanks!

done it . thanks

Ah d'accord merci beaucoup pour vitre aide et votre patience !! ❤️

NAT is not something the Geo-Filter can cause being open or moderate. You either have an Open NAT or you don't. You do have an Open NAT. The Geo-Filter blocks the server to test your NAT - it's not causing a moderate NAT. The test because it is unable to reach the server defaults to showing moderate. When it is able to reach the server i.e. with the Geo-Filter disabled then it is able to show you Open. This does not mean you only have an Open NAT with the Geo-Filter disabled and Moderate with it enabled. The NAT is open in both scenarios, it is just the reporting that is different. @Krush can you translate what I'm saying please?

I figured it out, i had my network selector in Fortnite to na east, once i put it in auto it went back to normal

It's not unlikely it will come back at all. It will be updated again

I'm part of the Early Access for DumaOS4 but I can't find the file for that. Any help with that? Edit: Nevermind, lol. My fault.

The R2 was sold with DumaOS 3, DumaOS 4 wasn't advertised as a reason to buy the R2, it was developed on the R3 itself and to get it on the older R2 hardware was a challenge that we didn't need to do but wanted to for our customers. We've explained why there have been delays and this hasn't just been for the R2 either. We never promise firmware because it's always subject to change, I've said many times we don't provide ETAs. The next R2 DumaOS 4 firmware would be the final firmware so the more time we take the more stable it will be overall. Also it is a support forum so there are only people posting issues here.

I still have my R1 from 2015 that i purchased for Advanced Warfare.

As the physical setup has changed the same settings for QoS may not work as well so you'll just need to fine tune it more - don't rely on auto setup just adjust it manually - we usually suggest starting at 70% then adjust by 10% up or down (it doesn't always have to be lower) until you get to a value that's pretty good then try 5% either side of that value to see if it can be improved further. Download & Upload also don't need to be on the same percentage, you may have different percentages where they each give the best results. It is important you have set the speeds you pay for/expect into the router though so it's using that as the basis, otherwise if you've left it with the speeds the in built speed test came back with for example then you may have them set too low and then you're then making it even lower than needed with the percentages.

I've followed through with the setup you two have recommended me with a lot of testing and it seems like it was a local network problem not BT, however, I still get jitters whilst in games but it's fine and I'm scoring an A. I appreciate the help, it's helped out a lot. Regarding the removal of the bt hub, that's something I can't do. I live in an old flat/estate building so I'm on a DSL cable which that can't go into the R3, hopefully one day I move out I can get FTTP 😭

https://forum.netduma.com/forum/151-netduma-r3-early-access/

Hi all! App version 1.3.26 is now available on the App Store & Play Store for iOS and Android. Not many changes since 1.3.20, but here they are: Fixed iOS 26 can't interact with views Fixed Ping Heatmap doesn't display servers with longitude of 0 Updated to use new Netduma Logo The biggest issue was an incompatibility with iOS 26, which was causing a lot of issues. This release should resolve those issues.

Sorry to hear that! We don't give out any ETAs but hopefully not much longer for one

Hello bro thanks for your reply. So I'm confused, what should we be doing? Turn on Geo filter and set my location to which country? I live in the UK so I just want to understand. Thank you bro!

Thanks Fraser

Okay that's good then, the router isn't limiting you, it's just the speed test provider the router uses isn't always the most accurate so you can ignore that

Ya I've addressed all of this. Thanks though

steady ping has been an absolute game changer for me when the server gets destroyed to lag and etc. try it out. I kept mine on default value

It's the Windows Task Manager

All sorted somehow

I will pass it onto the team, it's a good suggestion!

Thank you very much, we do appreciate it, I'll pass it on!

i reached out to nord and they said it has something to do with cod and vpns i got a refund and took protonvpn ..im using the wireguard which works amazing on the r3 you can close this topic

i geofence the same servers as bo6 and it works perfect

We don't announce any hardware until we're ready to, that being said we're focused on this big update right now

You're posting here asking for help and yet you will not take the advice of someone who has been providing support since the company launched 11 years ago. I don't quite know how you think that you know more about the problem you're having than I do but I'm sorry to say that what I have said is correct. If I wasn't correct then everyone would have the exact same issue and they don't. Regardless, if there was an actual issue that needed a firmware update, saying fix the issue is extremely unhelpful, it provides no information about the scenario in which your issue occurred, your full settings, setup etc. If you're not going to engage with the support that you have requested I don't know how else I can help you. In order to really fine tune your Congestion Control percentages you should follow these instructions: Follow this guide https://support.netduma.com/frequently-asked-questions/legacyfaqs/test-your-ping/ while downloading & start with 95% for Congestion Control (set to Always), check results, decrease by 10%, check, decrease by 10% etc, until you get to a value that is pretty good & then try 5% either side of that value to see if it can be improved. Download & Upload on Congestion Control don't have to be the same value & you may have a better experience with differing values.

No worries I understand! Thanks for the screenshot, I'll ask them to double check

I also wrote on that topic, but it's not worth it. The Netduma team published a fake server announcement and they won't correct the mistake. The only two servers that exist for the game are Frankfurt and London in Europe, and you'll never be connected to a third one in Europe.

Any updates on that? it still happens

Yes playing on a further away server is likely to worsen your jitter. No, the Geo-Filter and your bufferbloat test are not connected. The Geo-Filter shows game servers you connect to, it is highly unlikely to show the bufferbloat server you're using. The bufferbloat server could be anywhere, that's the point, doing the test at different times of the day could have you connecting to different servers and therefore getting different results. This is why I as well as Darkness said not to put too much emphasis on its results. Yes it is testing your network utilizing a server for the test. Here is an analogy for you. Your ping without bufferbloat is like driving your car on an empty road, you're going to a location and you know how long it will take you to get there, for example 20 minutes. This could be your baseline ping for example 20ms. Your ping with bufferbloat is like driving your car on a road with traffic, you're going to the same location and you know how long it should take you to get there (e.g. the 20 minutes), however due to the bad traffic it actually takes you 40 minutes to get to the same destination. Your ping here could be 40ms for example. In regards to the server the bufferbloat test is using, without a destination to test it against you can't get a ping value or a destination to drive to. Now imagine your place of work changed depending on the time of day and the time you start work changes as well therefore it could take you anywhere from 10 minutes to 1hr to get there. Would you be so confident to say that it takes you 10 minutes to commute to work everyday? Without knowing the server the bufferbloat test is using your results cannot be 100% trusted. That's why the pingplotter suggestion is better, you know the exact server you're using, you do a test to establish your baseline ping (ping without bufferbloat) and then apply traffic and your ping raises, just like road traffic extends your journey time and then you apply Congestion Control to limit the effect that traffic has on your ping. There really isn't anything else we can advise honestly: You've established it's an issue without the R3 - that automatically eliminates us personally from needing to troubleshoot with you We've advised you select the closest possible servers, this will help lower the ping and improve stability (jitter) We've advised you on how to effectively test and set your Congestion Control percentages to lower your ping and improve stability when bufferbloat would ordinarily apply

Good advice above! We'll be doing more cloud updates including addressing the Oklahoma servers always appearing

If anyone is struggling connecting with skybroadband using a third party modem like an vigor 130 just follow the steps in the picture below. Sky uses an identifier so we need to enter that into the R3 as below 👇 WAN settings then PPPoE then type whats in the picture below exactly and apply and its good to go ! remember to download the latest firmware too

Update: speeds stayed the same. I think i was to blinded on the duma side since i was going to game when i noticed the issue. Rebooting the to link and the duma brought back the speeds. I now made a reboot schedule weekly for the tp link, wish duma also had that feature in its settings since i dont use its wifi. Thread can be solve now. Thank you all!

Copying your settings my rgb doesn’t change still green/ yellow/ brown but it’s white at the edges.

Most of the issues with PPPoE that we've had in the past have usually been with QoS on the upload side not working with it which has been resolved. The issue currently is that a small percentage of PPPoE users are experiencing disconnects, this is most likely due to the nature of the connection method (i.e. that it 'logs' in to the internet service and can have a timeout on it) but we will fix that.

The R3 is the worst piece of networking gear I’ve ever used. It tanked my internet speeds, ruined my PS5 performance, and made my gaming experience significantly worse. Connecting directly to my ISP router wipes the floor with your product. This was advertised as a premium solution, but in reality, it’s a downgrade and a waste of money. I’m done wasting time troubleshooting something that should have worked out of the box.

Hey Netduma fellows, Hope you’re all having a great day! I wanted to share the best settings I’ve found for improving my online gaming experience. Now, I’m not sure if the Netduma team will be happy about this because, honestly, none of these settings are related to the Netduma router. I’ve been using Netduma routers for over five years, starting with the R1 model. Sometimes, they performed great; other times, not so much. Over time, I began to question whether using QoS alone was the best approach—until I was introduced to SQM (Smart Queue Management). Some of you might already be familiar with SQM, CAKE, and FQ_CoDel, but let me tell you—SQM is an absolute game-changer when running on high-performance router hardware with OpenWRT. My Solution for Consistent Performance The key to getting good, consistent results (which has helped me maintain a 3+ K/D ratio in every FPS game) was: 1. Using a high-performance router that supports OpenWRT 2. Enabling CAKE as the QoS algorithm Since CAKE requires significant CPU power, I chose the Flint 2 router, which can efficiently shape over 500 Mbps of traffic while running CAKE. The Best Part? Set It and Forget It The only tuning required is adjusting overhead and MPU (Minimum Packet Unit) settings. Other than that, once set up, it just works. That’s all I wanted to share. Hope this helps someone out there struggling with network consistency!