Leaderboard

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.

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.

You can leave it enabled

Thank you I appreciate you

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!

Thanks I think this worked.

I see. Thanks for your swift response. Much appreciated 👍🏻

Em qualquer horário, mais no momento tudo está ok.

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

Ok...grazie tante ☺️☺️☺️

Thank you I will upgrade asap

Hey thank you! That solved the issue nat type is now fixed!

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?

What do you want it to be? I'll change it for you

Thank you. I will wait for the update.

It keeps getting out of date, I've asked the team to update it again

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!

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

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.

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

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

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

Its like the normal filtering, servers inside your radius are allowed, outside are blocked but it just does it using a different approach. It can also help to prevent any cases where on games where the game ends and you can just stay in while it puts you into another sometimes you can get kicked to the lobby if it would be outside your radius usually but instead it would keep you in. So sometimes you can get games outside your radius if the game is persistent in wanting to put you in it.

Well that's great to hear! Do keep us updated!

No...questo non l'ho fatto perché uso il tplink solo per il wifi.... Proverò appena posso, ma l'unica cosa che posso dire che con il netduma ho risolto tanto problemi. Ti terrò aggiornato ☺️☺️☺️

Thanks for the heads up Fraser. GEO is working again for me, the Heatmap is actually not that important to me, if the GEO works, all good.

Good response above - it's one of those suggestions that float about the internet but in reality won't make a difference and if it does then it's almost certainly a placebo

I still have my R1 from 2015 that i purchased for Advanced Warfare.

Changing DNS is not going to improve ping or fix server issues. All it does is help you find information quicker. The closer a DNS server is, the better, and the more servers there are, the faster you get information. No, routers do not find the “best” DNS automatically—they just use whatever is given to them by default, which is typically your ISP’s DNS if you’re using DHCP.

I have the same issue + my GEO fence is not working when the Ping-Heatmap shows below picture. This is only the case for CoD. Can someone from the team check on it?

Ok..proverò a collegare tutto i dispositivi su netduma ..ti aggiornerò più tardi..grazie ☺️

That worked thank you so much. It was an ireland one like you said. Server ID was 1FD98CG

Okay so there will be a server that appears blocked on the map when that happens - almost certainly in Ireland, if you allow it then it will let you through. You may need to do it a few times, i.e. each time you load the game but once you've got them all it'll work normally without Geo-Latency enabled. If you could also provide the ID of the server(s) it is then we can add it to the global whitelist.

Thank you > I did make a new thread topic with reply. Thank you for your quick response

You should disable Geo-Latency and then ensure you're only covering the servers that are giving you the lowest ping. If they're too close together to do so then as you play them add them to your deny list so you build up a list of denied servers and you will play on the lower ping servers more often. You can also try using Ping Assist setting the upper limit to ~55ms which may do better.

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

The closest server to you is the Warsaw server so I would expect that the 23ms you're seeing is to that server specifically and otherwise you're connecting to a server further away. So yes in theory getting the router to utilize the Geo-Filter would allow you to force the Warsaw server more consistently. However, I will provide some caveats so you have the full picture: I'm presuming that the Warsaw server is the server giving you 23ms, it might be that in private matches it is relying on a P2P connection instead in which case this wouldn't be accurate and you're actually seeing 23ms to a person in your match instead. If that is true then your normal ping could already be to the Warsaw server or another and so may not be able to be lowered. The Warsaw server isn't one I see very often so I couldn't say if it is one that is frequently used for online play. For example, the Milan & Madrid servers are notoriously hard to force games on, even for people that live close to them so it's not a guarantee you'd always be able to force it.

thank you

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

I think give it another factory reset and try again as it shouldn't be cutting out at that point without changing the details, if that doesn't work you will need to access via ethernet unfortunately

Will do, thanks

Thank you.

Okay let us know how you get on!

Added https://forum.netduma.com/forum/144-netduma-r2-early-access/

thanks man

Added

I will do shortly. Connecting to NA is fine on console only and crossplay. It’s just eu that I can’t find lobby’s in

It's worth trying a few times as it's not always successful right away. I have seen 2.4 & 5GHz give out in the past while 60 still works so that is likely unfortunately. We've not brought out our own router capable of those speeds at the moment sorry to say

I've given you Early Access so you can upgrade to the version that resolved it for the above user https://forum.netduma.com/forum/151-netduma-r3-early-access/

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