Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation since 12/28/25 in Posts

  1. You just admitted it lag spikes when using it though??
    3 points
  2. 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.
    2 points
  3. I appreciate the info and it helped a lot! Happy to be part of the Duma gang again.
    2 points
  4. Sorry to hear that! We don't give out any ETAs but hopefully not much longer for one
    2 points
  5. 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!
    2 points
  6. 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 . .
    2 points
  7. 2 points
  8. 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
    2 points
  9. Dirtytamato

    2.4 enabled devices

    Ya I've addressed all of this. Thanks though
    2 points
  10. 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.
    1 point
  11. 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.
    1 point
  12. thank you for the help!
    1 point
  13. Ok grazie per le tempestive risposte. Buona serata
    1 point
  14. I think there is some improvement but may not get you all the way, I've added you so you can check
    1 point
  15. 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
    1 point
  16. 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:
    1 point
  17. Obrigado.
    1 point
  18. 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?
    1 point
  19. 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.
    1 point
  20. 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.
    1 point
  21. cbntlg

    BO7 won't load

    That fixed it. Thanks, Fraser.
    1 point
  22. Please upgrade to the Early Access version and see if it still occurs - once it's fully upgraded factory reset then monitor it
    1 point
  23. As above I wouldn't rely on that, try this instead https://support.netduma.com/frequently-asked-questions/legacyfaqs/test-your-ping/
    1 point
  24. Ça donne quoi, si tu fais un ping vers 8.8.8.8 sur ton PC ?
    1 point
  25. I'm in the same boat, let me know if you can
    1 point
  26. No worries at all, do keep us updated and any questions/issues just ask!
    1 point
  27. Yes that’s correct no mate no issues with geo filter after factory reset.
    1 point
  28. Thanks a lot!
    1 point
  29. Hey there once again @Netduma Fraser Here are a couple more i’ve saved up: 180E27B CGNS86 180EBMD 180E2GO 180E2FE 180ED0J
    1 point
  30. 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
    1 point
  31. Thank you i appreciate it 🙏
    1 point
  32. I'm sure it's easily resolvable, let us know if you want to continue
    1 point
  33. Fixed it, had nothing to do with the Netduma, can be closed. 🙂
    1 point
  34. You are the best! Thank you!
    1 point
  35. Netduma Fraser

    Vlan

    It's the WAN side yeah, so you're wanting it on the LAN side then? I can make the request to the team
    1 point
  36. 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.
    1 point
  37. Rodolfo Lima

    A doubt

    Obrigado
    1 point
  38. Netduma Fraser

    A doubt

    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
    1 point
  39. 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
    1 point
  40. 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.
    1 point
  41. I tried what Capoeira82 suggested with the marking on the map and so far it works. It seems to be the solution.... Thanks.
    1 point
  42. Ok thank you. I'll follow up when I get an extender
    1 point
  43. 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 !
    1 point
  44. As above, do the speed test on speedtest.net, do you get your expected speeds then?
    1 point
  45. Salut ! Tes tests de vitesse sont faits via l'outils Netduma ou derrière un PC en filaire via ookla ? L'outils Netduma utilise parfois des serveurs de test de vitesse non optimisé, le mieux est de rentrer manuellement les vitesses max données par ton FAI !
    1 point
  46. 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?
    1 point
  47. Netduma Fraser

    QOS

    The Congestion Control aspect is codel & our own proprietary algorithm I believe
    1 point
  48. damir117

    Battlefield 6

    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.
    1 point
  49. Netduma Fraser

    Battlefield 6

    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
    1 point
  50. 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.
    1 point
×
×
  • Create New...