Unstable R7000 with DDWRT, solid with Stock Firmware

Post new topic   Reply to topic    DD-WRT Forum Index -> Broadcom SoC based Hardware
Goto page 1, 2, 3  Next
Author Message
trymion
DD-WRT Novice


Joined: 25 Mar 2020
Posts: 5

PostPosted: Thu Jan 13, 2022 15:44    Post subject: Unstable R7000 with DDWRT, solid with Stock Firmware Reply with quote
Hello,

I've been running this r7000 for a while now.

Originally, was on KONG builds way back but when he left the scene I eventually switched over to the stock firmware. With the KONG builds, it was stable.

I've tried to come back to DDWRT every now and then but I can't seem to get them stable, no matter what I try to do.

Please note that with the stock firmware, the router is solid and has no issues. I would just like to get DDWRT working again because of the available customisability with it.

So far, this past month, I've tried 3 different builds and all exhibit the same issue.

R47942
R47976
R48081 (Currently installed)

I have a really simple setup here:
100/10 download/upload on cable, TC-4400.
One wired gigabit PC
6-10 wireless devices (phones, tables, laptops)
One USB fan (single 200mm placed under the router)

I have no special rules or scripts running.
IPV4, dhcp WAN, static IP for in-house devices.

Basically when I reinstall a firmware, it gets a wipe (nvram erase && reboot). I go back in, set DNS servers, setup wifi ssid/passwords and setup static IP addresses.

The issue I'm having is that, seemingly randomly, the router will just "die". All the lights will stay on/activity blinking but the power light will turn a solid orange. When this happens, nothing can connect to the router. It's still broadcasting the SSIDs but nothing can connect and the wired PC will detect that the cable is unplugged. I can't telnet to it, obviously, to access any logs because nothing can connect to the router. When rebooting it with the reset button/power plug, the syslog is reset and I so I don't know where or what could possibly be causing this.

I also have tried enabling remote access to the router and tried accessing it from outside but it is also unresponsive when it gets to that state.

