I would like to express my frustration regarding my Netduma R2.

I purchased this router second-hand and it was working perfectly when I received it. Since it still contained personal information and settings from the previous owner, I decided to perform a factory reset using the reset option available in the router's own web interface.

Unfortunately, after the factory reset completed, the router never booted correctly again.

What is most disappointing is that I did not use any unofficial procedure, custom firmware, or advanced configuration. I simply used the factory reset function provided by the router itself for its intended purpose.

It is very frustrating to invest in a premium and expensive product and then end up with an unusable device after performing a standard factory reset.

Could you please explain why this happened and whether there is an official recovery procedure available? At the moment, it appears that the factory reset has effectively bricked the router.

I would appreciate any assistance in recovering the device.

Attached is the error log.

Thank you.

logs (5).txt

In the following, it also looks like it will be ported over:

https://support.netduma.com/support/solutions/articles/16000132677-dumaos-firmware-progress

Does anyone have any information on the possibility of this coming or how/when it will be available?

I'm assuming all R2 users are currently wondering this as well.

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

For those using the Netduma R2: Which firmware version is currently providing the most stable performance and full throughput (bandwidth) without reductions? Does version 3.2.453 handle full speeds well, or is there a specific older build that you recommend for maximum performance?"

I’m experiencing intermittent but severe latency and connection instability while using my Netduma R2, and I’d like help determining whether the router could be contributing to the issue.

Setup:

• ISP: Vodafone (DSL/FTTC)
• Router: Netduma R2
• Modem: DrayTek Vigor 130 (bridge mode)
• Previously tested: Vodafone Power Hub (all-in-one)

What I observed:

• With the Netduma R2 + DrayTek Vigor 130:
  • Bufferbloat improved significantly (A rating after QoS tuning)
  • However, after a couple hours on using this setup:
    • Very high latency in games (e.g. ~110ms in Overwatch, ~190ms in Minecraft)
    • Large spikes (400–600ms, occasionally up to 2000ms+)
    • General web browsing becomes very slow
    • Continuous ping test (8.8.8.8) shows normal latency (10–60ms) with intermittent huge spikes and occasional “General failure”
• Modem status lights:
  • DSL solid
  • LAN active
  • No obvious disconnect indicators
• When switching back to the Vodafone Power Hub:
  • Connection becomes stable again (no spikes or dropouts)
  • Latency is higher under load (bufferbloat), but no extreme spikes or failures

QoS configuration on Netduma R2:

• Anti-bufferbloat enabled (tested both auto and always-on)
• Currently set to ~85% download / ~75% upload
• This successfully reduced bufferbloat but did not prevent later instability

Key question:
Based on this behaviour, does this point to:

• a potential compatibility or stability issue between the Netduma R2 and DrayTek Vigor 130 (e.g. PPPoE handling, WAN drops, etc.), or
• is this more likely to be entirely upstream (modem/line-related)?

Also, are there any recommended WAN/PPPoE/MTU or advanced settings on the Netduma R2 that could help improve stability in a DSL bridge modem setup?

Thanks in advance for your help.

client
dev tun
proto udp
remote 217.138.208.91 1194
resolv-retry infinite
remote-random
nobind
tun-mtu 1500
tun-mtu-extra 32
mssfix 1450
persist-key
persist-tun
ping 15
ping-restart 0
ping-timer-rem
reneg-sec 0
comp-lzo no
verify-x509-name CN=us9330.nordvpn.com

remote-cert-tls server

auth-user-pass
verb 3
pull
fast-io
cipher AES-256-CBC
auth SHA512

Config is connected

