What's new

[Fork] Asuswrt-Merlin 374.43 LTS releases (Archive)

  • 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!

V30E3, AC66U. When I put vsftpd.conf in /jffs/configs vsftpd does not start.
deleting /jffs/configs/vsftpd.conf makes everything ok.

I have been trying with empty vsftpd.conf and my previously working vsftpd.conf. Both cases do not work, if /jffs/configs/vsftpd.conf exists.

V30E2 shows the same problem.

All factory reset between firmware changes.

A false alarm. Sorry.

the entry "isolate=NO" was the culprit. Removing the entry from /jffs/configs/vsftpd.conf fixes the problem.
"isolate=NO" is needed for recent Merlin firmwares' vsftpd to work with MIPS models. Apparently not with John's. Maybe because of the difference in vsftpd versions. (3.x for Merlin's recent and 2.x for John's)

## MIPS troubleshooting
https://www.snbforums.com/threads/r...-69-is-now-available.42697/page-3#post-364427

"That's why. The (vsftpd with) MIPS issue was resolved by disabling process isolation. If you are replacing vsftpd.conf, make sure you also re-add isolate=NO in your custom vsftpd.conf, otherwise it will indeed be unstable on the RT-AC66U."

was what Merlin said, so I was kind of reluctant to take out the entry, but it's only for 3.x, I guess.
 
Last edited:
AiCloud refuses to connect in the two latest versions, both from the Android app and via the web. Reverted back to v29E2 and everything is working again. I'm on AC66U.
I intentionally don't touch AICloud code without a good reason because it's so fragile. So nothing there has changed recently.

I tested on my AC68P, and cloud access worked, but SmartSync would hang continuously on INIT (I'm assuming that's the problem you are seeing). I was able to fix this on the AC68 by backporting the recent prebuilt binaries from the 384 code where it specifically called out fix with SmartSync. Unfortunately, there is no 384 code for the MIPS routers. I did update the MIPS binaries to the latest 380 base, but am not set up to test SmartSync on MIPS.

I was getting a new release ready, but am going to redo it to pick up these changes. Best I can offer is to give it a try again then.
 
I intentionally don't touch AICloud code without a good reason because it's so fragile. So nothing there has changed recently.

I tested on my AC68P, and cloud access worked, but SmartSync would hang continuously on INIT (I'm assuming that's the problem you are seeing). I was able to fix this on the AC68 by backporting the recent prebuilt binaries from the 384 code where it specifically called out fix with SmartSync. Unfortunately, there is no 384 code for the MIPS routers. I did update the MIPS binaries to the latest 380 base, but am not set up to test SmartSync on MIPS.

I was getting a new release ready, but am going to redo it to pick up these changes. Best I can offer is to give it a try again then.

Ok, I'll give it another try but SmartSync isn't the problem, I don't have it enabled. The problem is I cannot connect to samba or ftp on the connected USB disk via web or app. I can connect to ftp via an ftp client (WinSCP) though. Really strange but well, I can live with being on v29.
 
Hi there, thanks for providing this code and discussion! I have an ASUS RT-N16 HW Version A1 which had Merlin installed on it. As I wanted to upgrade, I tried installing RT-N16_374.43_29E2j9527 using the recovery console. It failed installing, and I was left on recovery mode. I then downloaded the original Asus firmware, latest version 30043807378 directly from ASUS and successfully did a recovery install from it. Or almost succesfully... Now I am unable to enter recovery mode again. I have cleared NVRAM from the web interface many times, no luck with that. I am wondering if my CFE got damaged somehow! I tried to go back to ASUS original firmware 30043784850, also no luck. Any ideas on how to install a custom firmware now and/or restore the whole thing so it works as intended? I can try a 30-30-30 reset, but I am a bit wary of losing what I have now and possibly screwing up the whole thing. I have telnet access just fine to the router, so I can execute commands. Any ideas, very much appreciated! TIA!
 
@Lord Lovaduck
It very tough to damage the bootloader. Power down, then remove any USB attached devices and try again to enter recovery mode. Depending on the state of the your PC, you may need to assign it a static IP/mask (try 192.168.1.10/255.255.255.0) to connect. When you do the restore, make sure you give it enough time....the flash in the early MIPS router is VERY slow, and it can take up to an hour for it to complete.

