Leaderboard

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

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

THIS ARE JUST SETTINGS OUTSIDE OF THEIR GAME CONFIGS. THIS IS MORE TOWARDS THE R3 AND YOUR PC BACKGROUND PROCESES! you will still need to adjust your ingame settings according to your own specs. ect ect ect. this are the ADSOLUTE BEST settings for your bullets to kill as FAST as possible! 1. heres a pic of my fiber without the R3 2. Heres a pic of my speed with the R3 and all the settings i dissable inside the R3 to eliminte latency inside my router. turn these settings off at your own risk. i did and havent usse it in a month w out any issues. 3. run some bufferbloat test until you find your sweat spot 4. nornal speed test web is down for me idk y, but you need to lower your jitter as much as you can even when you do a simple speed test. 5. look at your task manager and if you have more proceses than what I have, It might be the reason why your jitter is always HIGH! or your game feels laggy and dogpoopy. 6. if you need help lowering your proceses without damaging your pc. check this link. it will take you to this guy who is a profesional. he worked with people like clix, bugha, and more pros. watch the video and follow the instructions. MAKE SURE you create a restore point right before your start or do anything. the only thing im experiencing is once i did mine. i cant no longer play music audio without having to RE-install my media player again. i dont mind that. so i dont care. i use my other pc for that. i can still do everything tho, everything works normal. this is the channel. 7. this is my congestion control settings 8. my games feels amazing no more shoot first and die first. anything outside of my control like servers lag lol well yall know how that goes.

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.

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

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

Those are ridiculously large in a I'm scared it will start scurrying across the room kind of way

done it . thanks

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

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

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.

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.

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

i got it working not sure what i did but it works now

It took a lot of time and effort to finally achieve this result. Trying things out, shifting the mesh system, and adjusting the netduma. I'm very happy with the result.

I appreciate the info and it helped a lot! Happy to be part of the Duma gang again.

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

Ya I've addressed all of this. Thanks though

It's the Windows Task Manager

All sorted somehow

The router limits me to 600 and something. IF i direct connect to my modem i get over 1 gig to the device. I even turned of QOS and tried

Hi guys, Just wanted to pop into the off-topic section and introduce myself. I've been reading the forums for a while and figured I'd finally say hello. Hope everyone's connections are stable and the lag is non-existent today. Happy gaming!

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

Okay well the PingPlotter results are looking very good so I think you can ignore the waveform test

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.

Fala, meu querido! Muito obrigado pela disposição em me ajudar com tantas dicas, muitas inéditas pra mim. Vou te dar um toque por mp, ok?

I prefer 236.

you can use antennas off of most any old routers if you have some laying around. The ones to my old XR450 will fit on the R3.

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.

@Krush not that, sorry. Wifi dropped out for ALL devices. I only had one static IP besides the router and it was outside the scope of the DHCP (1-10 for network devices, 10-99 for static, 100-250 for DHCP scope) SSID has been constant since installation. I may have resolved it by Factory Resetting the R3 router, splitting the Wifi bands and resetting again. I now have 10 devices on 5Ghz running stable, 3+ devices on 2.4Ghz running stable (so far) I think the issue is when 2.4 and 5 are using same SSID, R3 router has issues when multiple devices switch band at similar times and then cannot re-assign IPs to the MAC addresses. Each outage seemed to be in time with a DHCP renewal log "flood" However, splitting the bands should stop devices switching, and stabilise connections (I hope, bad timing yesterday when I was working online with a client)

Merci pour le retour ! Have Fun !

I did it thank you so much 😁

Obrigado

You can use one or the other, you don't need to use both as above

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!