Sun Apr 5 10:50:34 2026 OpenVPN 2.4.7 mipsel-openwrt-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [MH/PKTINFO] [AEAD] Sun Apr 5 10:50:34 2026 library versions: OpenSSL 1.1.1f 31 Mar 2020, LZO 2.10 Sun Apr 5 10:50:34 2026 WARNING: --ping should normally be used with --ping-restart or --ping-exit Sun Apr 5 10:50:34 2026 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts Sun Apr 5 10:50:34 2026 Outgoing Control Channel Authentication: Using 512 bit message hash 'SHA512' for HMAC authentication Sun Apr 5 10:50:34 2026 Incoming Control Channel Authentication: Using 512 bit message hash 'SHA512' for HMAC authentication Sun Apr 5 10:50:34 2026 TCP/UDP: Preserving recently used remote address: [AF_INET]217.138.208.91:1194 Sun Apr 5 10:50:34 2026 Socket Buffers: R=[163840->163840] S=[163840->163840] Sun Apr 5 10:50:34 2026 UDP link local: (not bound) Sun Apr 5 10:50:34 2026 UDP link remote: [AF_INET]217.138.208.91:1194 Sun Apr 5 10:50:34 2026 TLS: Initial packet from [AF_INET]217.138.208.91:1194, sid=88021dab 3d3f5cb0 Sun Apr 5 10:50:34 2026 WARNING: this configuration may cache passwords in memory -- use the auth-nocache option to prevent this Sun Apr 5 10:50:35 2026 VERIFY OK: depth=2, C=PA, O=NordVPN, CN=NordVPN Root CA Sun Apr 5 10:50:35 2026 VERIFY OK: depth=1, O=NordVPN, CN=NordVPN CA11 Sun Apr 5 10:50:35 2026 VERIFY KU OK Sun Apr 5 10:50:35 2026 Validating certificate extended key usage Sun Apr 5 10:50:35 2026 ++ Certificate has EKU (str) TLS Web Server Authentication, expects TLS Web Server Authentication Sun Apr 5 10:50:35 2026 VERIFY EKU OK Sun Apr 5 10:50:35 2026 VERIFY X509NAME OK: CN=us9330.nordvpn.com Sun Apr 5 10:50:35 2026 VERIFY OK: depth=0, CN=us9330.nordvpn.com Sun Apr 5 10:50:35 2026 Control Channel: TLSv1.3, cipher TLSv1.3 TLS_AES_256_GCM_SHA384, 4096 bit RSA Sun Apr 5 10:50:35 2026 [us9330.nordvpn.com] Peer Connection Initiated with [AF_INET]217.138.208.91:1194 Sun Apr 5 10:50:36 2026 SENT CONTROL [us9330.nordvpn.com]: 'PUSH_REQUEST' (status=1) Sun Apr 5 10:50:36 2026 PUSH: Received control message: 'PUSH_REPLY,redirect-gateway def1,dhcp-option DNS 103.86.96.100,dhcp-option DNS 103.86.99.100,explicit-exit-notify,comp-lzo no,route-gateway 10.100.0.1,topology subnet,ping 60,ping-restart 180,ifconfig 10.100.0.2 255.255.240.0,peer-id 1,cipher AES-256-GCM' Sun Apr 5 10:50:36 2026 OPTIONS IMPORT: timers and/or timeouts modified Sun Apr 5 10:50:36 2026 OPTIONS IMPORT: explicit notify parm(s) modified Sun Apr 5 10:50:36 2026 OPTIONS IMPORT: compression parms modified Sun Apr 5 10:50:36 2026 OPTIONS IMPORT: --ifconfig/up options modified Sun Apr 5 10:50:36 2026 OPTIONS IMPORT: route options modified Sun Apr 5 10:50:36 2026 OPTIONS IMPORT: route-related options modified Sun Apr 5 10:50:36 2026 OPTIONS IMPORT: --ip-win32 and/or --dhcp-option options modified Sun Apr 5 10:50:36 2026 OPTIONS IMPORT: peer-id set Sun Apr 5 10:50:36 2026 OPTIONS IMPORT: adjusting link_mtu to 1657 Sun Apr 5 10:50:36 2026 OPTIONS IMPORT: data channel crypto options modified Sun Apr 5 10:50:36 2026 Data Channel: using negotiated cipher 'AES-256-GCM' Sun Apr 5 10:50:36 2026 Outgoing Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key Sun Apr 5 10:50:36 2026 Incoming Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key Sun Apr 5 10:50:36 2026 TUN/TAP device tun0 opened Sun Apr 5 10:50:36 2026 TUN/TAP TX queue length set to 100 Sun Apr 5 10:50:36 2026 /sbin/ifconfig tun0 10.100.0.2 netmask 255.255.240.0 mtu 1500 broadcast 10.100.15.255 Sun Apr 5 10:50:36 2026 /bin/touch /tmp/lua_bnojmG tun0 1500 1585 10.100.0.2 255.255.240.0 init Sun Apr 5 10:50:36 2026 Initialization Sequence Completed

das Problem ist heute aufgetaucht.

bis gestern hat alles perfekt funktioniert und heute jedes mal bei Neustart immer reset automatisch 

I ran into the access issue when I moved and I no longer see the NetdumaR2 wireless network showing that I setup plus I have a new internet provider so I thought the hard reset would be the best approach.

Steps performed:

1. Press reset on back of router for 45 seconds.

2. Wait 10 minutes.

3. Plug Ethernet cable from computer into port and try to access http://dumaos/ in browser. I also tried with the IP address of 192.168.77.1.

I followed the steps indicated in this documentation, https://support.netduma.com/support/solutions/articles/16000129962-how-to-factory-reset-your-dumaos-powered-router.

First of all, many thanks.

Yesterday I performed some maintenance and reset my Netduma R2 using the reset button. Now, during the initial setup, it can’t detect the Ethernet connection. It’s strange because I still have internet access and can browse normally.

It seems that my Movistar WiFi 6 Go router can’t detect DumaOS anymore.

Also, I can’t access the Netduma software/interface because the router can’t complete the initial setup process.

Is there any way to downgrade the device to the latest DumaOS 3 version?

I'm having difficulty connecting to COD BO7 servers using the geo-filter; it continuously kicks me off the internet anytime I try to connect to a lobby. I've read there is issues with 3.3.280 firmware and the geo-filter