Leaderboard

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.

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.

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.

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

I'm thinking about that. I hadn't too much problems with v4.0.258, really. I only use that for Warzone.

Good to hear! If you download the last DumaOS 3 update, then just upgrade to it from the interface. Hard to say, I don't think 4 on the R2 is too unstable really. Whatever works best for you!

ok I will move the geo filter around this week and report back this weekend

Your ping sounds fine and it's unlikely you're experiencing any congestion so I think forcing some different servers might give you a better experience

To force servers you need to do the following: It's essential the Geo-Filter is enabled before the game client (e.g. Steam etc) if on PC or platform (e.g. Xbox, PlayStation) or the game have been launched. If you change Geo-Filter settings when you're on the game then you will need to restart the game for those changes to take effect, otherwise it will use the previous Geo-Filter settings and appear not to be working. For settings ensure Ping Assist and Geo-Latency are disabled in the Geo-Filter menu that can be found by clicking ⋮ in the top right hand corner of the page and go to Settings. Strict Mode should also be enabled, it is enabled by default so if you haven't disabled it you can ignore it. If you have disabled it or want to check it can be found in the same Settings menu as above or in Settings > Troubleshooting > Advanced > Developer Options depending on your firmware version. Fast Search should also be disabled which it is by default so can be ignored if you haven't changed it, otherwise this can be found in the same place.

Honestly, just having a 2.5 Gb Wan port would be a good enough upgrade for me as my 1 Gb AT&T fiber actually comes in at 1.25 Gbps. Would allow to use all available bandwidth. No actual devices other than my desktop pc have a 2,5 Gb port so the extra bandwidth is negligible. I guess I can say I have been lucky with the R3. I have not had any hardware issues with it like I had with the R2. My R2 eventually went into a power up boot loop and basically became a paperweight at 3 years old. I also had Wi-fi issues with the R2 but nothing like that with the R3. Fortunately for me though, my entire home is hardwired into every room. And anyone who buys a Netduma router is buying it for DumaOS. There is no other reason other than that to buy a Netduma router. So let them focus on getting the software right. That is what we paid them for.

No one usually posts a bad gameplay video to YT!

Yes correct. It's available to some users but not you. Just wait for it to be released.

They change servers every so often so what you experienced can happen, we then whitelist and it'll happen again at a future date, always a bit of cat and mouse really! Though you have prompted an idea that might help with this so I've relayed that to the team. You'll only see servers in a few different circumstances, with some games such as CoD you may see all servers, apart from those within your radius when you first launch the game. Then when you search you may see servers outside your radius being blocked. Then when you're in the game you should only see the game server you're playing on and potentially the auth server.

This is essentially what we're working on currently, one of the big features we've referred to - ACC (Adaptive Congestion Control), there is some very limited information about it here: https://netduma.com/blog/how-to-fix-bufferbloat

MERCI

We've been hearing about this for half a year, it's like waiting for Santa Claus on his reindeer who won't show up. Or is just prolonging time to the next release of new router to be honest 😂

Problem solved. It turned out to be my controller disconnecting from the console. That was causing the PSN and Call of Duty logouts. This was not related to the NetDuma R3 in any way. Thanks for the assistance — case can be closed.

Yes you will, we've spent a lot of time and resources on these new features so yes they will be coming

Buongiorno, volevo delle informazioni precise riguardo il settaggio del qos, cercando su internet ho visto che è consigliato per le ftth stare tra l 80% e il 90% e non necessariamente stare in bufferbloat a+ questo perché se per raggiungere a+ dovessimo scendere sotto la soglia del 80% in giochi come warzone verrebbe aggiunto un jitter artificiale, che ne compromettere la fluidita e l hit reg del gioco. È reale tutto ciò sapete dirmi qualcosa di concreto

