Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation since 05/16/26 in Posts

  1. 4 points
  2. It's not unlikely it will come back at all. It will be updated again
    2 points
  3. The R2 was sold with DumaOS 3, DumaOS 4 wasn't advertised as a reason to buy the R2, it was developed on the R3 itself and to get it on the older R2 hardware was a challenge that we didn't need to do but wanted to for our customers. We've explained why there have been delays and this hasn't just been for the R2 either. We never promise firmware because it's always subject to change, I've said many times we don't provide ETAs. The next R2 DumaOS 4 firmware would be the final firmware so the more time we take the more stable it will be overall. Also it is a support forum so there are only people posting issues here.
    2 points
  4. 1 point
  5. Hello. I am wondering what basic settings on the R3 that minimize and bloat and help my bullets nuke. I want to stay away from geo fencing though as I like to connect to all servers. Any settings I should specifically change or turn on/off? 2.5GB down, 300 up. Thanks.
    1 point
  6. That's fine then. No that's not true, you're not going to stress the system too much by lowering the percentage lower than 90%.
    1 point
  7. I've given you Early Access with the latest version being here: https://forum.netduma.com/topic/60946-new-r3-firmware-dumaos-401147/ As above for MAC cloning
    1 point
  8. Devastate

    Mac address cloning

    MAC address cloning can be found by navigating to Settings > WAN > Advanced > MAC Address Cloning.
    1 point
  9. 1 point
  10. Si..ho incluso il Giappone ... Ok...elimino tutti i server che ho nelle liste... Riprovo e ti faccio sapere☺️
    1 point
  11. If you're not using the Geo-Filter then it's not going to be possible to get the best experience more often than not. Otherwise that leaves you with Congestion Control to attempt to get results like the above - just keep fine tuning/testing until you get the best values. Then SmartBOOST to prioritize the devices/services for gaming.
    1 point
  12. It needs to be updated via the cloud which is what we will do, it should be done early this week
    1 point
  13. get you a good bufferbload first. I think its the most important thing you could do. here is mine
    1 point
  14. Could you switch the interface language back to English then provide another screenshot of what you're seeing when it happens and include a screenshot of the Geo-Filter settings menu please?
    1 point
  15. No worries, as long as Geofilter is working. I'm good. Thanks again.
    1 point
  16. KOAO

    DumaOS 4 on the R2

    I'm part of the Early Access for DumaOS4 but I can't find the file for that. Any help with that? Edit: Nevermind, lol. My fault.
    1 point
  17. I've asked them to update it today so hopefully they will have the time to do so
    1 point
  18. 1 point
  19. Thank you I appreciate you
    1 point
  20. OK - the WiFi Optimiser seems to be working more than 24 hours for the first time. I'll see how long it goes but this is a positive development!
    1 point
  21. Thanks I think this worked.
    1 point
  22. I see. Thanks for your swift response. Much appreciated 👍🏻
    1 point
  23. Em qualquer horário, mais no momento tudo está ok.
    1 point
  24. Okay good. Are you getting this at peak times or off peak times as well? You don't need to do both, one or the other is fine
    1 point
  25. Thank you I will upgrade asap
    1 point
  26. Hey thank you! That solved the issue nat type is now fixed!
    1 point
  27. Have you upgraded to this version yet? https://forum.netduma.com/topic/60946-new-r3-firmware-dumaos-401147/ If not I would highly recommend doing so to see if you get any of the same issues. The fact that you need to wiggle a cable around to make it work would indicate to me that it's probably a faulty cable and replacing that would likely fix it. Can you provide a screenshot of the LAN Settings page and the logs from when the issue happens if you still get the issue on that firmware please?
    1 point
  28. What do you want it to be? I'll change it for you
    1 point
  29. Thank you. I will wait for the update.
    1 point
  30. It keeps getting out of date, I've asked the team to update it again
    1 point
  31. R2 is outdated, forget about it.... the last update was a beta test of DumaOS4, which is almost 2 years old now, and there haven't even been any improvements to the stable version since.... their focus is on R3! They promised a version in December, I don't know if it will be beta or final, but so far nothing!
    1 point
  32. Parece ser uma boa ideia vou testar.
    1 point
  33. If it's just during peak time when it drops for example then that's just peak time congestion so I'd say leave it at your normal speed unless you're frequently playing during that time. If so or it's happening a lot of the time then setting to around 425 for the middle ground would be a good idea
    1 point
  34. It's best to tell it the speeds you actually have/expect so it's working with the correct information, otherwise you are unnecessarily throttling which could have the opposite of the intended effect.
    1 point
  35. Hi, There are a lot of known issues with latency issues in this year's Call of Dirty; many have stopped playing due to the mess. I tried everything to get it better, but no matter what I did, it was always the same, back a few years ago. It has been like this for years with COD, and it won't be changing any time soon. I stopped playing COD at the end of MW3, and many other friends did the same. COD is not what it used to be, and there isn't much the Duma can do to change their mess right now. It may change with the new engine update with MW4, but time will tell. (Not hopeful at all). I am sorry to be the bearer of bad news, but nothing will help; you will get replies from others that may offer some help. I took a lot of advice, and nothing worked
    1 point
  36. @scbba Show exactly what you’re seeing, maybe. But I play at 40 ms and cook most above-average players with a 2+ KD, and that’s while playing ranked, not casual pubs. Anyone can have a high KD running through bots nowadays, especially in potato CoD with VM lobbies—wannabe streamers with their little dongle devices. I haven’t touched CoD in ages; I retired after BO4, especially after cheating got so bad with free-to-play. It could also just be a network issue. Have you run PingPlotter results?
    1 point
  37. @scbbaI would just disable steady ping if you’re just seeing a variance of 5ms. That’s normal. You’re just adding extra latency for no reason. Steady ping is only needed in specific cases.
    1 point
  38. Benam

    DumaOS 4 on the R2

    Can you please add me also, Ive moved to a new hosue where I can actually use my r2 now!
    1 point
  39. If its worse then it's not setup correctly, please make a new topic with what you've changed on the router and we can go from there
    1 point
  40. The game feels so backwards right now. From what I’ve noticed, the lower your ping is, the more you get handicapped and the desync is actually crazy 😭 My sweet spot has honestly been around 30–60 ping lobbies. Anything lower just feels off for season 3 MP
    1 point
  41. i would to Feature Request an Addition of "Full Cone NAT" / "NAT Filtering: Open" Toggle The Problem is Currently, the Netduma R3 (DumaOS 4) lacks an explicit "NAT Filtering: Open/Secure" toggle. While the R3 supports PCP and UPnP, these protocols often result in a "Moderate" NAT type on PC for games with Peer-to-Peer (P2P) architectures, most notably Grand Theft Auto V. Symmetric vs. Full Cone NAT: By default, the R3 appears to use "Restricted" or "Symmetric" NAT filtering. While this is secure, it is incompatible with many P2P matchmaking systems. Even when ports (like UDP 6672) are opened via PCP, the NAT remains "Moderate" because the router only allows incoming traffic from the specific IP/Port that the PC first contacted. The "Full Cone" Requirement: For an "Open" NAT in GTA V, the router must support Full Cone NAT (Endpoint Independent Mapping). This allows any external host to send packets to the internal PC via the mapped port, regardless of whether the PC has messaged them first. Regional Necessity (Australia/Oceania): For players in Australia, the player pool is smaller. A "Moderate" NAT limits the number of successful P2P handshakes, leading to much smaller or empty lobbies, "Timed Out" errors, and increased latency. when playing with some other friends i previously had no issues with, since i had a router that allowed me to set Nat filter to open. An "Open" NAT is not just a label; it is a requirement for stable connectivity in isolated regions. The Solution here is I am requesting the addition of a "NAT Filtering" toggle in the WAN settings (similar to those found on Netgear, ASUS, and TP-Link hardware) that allows users to switch from "Secured" to "Open". because DMZ is not an answer: Using the DMZ is a "sledgehammer" approach that exposes the entire device to the internet. A "Full Cone NAT" or "Open Filtering" option provides the same connectivity benefits for gaming while maintaining a higher level of security by only affecting how active port mappings are handled. so for goodness sakes add this feature, it would actually help MANY people out with the multitude of complaints about Nat type open and especially for an issue like one console having open Nat and the other 2 having moderate or strict
    1 point
  42. Hey Netduma fellows, Hope you’re all having a great day! I wanted to share the best settings I’ve found for improving my online gaming experience. Now, I’m not sure if the Netduma team will be happy about this because, honestly, none of these settings are related to the Netduma router. I’ve been using Netduma routers for over five years, starting with the R1 model. Sometimes, they performed great; other times, not so much. Over time, I began to question whether using QoS alone was the best approach—until I was introduced to SQM (Smart Queue Management). Some of you might already be familiar with SQM, CAKE, and FQ_CoDel, but let me tell you—SQM is an absolute game-changer when running on high-performance router hardware with OpenWRT. My Solution for Consistent Performance The key to getting good, consistent results (which has helped me maintain a 3+ K/D ratio in every FPS game) was: 1. Using a high-performance router that supports OpenWRT 2. Enabling CAKE as the QoS algorithm Since CAKE requires significant CPU power, I chose the Flint 2 router, which can efficiently shape over 500 Mbps of traffic while running CAKE. The Best Part? Set It and Forget It The only tuning required is adjusting overhead and MPU (Minimum Packet Unit) settings. Other than that, once set up, it just works. That’s all I wanted to share. Hope this helps someone out there struggling with network consistency!
    1 point
×
×
  • Create New...