Leaderboard

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

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.

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!

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

Thanks Fraser

Okay that's good then, the router isn't limiting you, it's just the speed test provider the router uses isn't always the most accurate so you can ignore that

Ya I've addressed all of this. Thanks though

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

Hi According to the logs, your router is suffering from major software instability. 1. IPv6 configuration problem (odhcp6c) 2. Script and TLS errors (cli.lua) 3. Time instability (Time went backwards) 4. Very frequent DHCP renewal (udhcpc: lease obtained, lease time 600) 5. Memory cleanup (drop_caches) USER root cmd echo 3 > /proc/sys/vm/drop_caches 6. Processor instability (Time went backwards) 7. The conflict with "DPI" (Deep Packet Inspection) In your logs, I also see: user.info dpiclass-daemon: Daemon shutdown user.warn overwatch: Changing category of appid=161... to VPN Your router is suffering from major software instability. This isn't just a minor connection error; it's the DumaOS system crashing because it's trying to handle too many things at once.

thank you for the help!

Ok grazie per le tempestive risposte. Buona serata

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

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.

Good to hear! DNS won't make a difference for gaming so unnecessary to change it. There isn't a backup settings function currently but it has been requested so may come in future.

Good to hear, don't forget the Early Access firmware as well

That fixed it. Thanks, Fraser.

As above I wouldn't rely on that, try this instead https://support.netduma.com/frequently-asked-questions/legacyfaqs/test-your-ping/

I'm in the same boat, let me know if you can

No worries at all, do keep us updated and any questions/issues just ask!

Yes that’s correct no mate no issues with geo filter after factory reset.

Hey there once again @Netduma Fraser Here are a couple more i’ve saved up: 180E27B CGNS86 180EBMD 180E2GO 180E2FE 180ED0J

To answer your questions: It's a NTGR feature so they don't consult with us when removing one of their own features but I expect so. Unlikely, they probably removed it intentionally. Check the DumaOS version on the System Information page if it starts with 3.3 then yes, if not no. Yes if you really want that functionality

Thank you i appreciate it 🙏

Added you both

I'm sure it's easily resolvable, let us know if you want to continue

It's the WAN side yeah, so you're wanting it on the LAN side then? I can make the request to the team

I’m using a Huawei CPE Pro 5 as my 5G modem. I’ve tested multiple bands and currently have the modem band-locked to the combination that gives me the best SINR and RSRQ, rather than chasing peak throughput. My goal was stability and lower jitter. My jitter has dropped to around 3–4 ms, compared to ~5 ms previously, without any changes on the R3 side. I’m assuming this improvement is related to tower load, scheduling, or band conditions rather than router configuration.

None. I've left everything default. Just to follow up from last night, I have updated to the new firmware and factory reset the router. Currently everything seems great! Played 3 rounds of bf6 so far with no micro stutters and no dosconects. the wifi status light are actually functioning now. I will update if somthing changes

As above the team will all be back tomorrow to continue work on it, as always we'll make a post with the firmware when its ready

As your title indicates, it has been new year and Christmas holidays very recently so Netduma staff would have been having a break with their families, just like you did I guess? Most companies return back to work tomorrow so I imagine the staff will continue working on the update from tomorrow.

I tried what Capoeira82 suggested with the marking on the map and so far it works. It seems to be the solution.... Thanks.

Ok thank you. I'll follow up when I get an extender

Hi Krush, I am playing on my own. Totally understand thanks again Pete

Oui c'est ça ! Vous jouez en équipe ? En fonction de la proximité du serveur la latence n'est pas la même entre les membres d'un groupe de jeu ! Le jeu utilise des serveurs dédiés, l'hôte n'est plus le relais comme avant sur du serveur P2P !

Okay thanks Fraser so all good with the Netduma R3 I was concerned trying to bring latency down for gaming I have made mistakes with Netduma settings .Playing between 26ms and 31ms latency but other gamers are saying they are 16ms so I believe they are closer to the server if that’s right .

Thanks

As above, do the speed test on speedtest.net, do you get your expected speeds then?

That's just log spam, we're aware of it, you can ignore it as it won't be causing any issues. You can reset if you like but it's unlikely to make a big difference. You're saying the connection is weak but are they experiencing any issues with the WiFi specifically?

Well I'm glad I'm not the only one with this issue. I think I will purchase a good wifi extender and go that route. But ya all my other devices connect, they are just weak. But thanks for your help

In Battlefield 6, only the UK, Ireland and Germany servers are currently available for Europe, which is clearly visible when you start the game without a geo filter.

We can't do anything about that necessarily, if they don't want to connect you to those other servers for whatever reason they won't. Could be they're only used in times of heavy load, when other servers are down etc

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.

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.