Posted: Tue Mar 23, 2021 11:25 Post subject: After update to R44048 5g doesn't always start
I took the suggestion of updating to R44048 (I'd been at R41218). I did not reset. Everything worked fine for two days.
My router is set to reboot at 3:00a.m. daily. Since the update, every second day or so, the 5G interface doesn't start at boot. The interface shows that it's running, but nothing can connect to it. If I power-cycle the router, it will come up without a problem.
Before I start thrashing around, I thought I'd ask here. I was thinking of reloading R44048, letting it reset to default, then reloading the config R44048 file.
With the reported problems connecting to Apple devices, I don't want to update beyond R44048 at this point in time.
Thanks in advance for any suggestions. _________________ Router: Linksys WRT1900ACSv2
Modem: Verizon Fios DD-WRT v3.0-r44048 std (08/02/20)
ISP: Verizon Fios
NAS: ReadyNas314
Joined: 08 May 2018 Posts: 14207 Location: Texas, USA
Posted: Tue Mar 23, 2021 14:05 Post subject:
Screenshot all your configs. If the problem is due to an nvram issue, then restoring config from backup is not in your best interest. This is why it is always advised to configure from scratch after a reset. _________________ "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
Joined: 08 May 2018 Posts: 14207 Location: Texas, USA
Posted: Tue Mar 23, 2021 14:46 Post subject:
Selecting 'reset to defaults after flash' is not advised. You can either use the ~10 second reset button method with the router powered up, using reset to defaults via the webUI under 'Administration->Factory Defaults' or via telnet/ssh 'nvram erase && reboot'.
Posted: Sat Mar 27, 2021 10:55 Post subject: Ongoing issue with 5G interface
My original issue: I had updated to R44048 without resetting. Everything worked fine for two days. Then after the nightly reboot, the 5G interface failed to come up, and nothing could connect to it. Power-cycling the router got everything running.
Following kernel-panic69's advice, I reset NVRAM via
Code:
nvram erase && reboot
I actually did this twice, and then manually re-entered all my settings. I had thought of resetting using the 30-30-30 method, but recalled reading somewhere that newer routers can be bricked that way.
Again, everything worked perfectly for two days. But this morning, the 5G interface once again failed to come up after the reboot. Power-cycling the router got everything working again.
Why: dnsmasq DNS function stops working occasionally, and the nightly reboot is the easiest way to keep things running. It's never been a problem with previous releases. _________________ Router: Linksys WRT1900ACSv2
Modem: Verizon Fios DD-WRT v3.0-r44048 std (08/02/20)
ISP: Verizon Fios
NAS: ReadyNas314
Joined: 08 May 2018 Posts: 14207 Location: Texas, USA
Posted: Sat Mar 27, 2021 13:23 Post subject:
Just seems like possible user-configuration error. Someone *really* needs to do a write-up with screenshots on what wireless settings work on Marvells. There is plenty of discussion on configuring DNSMasq in the forum. After I figured a few things out (like that part of it was my wireless settings), I have had uptimes of up to a month between upgrades without issues with DNSMasq. _________________ "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
Well, suppose I turn OFF scheduled reboot, and let the router run for a week or two. If/when something happens, I'll share it here, along with whatever log entries or screenshot snips of my settings that might be useful.
Just to clarify, the problems I had with dnsmasq were many releases ago - perhaps three years. I configured the auto-reboot at that time, and have just left it in place. _________________ Router: Linksys WRT1900ACSv2
Modem: Verizon Fios DD-WRT v3.0-r44048 std (08/02/20)
ISP: Verizon Fios
NAS: ReadyNas314
Open to suggestions for a better router than the one I have now. About the only router-intensive thing I do is video streaming (Netflix, Amazon, etc.), and the WRT1900ACSv2 has supported that quite well. But, perhaps it's time for a change... _________________ Router: Linksys WRT1900ACSv2
Modem: Verizon Fios DD-WRT v3.0-r44048 std (08/02/20)
ISP: Verizon Fios
NAS: ReadyNas314
Joined: 08 May 2018 Posts: 14207 Location: Texas, USA
Posted: Sat Mar 27, 2021 13:46 Post subject:
But advising this, that, or the other, or some other voodoo combination a million times might, of course. I'm curious to see if this changeset will help. Shared code, i.e. Broadcom TurboQAM, might likely be more at fault than the abandoned driver. _________________ "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