All Activity

@Netduma Fraser I would like to change my display name. How can I do so?

Yea the same issue happens

Is Congestion Control set to Always or Auto? Have you found 50/50 gives you the best results or just randomly set? SmartBOOST should be used so the devices/applications you care about get prioritized above traffic you don't care about as much, if there was something impacting your ping results then this would help it. Given the ping statistics you provided, you had a maximum of 442ms but over 232 successful packets your ping averaged 22ms which indicates that you only experienced a couple of quick spikes rather than a consistently high ping and so it was relatively stable overall with 2 packets lost at just under 1% that's quite acceptable and I assume they would have happened with those couple of spikes which makes sense. So far then it indicates it's more of an isolated incident of spikes rather than a persistent one. The logs contain entries that can look like issues but are normal processes, that's why it's best for a user not to try to diagnose issues solely based on logs, if issues are occurring that can't be diagnosed through normal means then logs can be looked at for more information by the devs but its very rare this is needed and the entries you've mentioned aren't anything I haven't seen before. For example the hostapd entry can occur when Ping Optimizer fails and that could occur for any number of reasons such as the server times out and so it can't set the correct Congestion Control percentages etc. Some can appear when it's not using a certain setting but it looks like an issue because that setting isn't active and fails, that's what I mean by verbose, we're not heavily restricting the output to the log, normal processes appear there that can seem troubling if you're not used to them. cfront & RTNETLINK errors weren't in the logs you provided but again they're not necessarily any immediate cause for concern.

Check direct to your ISP modem/router to see if you get the same issue because if you do then nothing you do on the R3 would make a difference as it wouldn't be the cause

To clarify my setup: The Arris SB8200 (DOCSIS 3.1) feeds directly into the R2. The R2 is my main router for all wired/ethernet devices. I have a second router connected to the R2, but that is only used for WiFi devices — all gaming and primary devices are on ethernet directly through the R2, so all relevant traffic is going through it. To answer your questions: - Speeds: 120 down / 20 up, and yes those are entered into the router - Congestion Control: set at 50/50 for both upload and download - SmartBOOST: not currently enabled - The R2 is not in DMZ or bridge mode as it is the primary router — the SB8200 is a modem only I also want to flag some errors from my system logs that weren't addressed: hostapd is throwing "Failed to set beacon parameters" repeatedly every few seconds, cfront bottomch is constantly reloading interface IPs, and QoS is generating RTNETLINK errors. These seem like they could be contributing to instability and I'd appreciate those being looked at as well.

I factory reset my R3 and the problem still there lol I don't even know what to do at this point. I just wanted to shoot my gun. ggs only

If you've fully disabled the Geo-Filter and it's still occurring then check direct to your ISP modem/router to see if you get the same issue Yeah it's getting outdated very quickly at the moment, the team are aware and will push another cloud when they can

Falar nisso os servidores ainda não aparecem no ping.

I removed the Geo-Filter from now but still the same issues

Very likely an authentication server is getting blocked, look on the map when that error appears, look for a blocked icon and allow it. Repeat the process as it may take a few times then it will work. If you could provide the IDs also we can get them globally whitelisted.

Does anybody knows how to fix this BS?

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 did miss that part, my apologies. The logs are primarily for the devs to look at if needed and as such they're quite verbose, they contain backend entries that can look like issues but are normal processes. I doubt they specifically will be causing you issues but if it ends up that they are I can pass them on for more investigation. What is the model of the modem/router the R2 is connected to and how have you set that to ensure all traffic flows to the R2? E.g R2 in its DMZ, modem/bridge mode Are ALL devices connected to the R2? What are the speeds you pay for/receive & have you entered those speeds into the router? How have you setup Congestion Control? How have you setup SmartBOOST?

Seems like their track record looking through other issues from people in the forums.

While that may fix the connection error, you seemed to have not looked through the provided log files i uploaded. Why is hostapd failing every 6 seconds for 15+ minutes straight? Why are the interfaces constantly reloading? Why is QoS throwing RTNETLINK errors?

The dublin server is an authentication server required for online play so you may need to allow servers appearing blocked there a few more times and then it should work just fine. If you could then provide the IDs we can get the cloud updated with them.

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!

Hi. Is there an update on this issue. Mine is still not working. Please help.

Hello everyone! It has been a while, but I’ll try to make this as detailed as possible. I noticed we are on the DumaOS 4 web GUI, as when I plugged in my R2 for the first time in about a year, it showed it. I factory reset it and got it connected. I noticed the speed test in the auto setup wizard wouldn’t complete—no problem, I skipped it. I went to the Ping Optimizer and had the same issue, so I skipped that as well. I loaded into the GUI dashboard and selected the only device on my network for testing purposes: my PC. I selected the server region via my location, which, by the way, does not do anything when I click it (I had to manually enter my state). Upon trying to join a game, I noticed it was throwing me into Dublin, as shown in this picture (or at the least trying to connect to it), even though Strict Filter Mode was turned on. It did let me connect twice into a server with a ping of 27. After that, I was placed once into a server with 147 ping. So I reflashed the R2 firmware and factory reset it once again. Upon coming back online and selecting all the settings again, the speed test and Ping Optimizer worked. But now we fail to connect to Call of Duty servers. I allowed that Dublin server, thinking it was an official COD server it was failing to connect to due to the strict filter. Same issue. I tried to resync the cloud multiple times, and even went to Device Manager and set my PC as a console (as I was told years ago this would work). We seem to be struggling with multiple issues, and I’ve kind of exhausted all ideas on what to do next. We are also experiencing high latency while on Ethernet, along with packet loss, as shown in this state: Ping statistics for 1.1.1.1: Packets: Sent = 234, Received = 232, Lost = 2 (0% loss), Approximate round-trip times in milliseconds: Minimum = 10ms, Maximum = 442ms, Average = 22ms Any ideas? I would love to hear them. What seems to have stopped me from using the Netduma R2 a year or so back was the GUI crashing constantly. While that is no longer an issue, the connection is now. I've included some pictures, along with the Logs file. I hope this helps! R2_2026-05-22T03_45_47.263Z_logs.txt

Parece ser uma boa ideia vou testar.

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

Cai bem mais que isso, as vezes chega a cair para 350 exemplo, por isso minha dúvida.

It really depends how much it fluctuates, if it's significant for example frequently drops to 450 then it may be better to put in an average like 475

Só tem um observação o meu download ele não fica 100% 500 megas ele oscila as vezes! Mesmo assim eu ponho os 500 megas?