[R2] Critical DumaOS Web UI Failure – Accessing Dashboard Causes LAN/Wi-Fi Disconnects, Factory Reset Ineffective

[alexander.divos]

Hello Netduma Support Team,

I am reporting a reproducible stability issue with my Netduma R2. Accessing the DumaOS web interface appears to trigger a network subsystem failure or partial router restart.

1. Issue Summary

The router operates normally during regular internet browsing. Local connectivity and continuous ICMP ping responses remain stable as long as I do not access the DumaOS web interface.

However, opening the DumaOS dashboard consistently causes temporary connectivity loss on both Ethernet and Wi-Fi.

The issue persists after a factory reset and also occurs when the router is completely disconnected from its upstream WAN connection.

2. Steps to Reproduce

1. Connect a Windows PC directly to a LAN port on the Netduma R2.

2. Disconnect the R2 WAN cable to isolate the router from the upstream network.

3. Confirm that the PC receives an address in the 192.168.77.0/24 subnet.

4. Start a continuous ping using ping -t 192.168.77.1.

5. Verify that ICMP responses remain stable.

6. Open http://192.168.77.1 in a browser.

7. The browser redirects to http://192.168.77.1/desktop/index.html?cache=0.

3. Actual Behavior

• DumaOS displays a red loading screen but never successfully loads the dashboard.

• The local network connection becomes unstable immediately after accessing the interface.

• On Ethernet, Windows intermittently reports that the network cable is disconnected.

• ICMP requests fail, sometimes returning Windows transmission errors.

• Over Wi-Fi, the router's SSID temporarily disappears.

• Connectivity generally returns after approximately 5–10 seconds.

• The behavior is reproducible using different browsers.

• Normal connectivity remains stable when the DumaOS interface is not accessed.

4. Troubleshooting Completed

• Factory reset performed: No improvement

• Tested Microsoft Edge and another browser: Same issue

• Tested Ethernet and Wi-Fi: Both affected

• Tested without WAN connected: Issue persists

• Verified local DHCP functionality: Working

• Verified continuous ICMP connectivity without accessing DumaOS: Stable

• Verified the router can provide normal internet connectivity: Working

The original upstream configuration was:

ISP router → OPNsense firewall → Netduma R2 WAN → Client devices

However, the failure was reproduced with the Netduma R2 isolated from OPNsense, suggesting that the upstream firewall is not responsible.

5. Firmware and Power Information

• Device: Netduma R2

• Installed firmware version: Unknown, as the dashboard is inaccessible

• Firmware downloaded: DumaOS-R2-3.3.280.sig

• Firmware installation: Not attempted

• Power adapter currently in use: 12 V DC, 3.2 A

• Original power adapter: Unavailable

6. Technical Assessment

The issue appears to be triggered by initializing the DumaOS web interface rather than by normal network traffic.

Potential causes could include a firmware or web-service crash, network subsystem restart, hardware instability, or a power-related issue. I cannot confirm the root cause without additional diagnostics.

7. Support Request

Could your technical team please advise:

1. Is this behavior associated with a known DumaOS R2 firmware defect?

2. Is there an officially supported recovery or firmware reinstallation method that does not require access to the dashboard?

3. Can the R2 provide diagnostic logs through a supported alternative interface?

4. Could the symptoms indicate a power supply or hardware fault?

5. If software recovery is not possible, what hardware diagnostic or repair options are available?

I can provide screenshots showing the ICMP failures and additional test results if required.

I would appreciate guidance on the safest recovery procedure for this specific router model.

Thank you for your assistance.

[Netduma Fraser]

I've given you the Early Access firmware to try, access via the mobile app as that should allow you without a disconnect then upgrade and see if it works. If it doesn't then I think it'll be the power supply or where it's plugged into, do you have it connected to a power extender or direct to an outlet? If an extender please try direct to an outlet. Otherwise do you have another power adapter you could try with?