EDIT: fixed static ip
 
Last edited:
Thanks for the quick response! Flash had all the time it wanted, used the ASUS recovery util first, the TFTP portion went just fine then it waits for a long time (I had dinner in between) then it gave up, don't recall the exact wording of the error but it basically didn't get to reboot. After this I rebooted and the router was in recovery mode. Tried again using TFTP from the Windows client, also uploaded fine, left it untouched.... got back to recovery mode with the slow flashing. At that point I downloaded and installed the stock firmware, and when the unit rebooted itself I had the web interface up and running. And I had static address set from the beginning to 192.168.1.2 with gateway at 1.1, mask 255.255.255.0 as it should be, so that part was OK.
I am considering trying to install something from the administration page, using firmware update. Not sure what that could be :) :) any ideas? Reinstall same firmware? Or try a Merlin as I had before??? I cannot install the fork from my .380 version unfortunately!

@Lord Lovaduck
It very tough to damage the bootloader. Power down, then remove any USB attached devices and try again to enter recovery mode. Depending on the state of the your PC, you may need to assign it a static IP/mask (try 192.168.1.10/255.255.255.0) to connect. When you do the restore, make sure you give it enough time....the flash in the early MIPS router is VERY slow, and it can take up to an hour for it to complete.

EDIT: fixed static ip
 
Thanks Colin! Yes, Merlin have removed support for the N16 and as you said, old versions are not on their site although it's always possible to find some hoarder that has it, I myself might have it in some old notebook or archive drive. My question is more oriented to finding a firmware that would load from the Asus stock one and allow me to jump to this fork. Looking for stepping stones....

Merlin doesn't make firmware for the N16 anymore. In fact as far as I can see the old versions aren't even available for download.
 
My question is more oriented to finding a firmware that would load from the Asus stock one and allow me to jump to this fork. Looking for stepping stones....
Since you are on 380_7378 you can only go to ASUS firmwares 380_3000 or Merlin 380.60 or above via the gui. Any earlier level requires using the Restoration Tool.

One thought you might try loading the 'L' version of the fork via the Restoration tool. For Merlin code, if you can get a copy of 378.55 or 378.56 those would be the best levels to try, again via the Restoration tool.
 
Thanks, John! Trying to do this but don't forget, the crux of this issue is that I cannot enter the recovery mode anymore!!!
:mad: :mad::mad:
Today after leaving the router off for a few hours I tried again, and got teased with a short period of blinking light that resembled recovery mode. I rushed to start the recovery and while I fumbled through the process Murphy's law kicked in and took away the brief window of hope that had opened.
After this bitter disappointment:(, I decided to go all the way and tried a 30-30-30 reset (hope springs eternal:) but faded away quickly:confused:)... It was completely useless. Not even a reset to factory settings happened.

Stay tuned, I will keep trying....

Since you are on 380_7378 you can only go to ASUS firmwares 380_3000 or Merlin 380.60 or above via the gui. Any earlier level requires using the Restoration Tool.

One thought you might try loading the 'L' version of the fork via the Restoration tool. For Merlin code, if you can get a copy of 378.55 or 378.56 those would be the best levels to try, again via the Restoration tool.
 
Thanks, John! Trying to do this but don't forget, the crux of this issue is that I cannot enter the recovery mode anymore!!!
Try this.....
on your PC with the static ip start a continuous ping to the router address 192.168.1.1
now try to start recovery mode on the router
if you see what looks like recovery mode, kill the ping and try to access the CFE miniserver at
http://1921.168.1.1
 
Try this.....
on your PC with the static ip start a continuous ping to the router address 192.168.1.1
now try to start recovery mode on the router
if you see what looks like recovery mode, kill the ping and try to access the CFE miniserver at
http://1921.168.1.1
Thanks again John, unfortunately no luck with this technique either. I managed to get the router in Recovery mode after letting it unplugged all night. Started the recovery tool, it managed to get past halfway the TFTP portion, then it aborted got a solid power light and could not restart recovery mode again.

