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

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

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!

Hi. Geofilter doesn’t seem to be working with this game. I know it’s a bit early but I wanted to know if the team is working on it. thx

Generally you won't see all the servers on the Geo-Filter as it only shows what you're making connections to

Likely next week but I'll check with the team

If you're on console you don't need to select anything - it should show as EA Games when done for PC

Eu que agradeço.

I’m experiencing another issue where matching is not working properly. Occasionally, it does match, but most of the time, it seems to fail. When I checked the geofilter settings, I had set the geofence to the U.S. West Coast region, but it says it matched with a server in Oklahoma, which is outside the geofence, and the matching still doesn’t work. Could you please suggest any solutions for this? One notable detail is that when matching works, it shows a server within the U.S. West Coast region set by the geofilter, but when it doesn’t work, it always indicates a connection to an Oklahoma city server.

Thanks please keep us updated here (or on X) so we know when it's fixed!

Thanks for the input.

You would need to ensure ALL devices are connected to the R3 in that scenario, stop any devices auto connecting to the ISP modem/router. It's likely you would just need to fine tune your Congestion Control/SmartBOOST settings to get a better experience. We are working on the PPPoE issue.

There isn't a new firmware currently, the firmware pinned to the top of the Early Access sub forum is the latest

You're saying the ONT requires VLAN 10, does that mean the ONT is actually set to use 10 for VLAN? If so then you do not need to input this into the R3 as well. How often are you disconnecting? When it happens again please grab the logs from Settings prior to rebooting and we can take a look.

Disable Speed Test Bypass first of all and then re-test but it looks like you just need to re-tune the percentages to find what works best for you to keep the ping low. There are lots of variables when networking so it won't always be a case of the same settings working 100% of the time.

Added

Thank you I appreciate it

The bufferbloat test isn't the best way to determine values, 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. Doing the screensharing is more bandwidth intensive, that's why following this guide and instructions is better as you make your network essentially as bad as it could possibly get and then apply settings incrementally to determine what best brings your network as close as possible to its baseline.

Good to hear! I've given you Early Access https://forum.netduma.com/forum/151-netduma-r3-early-access/ if you'd like to try that to see if DumaOS allows access again.

Do you all offer any trade-in value or credit for sending in an R2 in order to get the R3? Thanks

No we don't but good question!

The interface is wholly loaded from your specific router, no connection to us to make that happen. Are you able to access using 192.168.77.1 through your web browser?

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 get this problem of connecting to the oklahoma server as well and I'm in the UK and set my geofilter to the UK

As in typically even in GPU for Pc most people don’t upgrade every gen unless massive improvements for example 20-30 series had biggest improvement and 30-40 and 50-60 series raw performance isn’t a lot more . obviously time between the router models are longer as we see when the Duma R3 was released vs R2. So when we have a R4 released if the improvement is 10% vs R3 most people wouldn’t see a point to upgrade for whereas if the improvement is a lot higher around 40% or more many people will purchase due to the price to performance also despite being more expensive than. A R3 Hope it makes sense

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

Já voltou ao normal, obrigado pela atenção.

It's already available as an option to choose when using a PC. If you're using a console it will only add as a console, you don't pick the specific game.

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

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

I can say with 99.9% certainty that its peak time congestion, the more subscribers they have in one area the worse it will be. There isn't much you can do really as its on their side. Switching to an ISP that is less popular in your area would likely improve it but if you're in quite a built up area you may have the same issue.

I don't know the technical specifics but I believe it does utilize it to an extent

If your ONT accepts an ethernet connection and doesn't require your ISP router to be used then that should be fine If your extender is able to select the WiFi it wants to connect to then yes it will work

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

Send me also

Thanks again, the team will take a look on Monday and do more testing overall

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

Ha ha, I've been doing exactly the same thing, my geo filter allows Spain, Saudi and the east coast of America (I'm in the UK) and the experience is mostly more "relaxed" than using local servers. I don't know why the Spanish server seems to work for me ,it's the exception but yes 100 ms ping works for me 👍

I've added you to Early Access so you can try that firmware to see if it works better for you but otherwise we are aware and working on a fix. In the meantime you could take it out of bridge and put the R3 in its DMZ instead so the R3 doesn't handle PPPoE and the issue won't happen https://forum.netduma.com/forum/151-netduma-r3-early-access/

The workaround I use is this . I am able to successfully upgrade to the latest version with these steps, replacing step 3 with the latest firmware. This solves that PPPoE issue for me.

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

Le plus simple est d'utiliser la sélection personnalisé par pays ! Et mettre le ping à 0

On Windows, there isn't much you can do about the network. You can tag your applications with DSCP tags if your router supports packet prioritization using DSCP. Some people optimize their Windows using the registry. Google is your friend, but if you want, you can test software. Windows: Resource Monitor (resmon.exe) allows you to see which processes are consuming bandwidth. Third-party tools like NetLimiter or cFosSpeed allow you to limit or prioritize certain applications. Router: All routers these days, or 99% of them, have QOS. QoS → its main role is packet classification and prioritization (e.g., gaming > voice > download). Bandwidth control → is achieved through mechanisms such as HTB (Hierarchical Token Bucket), HFSC, or FQ_Codel/SQM, which manage efficient throughput distribution. To be more technically precise: QoS ≠ direct throughput management → it's a "who comes before whom" logic in the queue. HTB or equivalents → allow hierarchical classes to be defined with minimum and maximum bandwidth allocations (per user, per IP, per protocol). In modern routers (e.g., OpenWrt), the two are often combined: Classification (QoS) → to identify sensitive flows. Scheduling/Shaping (HTB, FQ_Codel, CAKE) → to efficiently allocate and limit bandwidth. So, to put it simply: QoS = packet priority. HTB/HFSC = bandwidth control = actual bandwidth allocation. For gaming, both are very important, especially if you're playing on a PC. Having a 240 Hz monitor isn't enough. Optimizing Windows is important to avoid input lag in games. And when it comes to networking, there's no magic formula: a very good ISP connection and a good router to prioritize game packets and other... In your case, that's gaming, especially Call of Duty. This means you need to make sure your game takes priority over other tasks. No packet loss, no buffering, and no excessive ping; your game remains the top priority, even when downloads are overloading your bandwidth.

Bullpoopy? My K/D went from 1.3 to 3 after fixing my connection. The R3 isn’t perfect, but QoS + geofilter do work. I also mentioned other relevant stuff in the process. Not a waste of money for me. Don’t do what I did and use the Netduma in PPPoE — that’s nonsense and actually a waste of money!