Hi, Normally on a City Fibre connection you would need the username and password plus the VLANID. (At least that’s been the case on the last three City Fibre connections I’ve had.) VLANID could be 911. Your ISP should be able to give you the details for all of the above credentials. As @Krush shows above, if you’re already in the main Duma OS console. Then go to Settings > WAN, then select PPPoE, then pop in your details. *The VLANID is under the advance section of the WAN settings (on some firmware). Please note, it may take a few minutes for the City Fibre connection to establish once you fill in the details and save. You may need to reboot the router if you see no connection after say 10 minutes. Hope that helps.

If it's working without the Geo-Filter enabled then it'll 100% be those servers that need to be added, they can appear and disappear very quickly. Either way the team will investigate and resolve it via a cloud update as soon as they can.

Obg

Yes that's normal

No, we keep the current game and last game on there so when 7 came out we would have removed MW3. The servers are essentially all the same anyway.

Ill try it out

Hi! I've been working hard lately to get my Netduma, including Deco's Wi-Fi mesh, working. I've searched extensively for the correct settings and have found them. I'd like to share them with you. Here are both my Wi-Fi and wired results. First my WIFI results My wired results

Vous bloquez le serveur d’accès situé en Irlande ! Sans ce serveur d’authentification , vous ne pouvez pas accéder au jeux ! C’est un comportement normal lié au geofiltre.

Can you try the following please: Toggle "Reduce Transparency": Go to Settings > Accessibility > Display & Text Size and check "Reduce Transparency". If it is ON, turn it OFF, as this feature has been known to cause UI glitches and crashes with the new "Liquid Glass" design in iOS 26. If it's OFF, leave it OFF and ignore the rest, as that wont be the issue. Then launch the app, and see if that works, please.

Okay, so for you, "problem" rhymes with "breakdowns" in the IT world, which you clearly don't know much about, especially here, since it's supposed to be a gaming router, so latency and other factors should be optimized as much as possible. Well, in these logs, that's not the case. The router, especially the processor, is working unnecessarily and haphazardly, which affects the stability of the system and therefore the router... Basically, just because your car starts and runs doesn't mean it doesn't have a problem... But since it's you, I can understand.

@18RayFYour case is uncommon but not unheard of. What stands out is that you're using DHCP, which typically operates with an MTU of 1500. However, your ISP is clearly providing an MTU of 1492, commonly seen with PPPoE, and when the MTU exceeds the limit set by the router, fragmentation occurs, which can lead to issues like the one you experienced. In other cases, this might manifest more noticeably, such as through packet loss. It is not an issue on the router side as the router uses the most common configuration. @KinGzzyMost of what you said isn’t even an issue; the time going backwards is literally just the DPI reading the packets, and as you are using the AI, which you are, it doesn’t tell you the most obvious thing, which is that IPv6 is disabled.

No, you can't do anything; you have to wait for him to pass the information on to a Firmware (Embedded) Developer.

Disabling DHCP prevents the router from dynamically providing IPs to devices - you should only ever disable DHCP if you have given devices static/reserved IPs either on the router or the device itself. It is likely that when the DHCP lease tried to renew that is when the issue became known. You do not need to disable DHCP for any performance gains.

Ok grazie per le tempestive risposte. Buona serata

BO7 uses under 500kB/sec down and under 200kB/sec upload (5Mbps/1.6Mbps) on minimal texture streaming settings. Probably double once you bump the texture streaming up. There is a spike however at the beginning of each match as you load in (probably downloading initial textures, assets etc.) this is with looking at traffic captured via Wireshark, so there could possibly be a bug with the amount of bandwidth being reported? I regularly see "stats for nerds" allocate around 1.2Mbps to BO7 so i'm surprised it's running

Gaming requires very little bandwidth so the amounts shown are actually accurate but if disabling it works better for you that's fine, we just provide the tools, it's up to you how you use them. You could also try disabling gaming and prioritizing the device instead.

You're right. My bad. I just thought that the XR500 bricking issue was kind of a known thing. At any rate, thank you for your support over the years. I've read a lot of stuff you've written here and there, all of it is top notch stuff.

To get an Open NAT you need an open route to the internet, with the setup you're going to use you would need to put it in the DMZ to do that. It's perfectly fine to do so, the R3 has its own firewall so it is protected