I found this thread https://www.snbforums.com/threads/going-from-dd-wrt-k3x-asuswrt-merlin.19167/
with the recommendation of doing the following:
mtd-erase -d jffs2
mtd-erase -d nvram
reboot
I think I can do this with the current ASUS stock firmware 380, would it be safe? I also dumped the CFE from the RT-N16 based on a thread that has a lot of CFE versions unfortunately I couldn't find one for the RT-N16 to use as comparison! If anybody has a CFE for the RT-N16 for me to compare or can read this one and tell me if it is corrupted, I would be very thankful!
cfe.dump https://mega.nz/#!HI0VWbbT!lWeRXYQ6WX3u3JBajlwVPLHtsiuSmQ2c6LB1UOXkUqk
Again, thanks everybody! Being very far from everything (I live in Patagonia) I rely heavily on forum discussions for keeping my tech working, be that the router or my car. Always getting the best advice. It is specially valuable in my situation!
 
I found this thread https://www.snbforums.com/threads/going-from-dd-wrt-k3x-asuswrt-merlin.19167/
with the recommendation of doing the following:
Those commands are usually only necessary for routers that have or had DD-WRT installed which uses a different partitioning scheme that can confuse the asuswrt code. The later versions of asuswrt may also use a different partition naming convention where those commands would not be correct. What is the output of
Code:
cat /proc/mtd
 
LATEST NEWS!!! Managed to restore a mini DD-WRT after fumbling with the red WPS button and the reset button... based on a post where the recommendation was to erase flash memory and then immediately start recovey more. I did this, and recovery mode engaged. Tried restore with the smallest firmware I had (I had tried before with full sized ones and the router recovery never finished!).
Voila!!! It worked!!! At the moment there's a DD-WRT welcome page showing!!! I don't dare touch anything, just waiting for all the bytes to firmly settle o_O in flash memory and then I will see how to continue. I think I can install the fork directly from the mini DD-WRT. Will keep you guys posted as to how this goes!
:):):):)
Thanks for all help!

What is the output of
Code:
cat /proc/mtd
Here it is!!!
Code:
RT-N16 login: admin
Password:
admin@RT-N16:/tmp/home/root# cat /proc/mtd
dev:    size   erasesize  name
mtd0: 00040000 00020000 "pmon"
mtd1: 01fa0000 00020000 "linux"
mtd2: 019c2c84 00020000 "rootfs"
mtd3: 00020000 00020000 "nvram"
mtd4: 00100000 00020000 "jffs2"
admin@RT-N16:/tmp/home/root#
 
Last edited:
  • Like
Reactions: il2
@Lord Lovaduck
Interesting that DD-WRT loaded.....

The /proc/mtd output you posted looked normal for an N16, so not sure what the problem would be. You may want to run the same command now with DD-WRT loaded to compare it. the mtd-erase commands may be needed now after you load any asuswrt based code.
 
@Lord Lovaduck
Interesting that DD-WRT loaded.....

The /proc/mtd output you posted looked normal for an N16, so not sure what the problem would be. You may want to run the same command now with DD-WRT loaded to compare it. the mtd-erase commands may be needed now after you load any asuswrt based code.

Thanks! I did compare it, the JFFS partition was not present, the CFE location was the same, so was the NVRAM the linux partition had a different offset if I remember correctly. Didn't save the output as the most important thing IMHO was the JFFS and it wasn't there. I then did a firmware upgrade to the fork, directly from DD-WRT which succeeded!!!

fork started.JPG


At this point I have done a factory reset to clear NVRAM, it rebooted, went through initial setup as it should and it is now very much functional!!!

I am glad I didn't give up on this one!!!! Success!!!!
Thanks again for all the help!
 
Update-31E6 is now available!


