Multiple Issues With R2.

[Hungstick]

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

[Paulo_81]

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!

[Netduma Fraser]

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. 

[Hungstick]

4 hours ago, Netduma Fraser said:

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. 

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?

[Hungstick]

5 hours ago, Paulo_81 said:

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!

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

[Netduma Fraser]

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?

[Netduma Fraser]

5 hours ago, Paulo_81 said:

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 minute ago, Hungstick said:

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

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.