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

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

At some point some browsers enabled connecting to websites using HTTPS by default which is great for normal websites but not for a local site such as the router interface. Search DumaOS in your phone app store, install and login as you normally would with the interface.

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

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?

We'll need some more information, do you get the same high ping directly connected to your ISP modem/router for example? Are you using the Geo-Filter?

No on the Mac itself

I've given you Early Access so you can try that version to see if it works better but with the Geo-Filter enabled do you notice a blocked icon on the map? (Zoom out fully) If so, add that to your allow list and try again to connect, does it work then? https://forum.netduma.com/forum/151-netduma-r3-early-access/

Oui, merci Je viens de changer de firmware et tout va comme il se doit.

Thank you I appreciate it

We don't give out ETAs as you know, once the team finalize a build they're happy with they will make the selections from the poll topic and add them to the group

I think he is pointing to network processing unit, not AI capable hardware which in this case is irrelevant.

I wouldn't worry about that test specifically, instead 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. It will be more of a real world test.

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

Yes that’s true but a CPU has cycles to inspect and forward packets etc a NPU has parallel pipelines to process in nano seconds vs microseconds preventing spikes when loaded , also provides advanced security with barely any latency compared to a CPU . if added it will be beneficial but if you guys can’t it’s fine I’m only listing what I thjnk can have a big enough difference

I think we'll be putting out a new cloud update this week so it should be improved

If you have a steady ping already that doesn't fluctuate much then quite possibly you'll have a better experience without it as otherwise you're just adding unnecessary ping. We provide the features that you can experiment with but it doesn't mean everything has to be used, some people will find a better experience without it. Every connection is different.

There has never been a limiter on DumaOS 4 which the R3 launched with right away so no that's not possible. The closest thing to limiting is what you have done by reducing the speed you've told the router you have

@fds By monitoring the game during the bufferbloat test, you can detect abnormal spikes or packet loss. If such issues occur, continue fine-tuning the settings. The goal of SQM (Smart Queue Management) is to optimize the network, prevent overloading, and maintain consistent latency. Every connection is unique; for instance, my connection has 2G download and 400 Mbps upload speeds. To ensure stability without packet loss, I adjust it to 180 Mbps download and 60-80 Mbps upload. This setup consistently earns me an A+ rating, even during ISP congestion. Throughput is less critical for gaming; latency and stability are the key factors. While other elements may influence performance, the most important ones are within your network, which you can control. It seems that you want full throughput when you're not gaming, which is achievable through the router settings. Simply select the low latency option, and it should only be activated while gaming, if I recall correctly.

Thanks for the suggestions, I'll pass them along to the team. Though half the software suggestions the R3 does have already!

They usually use the same servers for the games so it's likely they've added more/replaced some with newer ones. I think what you've got is great for now and then when the game launches we can test further and you can provide any then if we miss any in an update, thanks!

You could have just Gaming prioritized or select your PS5 or both or do the game as well, its entirely up to you. It would be good to add the PS5 itself as a device as a fallback if normal detection isn't working

DMZ + PC = WARNING ! Ne jamais/jamais.... faire ça !

Send me also

We'll fix the PPPoE issue, thanks for letting us know. Disable Geo-Latency and Ping Assist, make sure you're enabling the Geo-Filter before you launch the game/client and if you change Geo-Filter settings while on the game then reboot the game and it should all stay within your radius. We're aware Ping Optimizer isn't 100% reliable currently but the ping at the start is your base ping - the ping you have before you do anything on the internet so it's established what that is to the server it is using (the ping won't be the same as wherever you may see your ping). It then simulates a heavily used network and re-tests the ping, this is where you'll see an increase in the ping. It then repeats the tests but adjusts the Congestion Control percentages to find the percentages that allow you to have a heavily used network with minimal difference in your ping. So what you described is the optimal outcome and exactly what you want it to be doing.

Do keep in mind that the beta has just launched, the player base is going to be massive and the servers will be under strain, this is something I am sure they're prepared for and are using the data to improve it for launch

We've got captures of the game and hoping to start testing it today/tomorrow and when we're happy with that it'll go public

Try this:

Autoriser/refuser, se limite à un serveur.... sur une multitude de serveur avec des id différents sur la même localisation !

Reboot to restore it. I will once back

When the speed drops does it return on its own or do you have to reboot to restore it? When it happens grab a picture of the WAN & LAN settings pages please

yeah, I know but being the IT wizard that I am I've lost the download after I reinstalled the original firmware again 😱 .....thanks for your patience and quick reply.

A bit more white but not pure white for me, regardless I've passed it onto the team so they'll take a look when they can

Yes of course doing it right now.

It should be better but do keep us posted!

I'll get the team to update Ping Heatmap for The Finals, thanks for the report - it won't affect your connection quality or your ability to connect to servers. It's purely a tool to inform you of where the servers are approximately located and your estimated ping to them to give you an idea of where you might want to force servers. Geo-Latency is enabled, that's why you are sometimes getting games outside your radius, if you disable that it will exclusively use your radius/zone. I'd suggest you remove the 4 iterations of your device from the Geo-Filter and then on the Device Manager give your PC a PlayStation device type. Then re-add your PC to the Geo-Filter and it should add as a console. The benefits of doing this are two-fold: a) You don't have to deal with/enabling/disabling multiple added devices/services b) If any of the game services you have added are out of date then this method will always allow you to filter in the sense that it'll never become outdated - there may be times we need to retest though if they've changed something drastic but for the most part you can add and forget.

C'est juste lié à la façon dont est connecté le R3 derrière votre FAI ... C'est connu... mais très facilement résoluble ! 😉

Oui je l'ai faite toute de suite, car a cause de l'ip partagée j'étais en nat modéré sur mon XR500

Tu es trop fort Krush! Même apres avoir enlevé mon pc du dmz du R2, je suis encore en nat ouvert. Un grand merci!!! Si jamais tu as d'autres propositions a me faire pour optimiser ce R2 et ma connexion je suis a ton écoute 😁 Encore merci!!!

Merci Krush! J'espère tavoir correctement compris.

Freebox! 😉 Tu vas dans paramètres "avancés" / DHCP / Baux actifs- sélectionnes le R2 (clique droit) ajouter et définis l'IP 192.168.1.165 De cette manière le R2 sera toujours derrière le DMZ avec la même IP. Tu peux désactiver IPV6 LAN/WAN sur le R2... Elle n'est pas gérée avec FREE.

@Wr3ck3rIt's a known issue currently being addressed. It doesn't impact the router, and you can use speedtest.net as an alternative.

I restart my router normally once a week - every 2 weeks, I have resynced the cloud, I'm on the latest version since like February, I have also checked with my ISP, no issues on their end

ACC is mentioned in that link I provided but we haven't provided any more information about it just yet. You can enter the poll here to be in with a chance to test it early on if you fulfil the requirements for this early test: https://forum.netduma.com/topic/60353-answer-this-topic-to-be-in-with-the-chance-to-beta-test-a-firmware-with-new-features/