What's new

Release [Fork] Asuswrt-Merlin 374 LTS release 50E8

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

Status
Not open for further replies.
I checked recently there wat plenty of space in /var (/tmp/var) . Is there something I can do to prevent this in future?
Sorry, but in your case you are definitely out of space. Load the 50D9 development build and set the 'wd_norestart' nvram so you can check when it actually happens.

nvram set wd_norestart=1
nvram commit
 
Last edited:
Sorry I don't remember what the log said, but I also had the same problem as soon as I connected my Oneplus phone to my network. I still don't know why but as soon as my phone connected to my wifi network my ac66 router rebooted. I then solved the problem by buying a used AC68 router.
 
Yes

Probably not. The FRAGATTACK fix needs updated wireless drivers from ASUS, and I believe the remaining routers supported by the fork are all considered EOL by ASUS.
Bit of a shame though, perfectly decent routers that could be patched, but now end up as e-waste..................
 
Just had to take a time out to reflect....

Today marks the 7th Anniversary following the first LTS fork release....I really can't believe it.

For those wondering.....here's how much has changed from the original Merlin base.

Code:
git diff --shortstat 374.43_2 374.43_50E8j9527
 41419 files changed, 9096019 insertions(+), 1774541 deletions(-)
 
@john9527, congratulations are in order! For starting and continuing to do a fantastic job with our older routers.

I for one am very grateful that you're still here sharing your time and skills so freely. Thank you, and here's to the next 7 years!
 
I have loaded 50DA and working just fine. I have one question though,

On VPN=>VPN Status=>OpenVPN Client 1 on top of OpenVPN Client box I can see this:

Screenshot 2021-08-16 at 09-56-39 ASUS Wireless Router RT-AC56U - VPN Status - 2.jpg

Shouldn't we see "Server Address" also? Like: """ OpenVPN Client1 - Running - octopus.myddns.com - UDP:1234"""

Thank you!!??
@john9527
 
Last edited:
Related to the other threads AC66U reboot issue, now 3d 9h uptime and still going. This is with the 50DA version. There was some issue last night which looks a bit troubling. Approximately 70h after last firmware update/reboot
Code:
Aug 18 03:16:09 watchdog: restart httpd, error detected or process not responding (12)
Aug 18 03:16:09 rc_service: watchdog 327:notify_rc stop_httpd
Aug 18 03:16:09 rc_service: watchdog 327:notify_rc start_httpd
Aug 18 03:16:09 rc_service: waiting "stop_httpd" via watchdog ...
Aug 18 03:16:10 httpd: start httpd
Aug 18 03:53:39 watchdog: restart httpd, error detected or process not responding (12)
Aug 18 03:53:39 rc_service: watchdog 327:notify_rc stop_httpd
Aug 18 03:53:39 rc_service: watchdog 327:notify_rc start_httpd
Aug 18 03:53:39 rc_service: waiting "stop_httpd" via watchdog ...
Aug 18 03:53:40 httpd: start httpd
Aug 18 03:54:09 watchdog: restart httpd, error detected or process not responding (12)
Aug 18 03:54:09 rc_service: watchdog 327:notify_rc stop_httpd
Aug 18 03:54:09 rc_service: watchdog 327:notify_rc start_httpd
Aug 18 03:54:09 rc_service: waiting "stop_httpd" via watchdog ...
Aug 18 03:54:10 httpd: start httpd
Aug 18 03:54:39 watchdog: restart httpd, error detected or process not responding (12)
Aug 18 03:54:39 rc_service: watchdog 327:notify_rc stop_httpd
Aug 18 03:54:39 rc_service: watchdog 327:notify_rc start_httpd
Aug 18 03:54:39 rc_service: waiting "stop_httpd" via watchdog ...
Aug 18 03:54:40 httpd: start httpd
Aug 18 03:55:09 watchdog: restart httpd, error detected or process not responding (12)
Aug 18 03:55:09 rc_service: watchdog 327:notify_rc stop_httpd
Aug 18 03:55:09 rc_service: watchdog 327:notify_rc start_httpd
Aug 18 03:55:09 rc_service: waiting "stop_httpd" via watchdog ...
Aug 18 03:55:10 httpd: start httpd
Aug 18 03:55:39 watchdog: restart httpd, error detected or process not responding (12)
Aug 18 03:55:39 rc_service: watchdog 327:notify_rc stop_httpd
Aug 18 03:55:39 rc_service: watchdog 327:notify_rc start_httpd
Aug 18 03:55:39 rc_service: waiting "stop_httpd" via watchdog ...
Aug 18 03:55:40 watchdog: aborting httpd response checks - unrecoverable error
Aug 18 03:55:40 httpd: start httpd
 
I have an ASUS RT-N66U running Merlin Fork 374.43_2-20E9j9527. I would like to update to 50E8.

I read the installation notes, but am still a bit confused.

Do I need to use the ASUS Firmware Restoration Tool? Should I do a factory reset prior to updating and clear the NVRAM after updating?

Appreciate any help.

