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.

Si purtroppo se connesso all ont devo per forza usare il pppoe capisco grazie mille

Muito obrigado por responder, tenha um ótimo dia.

No it's not necessary for you

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!

When it gets to the internet part of the setup selected the advanced options and then you can skip that part of the setup, complete the wizard and then you can get through to the interface. Then, reboot the Movistar, wait 2 minutes, reboot the R2 from the interface, wait 4 minutes and see if you get a connection then.

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

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.

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.

You can't setup to apply different locations/radius sizes etc for different games, this was something we were considering/looking into the feasibility of adding, it may come in the future.

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.

United Kingdom the service is called uswitch city fibre

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.

You can keep it enabled that's fine

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

got ya thanks.

There will be a blocked server when that happens, just zoom out on the map, run the test and you should see the server get blocked. Add it to the allow list and give us the ID and we can whitelist it. There may be a few servers responsible

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.

The longer the cable the more subject to interference it is but it's usually fine up to ~100 meters. However with such a long cable it is much harder to determine if there are any kinks or internal breaks for example

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

I think there is some improvement but may not get you all the way, I've added you so you can check

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’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 😂😂

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 . .

Added

Thank you, I'll pass it on!

im almost on your route..