You've had a lot of good advice so far but to summarize: If you want to use all of the R3 functions, i.e. QoS, SmartBOOST etc then you need to do either of these options: If you only care about using the Geo-Filter then what you suggested originally will work:

I tried everything for this and I actually found the work-around by accident. I'm on a PS5. On the Geo-Filter tab, on the far right side, click on the tab that is for the console that you're using. Disable filtering-enabled. As soon as the game starts loading you in, you can re-enable it. Most times you are able to close the game and start it back up with no problems but I found that I had to do this at least once a day. I also found out how to stop this from happening. Before you re-enable the filtering tab, look at your map fully zoomed out and locate the Dublin servers which should be near the top in the middle of the map for those who aren't refreshed in their world map knowledge. Click on the Dublin server and in the upper right hand corner, click on the check-mark to allow it. I personally had to click on and allow 2 different Dublin servers because after I allowed one, it did it again and I looked and found there to be a second one, which I allowed as well but after that I have never had that error message pop up again.

Obrigado.

Either way, it's up to you, there won't be any conflicts

This isn’t a support post, this is just a post from a hardcore call of duty ranked player giving my honest review of the router. Because ive been seeing soooo much negativity about this router. Ive been playing ranked play on call of duty modern warfare 3 on pc for about 8 hours a day. I can honestly say the netduma r3 melts my enemies. I’ve tried multiple different routers so I know how each router feels when you’re playing competitively when every millisecond counts! I’ve tried Openwrt, Ubiquiti, Arista, Mikrotik, Pfsense and Asus ROG routers. They all do very good A+ 0ms bufferbloat with QOS. BUT the problem with those routers is the hit detection / lag comp. Where you clearly see the enemy and shoot them first and you die first. It’s like you shoot nerf bullets and they just INSTA DELETE you! I don’t know how netduma does it but this router is manipulating the lag comp / hit detection to give you a advantage. I mean theres still some moments when I’m like how did I lose that gunfight but it’s ALOT less compared to those other routers. The latest firmware still has some bugs that I’m sure is going to be fixed.. but the firmware is more than playable for me Anyone else feels this way or its only me?

I’m going to push back on this a bit, because the conclusion being drawn here doesn’t line up with how online games or networks actually work. I’m an Enterprise Lead Network Engineer with over a decade of experience designing and operating large-scale, latency-sensitive networks (factories, global WANs, DCs, SDN, etc.). I am also a professional competitive CS2 and FortNite player. From a technical standpoint, a consumer router cannot “manipulate lag compensation or hit detection” in the way you’re describing. How hit registration actually works: In modern multiplayer shooters (including CoD), hit detection is authoritative on the game server, not the client and certainly not your router. The general flow looks like this: Your client sends input events (movement, aim, fire timestamp) The server rewinds game state using lag compensation The server determines whether a hit occurred The result is sent back to all clients Your router never sees: Player hitboxes Server reconciliation logic Lag compensation algorithms Damage calculation It only sees encrypted UDP packets with timestamps. (along with a few checksums that are used on the backend to determine whether there has been any manipulation to the data stream, but that is entirely dependent upon game and AC used). What lag compensation really is Lag compensation exists to normalize different client latencies, not to “reward” or “punish” certain players. If two players fire at nearly the same time, the server rewinds state to each client’s perceived moment and resolves the outcome. This can feel unfair at times, but that’s a function of: Tick rate Interpolation / extrapolation Server load Packet arrival variance Player movement prediction Not the brand of router. What routers can affect (and what they can’t) At Layers 1–5, almost every modern router you listed (OpenWRT, MikroTik, pfSense, Ubiquiti, Asus, NetDuma) is doing the same fundamental job: NAT Stateful firewall Packet forwarding Optional QoS / shaping This is the ONLY thing that you might be able to argue NetDuma does 'better' than others. However, that is merely if they do it 'out of the box' vs. others that may not considering it's all adherent to RFCs and standardizations, dscp values, etc. If bufferbloat is already controlled (which you explicitly said it was), then: Latency is stable Jitter is minimized Packet loss is negligible At that point, there is no mechanism for a router to selectively improve hit registration. It cannot reorder server logic, alter rewind windows, or bias combat resolution. If it could, competitive esports would ban consumer routers overnight. Why it feels different Perceived improvements usually come from: Different matchmaking servers or routes Temporary changes in server load Variance in opponents’ latency Session-to-session network conditions Confirmation bias (especially after hardware changes) Humans are very good at pattern-matching and very bad at controlled experiments, especially when adrenaline and competition are involved. The key point If a router could truly “manipulate lag comp”: It would be detectable by the game developer It would be considered cheating It would be patched or blocked immediately No consumer router has access to the data or control plane required to do that. Final thought If you’re enjoying the R3, that’s totally fine. Stable latency and good QoS do matter. But attributing gunfight outcomes to router-level manipulation of hit detection isn’t technically accurate. The network delivers packets. The server decides who lives and who dies. Everything else is perception.

