Posted: Mon Nov 03, 2025 22:27 Post subject: MX4300 Is there a way to mimick power cycle via GUI/telnet
For my recent mx4300 firmware builds there seems to be a problem with the main router losing lan connection after about 48 hours approximately. It may even be fixed now with the latest updates but when this problem happens, I need to power cycle the router to restore the connections. Simple GUI reboot will not clear the error. Daily keepalive reboot also doesn't seem to clear it as all my routers reboot daily via that gui setting.
Is there any remote command that can be executed that will be the same as the power cycle? I am going to traveling the next few months like lots of people and was hoping to be able to mimic power cycling just in case it is needed.
I am not sure if this will even work as Im not sure when the main router loses connection if I can connect from outside and its just dhcp that is failing for devices connected or what...which i just realized I should test now that I thought about it, might give more insight into what is breaking, but anyway, is there any command that works?
Also note, I did search here and the openwrt forums and internet but didnt find an answer that i thought would work on ddwrt...yet
I have thought that if there isnt, I can rig a timed switch to just power cycle or I also have another method thru a battery backup that might work too I guess, so those are other potential ways around the problem if necessary but if there exists a remote command, that would be great too.
Thanks in advance for your help and all everyone does for the firmware!
Joined: 16 Nov 2015 Posts: 7039 Location: UK, London, just across the river..
Posted: Tue Nov 04, 2025 8:04 Post subject: Re: MX4300 Is there a way to mimick power cycle via GUI/teln
sanjonny wrote:
Is there any remote command that can be executed that will be the same as the power cycle?
if reboot command is hanging via GUI (very rare), connect to CLI (telnet or SSh) then issue:
Code:
echo b > /proc/sysrq-trigger
This will force reboot your unit..
It has been around for a while...but on update my R7800/XR500 are heaving issues with reboot command...sometimes works, sometimes not and i have to use the code from above... especially when im away and not close to the unit... _________________ Atheros
TP-Link WR1043NDv2 -DD-WRT 62606 Gateway/DoT,Forced DNS,Ad-Block,Firewall,x4VLAN,VPN
TP-Link WR1043NDv2 -Gargoyle OS 1.15.x AP,DNS,QoS,Quotas
Qualcomm-Atheros
Netgear XR500 -DD-WRT 62890 GTW/SmDNS/DoT,AD-Blk,Forced DNS,AP&Net Isolation,x2VLAN,Vanilla
Netgear R7800 --DD-WRT 62606 Gateway/DNSCryptv2,AD-Block,Forced DNS,AP&Net Isolation,x3VLAN,Firewall,Vanilla,VPN cli
Netgear R9000 --DD-WRT 62606 Gateway/DoT,AD-Block,AP Isolation,Firewall,Forced DNS,x2VLAN,Vanilla
Dynalink DL-WRX36-DDWRT 62606
Broadcom
Netgear R7000 --DD-WRT 62966 GTW/DNScrypt-proxy2/AD-Block,IPset Firewall,Forced DNS,x4VLAN,VPN cli
NOT USING 5Ghz ANYWHERE
------------------------------------------------------
Stubby DNS over TLS I DNSCrypt v2 by mac913
Joined: 05 Oct 2008 Posts: 834 Location: Helsinki, Finland / nr. Alkmaar, Netherlands
Posted: Tue Nov 04, 2025 19:14 Post subject:
Per Yngve Berg wrote:
IPv4 cease to work when the Lease towards the ISP expired. Renew is blocked. Pressing "Renew" change IP to 0.0.0.0 and no new address.
IPv6 continue to work normally.
It has been like this for the last 5 builds
I use only IPv4 ... and initially I hadn't paid attention to the router type which is the subject of this particular discussion.
Didn't check remaining WAN lease time when I pressed Renew on my R7800 to test Per Yngve's observation, but sure enough the router lost its WAN IP.
GUI reboot didn't help. I started to worry already ...
Fortunately interrupting power did result in getting a WAN IP again.
Not getting an IP on GUI reboot is a bit odd, because the router is rebooted by Keep Alive every night. Yet every morning it has had its WAN IP (behind a CGNAT, so some 10.x.y.z). There must be an other factor involved, too. Maybe it's what Per Yngve writes about the remaining lease time from the ISP.
Total WAN IP lease time in my case looks like 24 hrs.
Do we need to do more experiments to find out exactly what circumstances and causes a loss of WAN IP and what not?
IPv4 cease to work when the Lease towards the ISP expired. Renew is blocked. Pressing "Renew" change IP to 0.0.0.0 and no new address.
IPv6 continue to work normally.
It has been like this for the last 5 builds
I use only IPv4 ... and initially I hadn't paid attention to the router type which is the subject of this particular discussion.
Didn't check remaining WAN lease time when I pressed Renew on my R7800 to test Per Yngve's observation, but sure enough the router lost its WAN IP.
GUI reboot didn't help. I started to worry already ...
Fortunately interrupting power did result in getting a WAN IP again.
Not getting an IP on GUI reboot is a bit odd, because the router is rebooted by Keep Alive every night. Yet every morning it has had its WAN IP (behind a CGNAT, so some 10.x.y.z). There must be an other factor involved, too. Maybe it's what Per Yngve writes about the remaining lease time from the ISP.
Total WAN IP lease time in my case looks like 24 hrs.
Do we need to do more experiments to find out exactly what circumstances and causes a loss of WAN IP and what not?
Its been whacky and I've been trying to document. short version, around 48 hours its happened to main router or secondary router, but power cycle reboot clears it.
GUI reboot doesnt and daily keep alive doesnt. And in the past if the 48 hours was first on the secondary...it would lose its lan connection to the primary, but in most circumstances the primary would reach the time first as whatever goes out must reset on the secondary when the primary reboots. It's around 48 hours...devices are still connected and it still shows lan connection.
Its been going on longer than the last 5 updates, but I didnt get as much investigation till recently. I think it has also happened on other models and I have been watching the wan ip...but in my circumstance, the wan ip was there, but the internet connection will not work until power cycle.
Logs didnt really show anything. The last few revs im not sure it still exists, time hasnt gone on long enough without reboot for other reasons.
IPv4 cease to work when the Lease towards the ISP expired. Renew is blocked. Pressing "Renew" change IP to 0.0.0.0 and no new address.
IPv6 continue to work normally.
It has been like this for the last 5 builds
Confirm this on the latest build 11/5-62540 on mx4300 which I will add to the build thread.
As mentioned above, mostly mine seems to drop after 48 hours. It still shows connected and lease still available but no internet connection for devices. I did some basic checking this time and yes renew set to zero but did not regain connection and GUI reboot also did not regain connection. Power switch did like has been happening. I don't know if I could contact the router from outside the network, I did so many checks and forgot to check that one this time, but devices connected to the various waps and vaps could not get to the internet.
I was just thinking and sorry for the bad memory, did recent builds not have problems with the NTP not connecting? I am wondering if that might not be involved. I will keep my eye on it the next few days, but that would make sense why its experienced at different times and maybe why the gui reboot doesnt affect it but power cycling does?
Previously when I was in a similar situation and going away for few days/week, I would add reboot cron job and set it to every day or every 2 days to preemptively reboot. This has always worked for me.
my guess would be that is the same as running the gui reboot/keep alive reboot that does not resolve the situation. But I will try it and see what happens.
ALSO I confirmed that when this happens the router and internal network is fine as far as contact and talk between devices. Just lost the connection out and it turns out in to the network.
it does happen regardless of WAN ip time, meaning whatever the refresh is from the internet provider and unfortunately, that you cannot contact the router remotely, at least via ssh or telnet from the internet. So essentially it loses its wan connection even though it says it still has it, which is I guess why the router doesnt have any log entries related.
I currently dont run any watchdog type stuff on the router, though i do end up knowing within a short window when it has lost connection because other devices like switchbot and such notify me from their servers that they have lost contact. See the 11/5 build thread for more info on that.
Posted: Wed Nov 19, 2025 13:19 Post subject: Re: MX4300 Is there a way to mimick power cycle via GUI/teln
Alozaros wrote:
sanjonny wrote:
Is there any remote command that can be executed that will be the same as the power cycle? coc mod apk th 18
if reboot command is hanging via GUI (very rare), connect to CLI (telnet or SSh) then issue:
Code:
echo b > /proc/sysrq-trigger
This will force reboot your unit..
Has anyone confirmed if this command forces a "colder" boot than the standard reboot command on the MX4300 (IPQ807x chipset)?
Since sanjonny mentioned that standard software reboots aren't clearing the error, I'm wondering if sysrq actually drops power to the interfaces briefly or resets the PHY, or if it's just an immediate kernel restart?
Posted: Wed Nov 19, 2025 20:03 Post subject: Re: MX4300 Is there a way to mimick power cycle via GUI/teln
Monu wrote:
Alozaros wrote:
sanjonny wrote:
Is there any remote command that can be executed that will be the same as the power cycle? coc mod apk th 18
if reboot command is hanging via GUI (very rare), connect to CLI (telnet or SSh) then issue:
Code:
echo b > /proc/sysrq-trigger
This will force reboot your unit..
Has anyone confirmed if this command forces a "colder" boot than the standard reboot command on the MX4300 (IPQ807x chipset)?
Since sanjonny mentioned that standard software reboots aren't clearing the error, I'm wondering if sysrq actually drops power to the interfaces briefly or resets the PHY, or if it's just an immediate kernel restart?
I have not been able to test it but I have been able to just test for my upcoming travel that basically just adding a daily physical shutoff of the router via a smart switch ....but you could use a light timer or anything and taking it down for a minute and bringing it back up seems to be working. so over the 48hish time limit I still retain the connectivity. When I get back from travel i'll do more diagnosis on the issue but for 62540 11/5/25 at least I seem to be able to maintain a working connection so far at 3+ days.
I am thinking this might be causing an issue with a second router losing its lan connection after the 48 hours contrary to what I had thought before that if the main router reset the others wouldnt have the issue...but I am not sure that is the case so just throwing it out there and will note on the relevant build thread...that router is running 62606-11-12-25 so it might be something else going on and have not had a chance to diagnose properly.