Update-31E6 Highlights
  • Updated DROPBEAR to release 2018.76
  • Updated OpenVPN to release 2.4.5
  • Updated NANO to 2.9.3
  • Located nanorc file to /jffs/configs allowing users to provide their own config file (Merlin backport)
  • Update ASUS webstor components to ARM/384 and MIPS/380 latest releases
  • Added new SMBv1/SMBv2 options for SAMBA support (Merlin backport)
  • NEW: Added options to set the SMB buffers size for performance tuning
    The buffer allocation will be set to 'Auto' mode after loading this release, which has been the best option for most users.
  • Updated entware setup scripts to support the new entware repository
  • Updated the DNSCrypt update resolvers script to support the new v2 format
    The fork still uses the original v1 DNSCrypt release (v2 support is planned for a later release) but can now process the v2 resolver definition files to get the latest list of resolvers. Running the script will also now warn you if a resolver you have selected has become unavailable.
    IMPORTANT: The resolver naming convention has changed, so you will need to reselect your resolvers following the first running of dnscrypt-update-resolvers.sh
  • Ignore reserved hostnames from broken dhcp clients (Samsung TV) (Merlin backport)
  • Included additional BusyBox applets hd, od and base64
  • Fixed unable to delete policy rules in OpenVPN client
  • Fixed Connection status not updating when first run under FireFox - @umx2000
  • Fixed https certs not available after being updated - @Uncle_Gadget

Please review the 'Installation Notes' section in the first post for further information on installing this fork.

The 'E' Build series supports all the support routers, including the newer rev AC68U and similar routers, and is the default fork version. The biggest change is the inclusion of the KRACK fix for the N66, AC66, AC56 and AC68 routers when used as a Repeater or Media Bridge. The N16 will NOT be updated for the KRACK fix.

For those of you with early rev (A1,A2,B1) AC68U's who wish to remain with the earlier wireless drivers, I've included a build directory that continues to be based on the earlier drivers/SDK, Update-nnLx (Legacy 'L' Build). IMPORTANT: The legacy builds do NOT include the KRACK fix for any supported router since part of the fix requires new wireless drivers.

I've also included a file @UpgradeMatrix.txt in the download directory. This shows the options for each router and build combination, including the need for a Factory Default reset or possible JFFS reformat.


Thanks again for everyone's support!


LATEST RELEASE: Update-31E6, including support new rev AC68 class routers
12-March-2018
Merlin fork 374.43_31E6j9527
Download http://bit.ly/1YdgUcP
============================

SHA256
Code:
(Default Build - All supported routers)
6f96b08b0e301f71088c483d2366aa4f892762c9bdd543c05bc97674862f1cec  RT-N16_374.43_31E6j9527.trx
e098cc44769fb29ce4824483f8ed67189104027479ccc89b3b3d69d21572dc4a  RT-AC66U_374.43_31E6j9527.trx
b1f3ec16171a8226c25e960a9741b814c10684e593fcb9288901013bf9c4a120  RT-N66U_374.43_31E6j9527.trx
8db9d8157d034402ac01fe53e8060e76492a9b1f9072a07edcd459bb69301cb4  RT-AC68U_374.43_31E6j9527.trx
5ac83930ac1123e48b9aa8611f0d43ed4d7901a421f0dbc30cad961933537bfa  RT-AC56U_374.43_31E6j9527.trx

(Legacy Only Builds)
46bc8eaf9f7b195876dad55f6bd2da15fd2e2f2c2d07b08eeb040183d8f739e4  RT-AC68U_3.0.0.4_374.43_2-31L6j9527.trx
a401d38469679cf9376c5e3aea1a8e3ea81a1e4cbbd75bcbf9ed54a348637896  RT-AC56U_3.0.0.4_374.43_2-31L6j9527.trx
4d6c824ea903f108854a4e8bf4efeb555863f9fb3b49a8b0fb1363f5e148be5d  RT-N16_3.0.0.4_374.43_2-31L6j9527.trx
0bdaa21d53b2ce040a1c957a882199ff5e4a4ddba20807313bdabab96634f1d5  RT-AC66U_3.0.0.4_374.43_2-31L6j9527.trx
8f8989f892f5c878155e72f597046bcdd3bd5887bd0e6c45274459f39bc1cdef  RT-N66U_3.0.0.4_374.43_2-31L6j9527.trx
 
Last edited:

Sign Up For SNBForums Daily Digest

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

Members online

Top