I've tried enabling the WDS/watchdog feature but it doesn't seem to work for my case. I've set it to google's DNS, quad9, cloudflare, and even to devices at home (e.g. a tablet that's always connected/never leaves the house) and it never reboots itself.

The past few days, I've tried to use a script I found online that is put into the startup scripts that apparently pings any IP address (i set it to the tablet mentioned above) and if reboot if it returns 0 but that didn't work either.

The only thing I can do is reset the router (button or unplug).

I have zero knowledge of how the software works, but I'm assuming that when this happens DDWRT is just crashed and fully unresponsive until a reboot.

Every thread about a new beta build, I see people with R7000s saying that it's stable with long uptimes but I can't figure out why mine can't any longer (possibly since any KONG build, if I try to think back).

I originally thought (i made a thread similar to this but with a separate problem I was able to fix) that my router possibly had a hardware issue but running the stock netgear firmware is rock solid and I never have to reboot or touch it.

Any help is appreciated.

I guess, at the end of the day, I can go back to the stock firmware but it's wracking my brain as to why DDWRT just won't work any more.
Sponsor
Alozaros
DD-WRT Guru


Joined: 16 Nov 2015
Posts: 6407
Location: UK, London, just across the river..

PostPosted: Thu Jan 13, 2022 19:32    Post subject: Reply with quote
check your power supply, it will work on stock firmware but not on ddwrt if corrupted..
otherwise my R7000 is rock solid..

_________________
Atheros
TP-Link WR740Nv1 ---DD-WRT 55179 WAP
TP-Link WR1043NDv2 -DD-WRT 55303 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 55460 Gateway/DoH,Forced DNS,AP Isolation,4VLAN,Ad-Block,Firewall,Vanilla
Netgear R7800 --DD-WRT 55460 Gateway/DoT,AD-Block,Forced DNS,AP&Net Isolation,x3VLAN,Firewall,Vanilla
Netgear R9000 --DD-WRT 55363 Gateway/DoT,AD-Block,AP Isolation,Firewall,Forced DNS,x2VLAN,Vanilla
Broadcom
Netgear R7000 --DD-WRT 55460 Gateway/SmartDNS/DoH,AD-Block,Firewall,Forced DNS,x3VLAN,VPN
NOT USING 5Ghz ANYWHERE
------------------------------------------------------
Stubby DNS over TLS I DNSCrypt v2 by mac913
trymion
DD-WRT Novice


Joined: 25 Mar 2020
Posts: 5

PostPosted: Thu Jan 13, 2022 19:48    Post subject: Reply with quote
Alozaros wrote:
check your power supply, it will work on stock firmware but not on ddwrt if corrupted..
otherwise my R7000 is rock solid..


thanks for the reply.
is there anything i should be looking for? i assume there's probably no physical way to check if it's bad but maybe i can try a different outlet.

if it's the power plug, would underclocking the r7000 show improvements? e.g. 800 or 600mhz options under the "overclocking" section in DDWRT. i suppose i could give these a try as well.

thanks again for giving me something else to try.
Alozaros
DD-WRT Guru


Joined: 16 Nov 2015
Posts: 6407
Location: UK, London, just across the river..

PostPosted: Fri Jan 14, 2022 7:21    Post subject: Reply with quote
use multi-meter to measure the power supply output...or buy another one at least 3.5A... if you can find a 5Amp it will be even better...
if power supply is broken, slowing down CPU is not an option...

The other possible issues are corrupt radio hardware, bad firmware installation...or bad settings and bad clients at last...

can you give a kernel syslog or serial log to gain more details...it would be a bit more visible if a firmware or settings issue is the reason...

_________________
Atheros
TP-Link WR740Nv1 ---DD-WRT 55179 WAP
TP-Link WR1043NDv2 -DD-WRT 55303 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 55460 Gateway/DoH,Forced DNS,AP Isolation,4VLAN,Ad-Block,Firewall,Vanilla
Netgear R7800 --DD-WRT 55460 Gateway/DoT,AD-Block,Forced DNS,AP&Net Isolation,x3VLAN,Firewall,Vanilla
Netgear R9000 --DD-WRT 55363 Gateway/DoT,AD-Block,AP Isolation,Firewall,Forced DNS,x2VLAN,Vanilla
Broadcom
Netgear R7000 --DD-WRT 55460 Gateway/SmartDNS/DoH,AD-Block,Firewall,Forced DNS,x3VLAN,VPN
NOT USING 5Ghz ANYWHERE
------------------------------------------------------
Stubby DNS over TLS I DNSCrypt v2 by mac913
Puppetnation
DD-WRT Novice


Joined: 13 Aug 2010
Posts: 38
Location: Italy

PostPosted: Wed Jan 26, 2022 22:58    Post subject: R7000 dies randomly Reply with quote
My R7000 acts the same as yours.
Replaced stock PSU (suspecting any fault) with a 5A but the history is repeating...WAN ip sometimes keeps but not surfing, sometimes it retrurns to 0.0.0.0 with or without connection repair script.
Sometimes GUI is reachable and responding, sometimes is not.

Even a power off/on is often not enough, I need to do it twice.

Useless to say I always made 30/30/30, reflash from Kong builds but NOTHING TO DO

I suspect my R7000 is dying, maybe a known physical issue?

_________________
Netgear R9000+Draytek 2865 as bridge modem
MikroTik hAP AC as backup or portable
foz111
DD-WRT Guru


Joined: 01 Oct 2017
Posts: 704
Location: Earth

PostPosted: Thu Jan 27, 2022 9:07    Post subject: Reply with quote
OP, you could try remote logging or connect it to a serial and wait for it to crash & see what the output says.
https://wiki.dd-wrt.com/wiki/index.php/Logging_with_DD-WRT

If you can get it back up and running with a simple reboot SFTD in and you can grab the messages.0 log from /tmp/var/log

_________________
Netgear R7800 PPPoE Main Router
Network IPV4 - Isolated Vlan's with IoT Devices. Unifi AC-Pro x 3 AP's, Router Wi-Fi Disabled. OVPN Server With Paid Commercial Wireguard Client's. Gateway Mode, DNSMasq, Static Leases & DHCP, Pi-Hole DNS & Running Unbound.

No one can build you the bridge on which you, and only you, must cross the river of life!
dkca
DD-WRT Novice


Joined: 12 Jun 2013
Posts: 33

PostPosted: Fri Jan 28, 2022 17:54    Post subject: Reply with quote
My R7000 is still on DD-WRT v3.0-r47074 std (07/20/21) and it is so far so good. Was thinking of updating to newer DD-WRT firmware... Confused

Following this thread for updates.

BTW, I would be interested to see the log entries when it crashes too...
scope2
DD-WRT User


Joined: 12 Jul 2017
Posts: 181

PostPosted: Mon Jan 31, 2022 9:03    Post subject: Reply with quote
Im running DD-WRT v3.0-r47608 std (10/28/21) on my R7000 and its been very solid.
eolo
DD-WRT Novice


Joined: 04 Dec 2016
Posts: 24

PostPosted: Sun Mar 27, 2022 17:41    Post subject: R7000 crashing every day after upgrade from r44715 Reply with quote
Hello,
running r44715 from november 2020, upgraded to r48432 after discovering mac-filter broken on r44715.
I've two R7000 and a R6400v1.

R6400 r44715 --> r48432, upgrade from webgui, no configuration reset --> all OK

R7000-1 r44715 --> r48432, upgrade from webgui, no configuration reset --> all OK

R7000-2 r44715 --> r48432, upgrade from webgui, no configuration reset --> router unresponsive --> reset from button --> manual configuration from gui --> router unresponsive after about 1 day, need power restart --> router reset, reflash with r48432, reconfig from gui --> router unresponsive after about 1 day, need power restart --> router reset, reflash with r48305 --> router unresponsive after about 1 day, need power restart --> changed power supply --> router unresponsive after about 1 day, need power restart --> upgrade today from webgui to r48567, no reset, SFE disabled, waiting........

All threee router are configured the same, ONLY AP, 2.4GHz with 3 SSID (2 VAP), 5GHz with no VAP, mac filter on the main SSID, no QOS, no WAN, no DHCP, no IPv6, no DDNS, no telnet, no tor, no ttraff, no vnc, no zabbix, no freeradius.
Enabled only SNMP, SSH, remote syslog.

There are are no useful syslog messages to identify the problem.

To exclude an hardware failure i'll revert to r44715 at the next router death.

Any suggestion to be able to log system messages on router surviving the reboot?

UPDATE 28/03/2022: R7000-2 router unresponsive after about 16 hours: now downgrading to r44715.

UPDATE 30/03/2022: r7000-2 router unresponsive after 23h 26min. Now I suspect an hardware defect, because r44715 worked flawlessy from 2020 to 2022, and after the flash to r48432 the router begin to crash.

UPDATE 31/03/2022: r7000-2 router (flashed with an old r43334 that was very stable for me) unresponsive after 13h 2min. Trying now with stock rirmware, flashed Netgear R7000-V1.0.3.24_1.1.20.chk.

UPDATE 03/04/2022: after 3 day without problems with stock firmware, I think there are not hardware defects. I need features unavailable on stock firmware, so now I try to flash Fresh Tomato 2022.1.

-----------------------------------------------------
Atheros
Netgear WNDR3700v1 - DD-WRT r39137 (last with snmp) AP +2 VAP on 2.4GHz
Broadcom
Netgear R6400v1 - DD-WRT r48432 AP +2 VAP on 2.4GHz
Netgear R7000 - DD-WRT r48432 AP +2 VAP on 2.4GHz
Netgear R7000 - DD-WRT r????? AP +2 VAP on 2.4GHz (unstable with r48432)

-----------------------------------------------------
eolo
DD-WRT Novice


Joined: 04 Dec 2016
Posts: 24

PostPosted: Tue Apr 12, 2022 21:19    Post subject: Re: R7000 crashing every day after upgrade from r44715 Reply with quote
eolo wrote:
Hello,
running r44715 from november 2020, upgraded to r48432 after discovering mac-filter broken on r44715.
I've two R7000 and a R6400v1.

R6400 r44715 --> r48432, upgrade from webgui, no configuration reset --> all OK

R7000-1 r44715 --> r48432, upgrade from webgui, no configuration reset --> all OK

R7000-2 r44715 --> r48432, upgrade from webgui, no configuration reset --> router unresponsive --> reset from button --> manual configuration from gui --> router unresponsive after about 1 day, need power restart --> router reset, reflash with r48432, reconfig from gui --> router unresponsive after about 1 day, need power restart --> router reset, reflash with r48305 --> router unresponsive after about 1 day, need power restart --> changed power supply --> router unresponsive after about 1 day, need power restart --> upgrade today from webgui to r48567, no reset, SFE disabled, waiting........

All threee router are configured the same, ONLY AP, 2.4GHz with 3 SSID (2 VAP), 5GHz with no VAP, mac filter on the main SSID, no QOS, no WAN, no DHCP, no IPv6, no DDNS, no telnet, no tor, no ttraff, no vnc, no zabbix, no freeradius.
Enabled only SNMP, SSH, remote syslog.

There are are no useful syslog messages to identify the problem.

To exclude an hardware failure i'll revert to r44715 at the next router death.

Any suggestion to be able to log system messages on router surviving the reboot?

UPDATE 28/03/2022: R7000-2 router unresponsive after about 16 hours: now downgrading to r44715.

UPDATE 30/03/2022: r7000-2 router unresponsive after 23h 26min. Now I suspect an hardware defect, because r44715 worked flawlessy from 2020 to 2022, and after the flash to r48432 the router begin to crash.

UPDATE 31/03/2022: r7000-2 router (flashed with an old r43334 that was very stable for me) unresponsive after 13h 2min. Trying now with stock rirmware, flashed Netgear R7000-V1.0.3.24_1.1.20.chk.

UPDATE 03/04/2022: after 3 day without problems with stock firmware, I think there are not hardware defects. I need features unavailable on stock firmware, so now I try to flash Fresh Tomato 2022.1.

-----------------------------------------------------
Atheros
Netgear WNDR3700v1 - DD-WRT r39137 (last with snmp) AP +2 VAP on 2.4GHz
Broadcom
Netgear R6400v1 - DD-WRT r48432 AP +2 VAP on 2.4GHz
Netgear R7000 - DD-WRT r48432 AP +2 VAP on 2.4GHz
Netgear R7000 - DD-WRT r????? AP +2 VAP on 2.4GHz (unstable with r48432)

-----------------------------------------------------


The R7000-2 with fresh tomato is running flawlessy (no router unrensponsive, no need to recycle power), but I realized that about every 1-2 days the 2.4GHz radio disappears. Checking on syslog, I discovered some strange messages, and I suspect an hardware problem: with DD-WRT the router stop working, with fresh tomato the router restarts automatically (time 01:00 in syslog). Here an example of the error messages:

2022-04-10T12:00:20+02:00 r7000-2 192.168.17.250 daemon.warning MSG: dnsmasq-dhcp[1006]: no address range available for DHCP request via br0
2022-04-10T12:11:21+02:00 r7000-2 192.168.17.250 kern.warning MSG: kernel: framerdy 0x2 bmccmd 7 framecnt 0x400
2022-04-10T12:11:21+02:00 r7000-2 192.168.17.250 kern.warning MSG: kernel: AQM agg params 0xfc0 maxlen hi/lo 0x0 0xffff minlen 0x0 adjlen 0x8
2022-04-10T12:11:21+02:00 r7000-2 192.168.17.250 kern.warning MSG: kernel: AQM agg results 0x8001 len hi/lo: 0x0 0x69 BAbitmap(0-3) 0 0 0 0

2022-04-10T12:12:09+02:00 r7000-2 192.168.17.250 daemon.warning MSG: dnsmasq-dhcp[1006]: no address range available for DHCP request via br0
2022-04-10T12:12:09+02:00 r7000-2 192.168.17.250 daemon.warning MSG: dnsmasq-dhcp[1006]: no address range available for DHCP request via br0
2022-01-01T01:00:08+02:00 r7000-2 192.168.17.250 kern.info MSG: kernel: br0: port 3(eth2) entering forwarding state
2022-01-01T01:00:08+02:00 r7000-2 192.168.17.250 kern.info MSG: kernel: br0: port 2(eth1) entering forwarding state
2022-01-01T01:00:08+02:00 r7000-2 192.168.17.250 kern.info MSG: kernel: br0: port 2(eth1) entering forwarding state
2022-01-01T01:00:08+02:00 r7000-2 192.168.17.250 kern.info MSG: kernel: br0: port 1(vlan1) entering forwarding state
2022-01-01T01:00:08+02:00 r7000-2 192.168.17.250 kern.info MSG: kernel: br0: port 1(vlan1) entering forwarding state

Now I'll revert to stock firmware and test the stability a week long. If problems occurs I'll throw away the router.
Alozaros
DD-WRT Guru


Joined: 16 Nov 2015
Posts: 6407
Location: UK, London, just across the river..

PostPosted: Wed Apr 13, 2022 18:22    Post subject: Reply with quote
bear in mind Fresh Tomato, Stock firmware and DDWRT all use different kernels..
as well iv im not wrong, make sure you have a stable not corrupt copy of your R7000 CFE as inappropriate jumping around Tomato and DDwrt or stock can mess it up...
Crashing router could be due to bad PSU, bad settings, bad CFE, or corrupt hardware (radio, WAN port, switch and ect.)
for example my R7000 is flawlessly running the last 5 years on any new build (mostly the same settings)...currently running 48646 for a 1 day no problems...rock solid and it sees heavy use...

_________________
Atheros
TP-Link WR740Nv1 ---DD-WRT 55179 WAP
TP-Link WR1043NDv2 -DD-WRT 55303 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 55460 Gateway/DoH,Forced DNS,AP Isolation,4VLAN,Ad-Block,Firewall,Vanilla
Netgear R7800 --DD-WRT 55460 Gateway/DoT,AD-Block,Forced DNS,AP&Net Isolation,x3VLAN,Firewall,Vanilla
Netgear R9000 --DD-WRT 55363 Gateway/DoT,AD-Block,AP Isolation,Firewall,Forced DNS,x2VLAN,Vanilla
Broadcom
Netgear R7000 --DD-WRT 55460 Gateway/SmartDNS/DoH,AD-Block,Firewall,Forced DNS,x3VLAN,VPN
NOT USING 5Ghz ANYWHERE
------------------------------------------------------
Stubby DNS over TLS I DNSCrypt v2 by mac913
kernel-panic69
DD-WRT Guru


Joined: 08 May 2018
Posts: 14125
Location: Texas, USA

PostPosted: Thu Apr 14, 2022 16:10    Post subject: Reply with quote
Alozaros wrote:

as well iv im not wrong, make sure you have a stable not corrupt copy of your R7000 CFE as inappropriate jumping around Tomato and DDwrt or stock can mess it up...

XWRT-Vortex is the only firmware with caveats regarding the CFE used, and this is well-documented in the forum. Of course, @twindragon6 is using the Asus CFE appropriately modified so it detects the device as an R7000, so these caveats are non-existent, AFAIK. Also documented in the forum Cool

_________________
"Life is but a fleeting moment, a vapor that vanishes quickly; All is vanity"
Contribute To DD-WRT
Pogo - A minimal level of ability is expected and needed...
DD-WRT Releases 2023 (PolitePol)
DD-WRT Releases 2023 (RSS Everything)

----------------------
Linux User #377467 counter.li.org / linuxcounter.net
eolo
DD-WRT Novice


Joined: 04 Dec 2016
Posts: 24

PostPosted: Tue May 03, 2022 19:22    Post subject: Reply with quote
Alozaros wrote:
bear in mind Fresh Tomato, Stock firmware and DDWRT all use different kernels..
as well iv im not wrong, make sure you have a stable not corrupt copy of your R7000 CFE as inappropriate jumping around Tomato and DDwrt or stock can mess it up...
Crashing router could be due to bad PSU, bad settings, bad CFE, or corrupt hardware (radio, WAN port, switch and ect.)
for example my R7000 is flawlessly running the last 5 years on any new build (mostly the same settings)...currently running 48646 for a 1 day no problems...rock solid and it sees heavy use...


The CFE version is the same on both my R7000s. The R7000-1 runs flawlessy, the R7000-2 has the problem.
Do you know how can I compare the content of the two CFEs?

root@R7000-1:~# nvram show | grep version
size: 42258 bytes (23278 left)
router_version=211005
cfe_version=v1.0.22
os_version=48432
ezc_version=2
root@R7000-1:~#

root@R7000-2:~# nvram show | grep version
size: 42967 bytes (22569 left)
router_version=211005
cfe_version=v1.0.22
os_version=48646
ezc_version=2
root@R7000-2:~#
eolo
DD-WRT Novice


Joined: 04 Dec 2016
Posts: 24

PostPosted: Tue May 03, 2022 19:37    Post subject: some evidence Reply with quote
After fresh tomato 2022-1 crashing, reverted to stock firmware.
On stock firmware R7000-2 worked flawlessy for 1 week.
I need two VAPs (guest & IoT) so I tried the last dd-wrt release (r48646).
Configured R7000-2 the same as with stock firmware (AP with 2 SSID, one for 2.4G and one for 5G radio).
Worked flawlessy for 4 days.
After 4 days configured 2 VAPs on the 2.4G radio. R7000-2 crashed (unresponsive, power recycle needed) after about 40 hours.
So I deleted VAPs, R7000-2 is running now flawlessy (until now 54 hours).
It seems the problem depends on VAPs presence.
I'll keep you up-to-date.
eolo
DD-WRT Novice


Joined: 04 Dec 2016
Posts: 24

PostPosted: Tue Jun 21, 2022 20:54    Post subject: Inauspicious epilogue Reply with quote
After 3 days, even without VAP, the the R7000-2 with r48646 crashed.
Reverted to original firmware, it ran smoothly for over 1 month. Unfortunately the problem occurs only with dd-wrt or fresh tomato, I have no other tools to investigate, I will eliminate it Crying or Very sad
Goto page 1, 2, 3  Next Display posts from previous:    Page 1 of 3
Post new topic   Reply to topic    DD-WRT Forum Index -> Broadcom SoC based Hardware All times are GMT

Navigation

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You can attach files in this forum
You can download files in this forum