Putting yourself in 100ms ping lobbies is setting yourself up for a major disadvantage either way you look at it 😂😂

Added

For anyone anyone that wants good hitreg on BO6, this is my setup based on 1Gbps fibre Internet. 1. I've set congestion control to 50.5% for both up and down which gives me the best bufferbloat results. When tuning for Bufferbloat, pay attention to Jitter. Try and get it under 10ms. I managed to get mine under 3ms as I have very good Internet here in my country. 2. Set Congestion Control to Auto or Recommended. I keep mine on Always On unless I have big downloads. 3. I only prioritised Call of Duty (Series) for Apps and my PC for device. You don't need to prioritise Call Of Duty (Content) as @YT_LowPingKinghas mentioned in his videos Call of Duty (Series) covers Call of Duty (Content) as well. Focus on getting your Jitter as low as possible. I've noticed tremendous consistency and crispy hitregs just by doing this. I've uploaded a video of my gameplay and its been very consistent from game to game. Do give it a try and hope this helps. Nothing complicated to setup as the router does everything properly with 540 firmware but Geofilter is kinda broken now as it doesn't indicate which server on the map its connecting to anymore. I hope this can be fixed in the next update. And do factory reset your router after upgrading to 540 firmware. I got away without doing factory reset last few updates but 540 firmware wasn't having it. Had ping spikes and weird issues until I factory reset and it was GOLDEN.

im almost on your route..

The R3 does it's job but it can't magically make your bullets register how they should, that's up to the game and your opponents - the matchmaking doesn't prioritise the connection of your opponents, so when you get connected to laggy people from across the country most of the time, you're going to get poor hit registration no matter what router you're using. I sit single digit pings but get penalised heavily, the game just feels delayed when there's people with crap connections in the match. If everyone's under 20ms (rare) it feels amazing. They've tried to make the game playable for everyone no matter your ping but it's not perfect, there's a reason why people geo filter to servers further away to increase their ping, or why some Japanese/Chinese connect to the Australian servers on purpose. MWIII has given me the worst experience i've had in cod in a long time. My KD is around 2.8 now but I was probably negative the first 2 months from how awful it ran. That's the lowest i've had since like OG MW3 and I'm surprise it's even gotten there with how bad it runs. The only router that has made this game remotely playable is the R2 or R3 - no other router has given me playable matches until recently, I decided to switch to my old Asus router I was running as an AP to router mode and it has been giving me some smooth hit rego. It's running Merlin firmware, I have no fancy settings, just set my console to priority and using Adaptive QoS with my full bandwidth set up. I have found matches run bad if I throttle bandwidth low, unlike some of the older cods. Some people that I occasionally play with have no issues whatsoever playing via WiFi and they're sitting on 30-70ms ping due to their location. When I vs them for fun in public lobbies, they have the type of connection where you're dead before you can ADS.. they are just synced to the server much earlier than you and have the lag comp on their side. I've tried bumping up my ping but it doesn't give the same experience as having a high ping by default. Maybe it's related to the routing.

It's available on the latest firmware, please update to that and you'll be able to do this.