Hi Jedi, I still have one of these dinosaurs (RT-N66U)....I need to update as well but couldnt find clear instructions as well....can you point me in the right direction...thanks.
 
but I also had the same problem as soon as I connected my Oneplus phone to my network. I still don't know why but as soon as my phone connected to my wifi network my ac66 router rebooted. I then solved the problem by buying a used AC68 router.
I had this problem in my Oneplus/N66U router combo and solution was to disable the NAT Acceleration under LAN/Switch Control.
 
Thanks for your advice bejoysat. My 'new' AC68U works fine. The AC66U is in a box somewhere in the attic :)
 
Just had to take a time out to reflect....

Today marks the 7th Anniversary following the first LTS fork release....I really can't believe it.

For those wondering.....here's how much has changed from the original Merlin base.

Code:
git diff --shortstat 374.43_2 374.43_50E8j9527
41419 files changed, 9096019 insertions(+), 1774541 deletions(-)
Congratulations John and thank you so much for all the work you put in to maintain this fork. It really is greatly appreciated by me and many, many other people.
 
  • Like
Reactions: sto
Related to the other threads AC66U reboot issue, now 3d 9h uptime and still going. This is with the 50DA version. There was some issue last night which looks a bit troubling. Approximately 70h after last firmware update/reboot
Code:
Aug 18 03:16:09 watchdog: restart httpd, error detected or process not responding (12)
Aug 18 03:16:09 rc_service: watchdog 327:notify_rc stop_httpd
Aug 18 03:16:09 rc_service: watchdog 327:notify_rc start_httpd
Aug 18 03:16:09 rc_service: waiting "stop_httpd" via watchdog ...
Aug 18 03:16:10 httpd: start httpd
Aug 18 03:53:39 watchdog: restart httpd, error detected or process not responding (12)
Aug 18 03:53:39 rc_service: watchdog 327:notify_rc stop_httpd
Aug 18 03:53:39 rc_service: watchdog 327:notify_rc start_httpd
Aug 18 03:53:39 rc_service: waiting "stop_httpd" via watchdog ...
Aug 18 03:53:40 httpd: start httpd
Aug 18 03:54:09 watchdog: restart httpd, error detected or process not responding (12)
Aug 18 03:54:09 rc_service: watchdog 327:notify_rc stop_httpd
Aug 18 03:54:09 rc_service: watchdog 327:notify_rc start_httpd
Aug 18 03:54:09 rc_service: waiting "stop_httpd" via watchdog ...
Aug 18 03:54:10 httpd: start httpd
Aug 18 03:54:39 watchdog: restart httpd, error detected or process not responding (12)
Aug 18 03:54:39 rc_service: watchdog 327:notify_rc stop_httpd
Aug 18 03:54:39 rc_service: watchdog 327:notify_rc start_httpd
Aug 18 03:54:39 rc_service: waiting "stop_httpd" via watchdog ...
Aug 18 03:54:40 httpd: start httpd
Aug 18 03:55:09 watchdog: restart httpd, error detected or process not responding (12)
Aug 18 03:55:09 rc_service: watchdog 327:notify_rc stop_httpd
Aug 18 03:55:09 rc_service: watchdog 327:notify_rc start_httpd
Aug 18 03:55:09 rc_service: waiting "stop_httpd" via watchdog ...
Aug 18 03:55:10 httpd: start httpd
Aug 18 03:55:39 watchdog: restart httpd, error detected or process not responding (12)
Aug 18 03:55:39 rc_service: watchdog 327:notify_rc stop_httpd
Aug 18 03:55:39 rc_service: watchdog 327:notify_rc start_httpd
Aug 18 03:55:39 rc_service: waiting "stop_httpd" via watchdog ...
Aug 18 03:55:40 watchdog: aborting httpd response checks - unrecoverable error
Aug 18 03:55:40 httpd: start httpd

Edit: Seems this error was fixed with 50DA. Going to try soon.

Same except "watchdog 346" if that makes a difference. Otherwise things seem to be running normally for me as they have almost the entire time of using this firmware.

And congrats on 7 years of this fork, John. I think I've personally been using it 4 years + 3 of Merlin on this same router. Thank you guys so much for your hard work and the untold amount of routers you've saved from wasting away and $ you've saved people. Also Asus since this has been the most stable router I've ever used, though admittedly haven't used but a handful.
 
I have loaded 50DA and working just fine. I have one question though,

On VPN=>VPN Status=>OpenVPN Client 1 on top of OpenVPN Client box I can see this:

View attachment 35740

Shouldn't we see "Server Address" also? Like: """ OpenVPN Client1 - Running - octopus.myddns.com - UDP:1234"""

Thank you!!??
@john9527
 
New dev 51D3 on my RT-AC68U rev A1. Smooth as ever.:)
 
I don't know how this might affect the forks, but this is pretty bad, I think: https://www.bleepingcomputer.com/ne...ds-of-thousands-of-devices-using-realtek-sdk/

Congrats on 7 years! Still running my RT-N66U with 50E8 :)
Search?

 
Release 51E3 is now available.

@RMerlin - please lock this thread.

 
Status
Not open for further replies.

Latest threads

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top