Leaderboard

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.

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

You can keep it enabled that's fine

Ill try it out

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

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.

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.

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

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.

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.

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

You shouldn't have a double NAT if the R3 is in the EE hub DMZ so I'd suggest checking the WAN IP on the R3 is the same as the IP entered in the DMZ. In that scenario if you need PPPoE for example then yes you can just put those details in and leave everything else the same. You may need to fine tune your Congestion Control settings a little more to get the same results you're used to but otherwise it would be fine. I would look into the DMZ thing though first as you can see reduced speeds and there is also a disconnect issue with PPPoE we're looking into. The R3 won't change any settings unless you change them so no need to screenshot. If you have a double NAT even after connecting to the ONT then you have a CG-NAT in which case you only have these options to resolve it: Get a static public IP from the ISP (usually a charged extra) Use a VPN (using a VPN generally gives you a moderate/strict NAT anyway, also an extra charge) Change ISP to one that doesn't use CG-NAT

Just updated and it seems like the issue disappeared, did not need to reset factory settings either. Interface loads way faster too. Thanks for the access.

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/

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

Ça donne quoi, si tu fais un ping vers 8.8.8.8 sur ton PC ?

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

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 🙏

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

Added you both

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.

Fixed it, had nothing to do with the Netduma, can be closed. 🙂

You are the best! Thank you!

Yep please can you ask for vlan routing also while applying QOS on each interface also please. Also not sure if people know but Vlans can help reduce max and 95th percentile latency , due to the fact that traffic is separated on different logical interfaces, each with its own ingress queues and burst absorption. This means Wi-Fi airtime chaos (retries, aggregation bursts, uploads from phones/TVs) is contained inside the Wi-Fi VLAN’s queues, instead of blocking or compressing ACKs for your wired gaming traffic. When the flows finally merge they’re already smoothed and paced.

Added

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

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.

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