Jump to content

Recommended Posts

  • Administrators
Posted

Right click the page > Inspect Element > Console and paste this command:

long_rpc_promise("com.netdumasoftware.settings", "remote_access",["true"])

press enter and it should come back with a response. Let me know when it's done and then reply back here from a device connected to the R2 please and we'll attempt a remote upgrade.

Posted (edited)

I tried to run the command you were envious of, but it seems it wasn't successful. Please attach a screenshot after running the command. I have a PC connected to it; if you need access to it to try something, I can give you access. I just need you to tell me a preferred time in Brasilia so I can assist you.

Comando acesso remoto Netdumas.jpg

Edited by jorgelcd
Text
  • Administrators
Posted
7 hours ago, jorgelcd said:

Good evening. Any news regarding access?

Do the same process but use this command instead please:

duma.RPCHandler.PromiseAsync("com.netdumasoftware.settings", "remote_access","true")

I'll have someone monitor the topic so they can try to upgrade you when you say you're accessible.

Posted

I was able to execute the command you sent. Now the connection doesn't take very long, because he keeps losing the connection all the time.

Captura de tela 2026-06-21 180443.png

  • Administrators
Posted
23 hours ago, jorgelcd said:

Thank you. I'll be waiting.

They weren't able to access, if your ISP modem/router has WiFi, set it up so that it is in bridge or modem mode, you can also use the DMZ. Copy the WAN IP from the R3 (found in Settings > WAN) and enter it into the DMZ function on the ISP modem/router. Then post back here from a device connected to the R3 when you've done that and we'll attempt to connect again.

Posted

Good morning. I have a question: even if it loses connection every minute, will the remote connection you told me to run still work? Shouldn't the connection be stable for you to be able to access it? I work in networking and I'm almost certain you won't be able to access it. The router has a problem with the kernel; it's constantly intermittent.

Posted

"I identified from the logs that the antijitter module causes a kernel panic (BUG: spinlock bad magic) at approximately 62 seconds after boot on kernel 4.14.156, causing the router to reboot in a loop. The connection window is too short (~90 seconds) for a remote upgrade to complete successfully. Please advise on an alternative recovery method."

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...