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

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

thank you for the help!

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

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.

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:

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

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.

There won't be no. It'll just be security fixes then, it's unlikely it's based on 3.3, I think it probably reached end of service before they did it.

That fixed it. Thanks, Fraser.

Invite de commande ping 8.8.8.8 https://www.ionos.fr/digitalguide/serveur/outils/commande-ping/ —- Mettre le PC en filaire derrière le R3

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.

Thanks a lot!

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

Thank you i appreciate it 🙏

Auto will work when you're gaming (assuming that's what you're prioritizing on SmartBOOST) so you don't need to set it to Always

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

Manual is way better, ping optomizer gets it wrong most of the time for me and you have to keep using it everyday incase your congestion changes. Manual I just set it to as close to 0 bufferbloat as possible and that's it done.

You are the best! Thank you!

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

We've not had anyone have this issue before and in those scenarios it's usually some unique aspect of the persons setup contributing to the issue, it's likely we'll get to the bottom of it with continued troubleshooting but if you'd like to return just email us and we can go from there.

ok I will try this tomorrow

Obrigado

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

Blocking devices using bandwidth when you're playing etc is an extreme measure, as long as you have Congestion Control setup and SmartBOOST set to prioritize you then they won't be causing any issues

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

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 .

Hi Krush and Fraser thank you both for replying . This is what I got earlier but can try Speedtest aswell.

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?

The Congestion Control aspect is codel & our own proprietary algorithm I believe

So what I dont understand.... When using Exit Lag, youve said your pings haven't changed but when using Exit Lag you now also get lag spikes for 2 - 5 seconds (that is crazy long!). So tell me, what benefit is Exit Lag giving you as from what youve said already, it's giving you MORE issues?

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.