1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.
Dismiss Notice

Welcome To SNBForums

SNBForums is a community for anyone who wants to learn about or discuss the latest in wireless routers, network storage and the ins and outs of building and maintaining a small network.

If you'd like to post a question, simply register and have at it!

While you're at it, please check out SmallNetBuilder for product reviews and our famous Router Charts, Ranker and plenty more!

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

Discussion in 'Asuswrt-Merlin' started by john9527, Aug 14, 2014.

  1. john9527

    john9527 Part of the Furniture

    Joined:
    Mar 28, 2014
    Messages:
    5,925
    Location:
    United States
    LATEST RELEASE: Update-37E4/36L4
    25-November-2018
    Merlin fork 374.43_37E4j9527
    Download http://bit.ly/1YdgUcP
    ============================

    This is an LTS (Long Term Service) fork of Asuswrt-Merlin based on 374.43_2. This older code base has a history of being very stable, and some of the older code components may perform better in some environments. It may be a good choice for those who desire a 'set it and forget it' router solution. Additional information on the differences between this firmware and the later Asuswrt-Merlin releases can be found following the recent change highlights.

    The following routers are supported by this firmware:
    • N16, N66U, AC66U (original MIPS based revs)
    • AC56U, AC68U (Rev A1,A2,B1), AC68P (and the retail and color versions, R and W, of each router)
    • AC68U (Rev C1,E1), AC1900 and AC1900P (and the retail and color versions, R and W, of each router) and the AC66U-B1
    The following routers were released after the base code used for this fork was available, and are NOT supported.
    • AC87U, AC3100, AC3200, AC88U, AC5300, AC86U (and the retail R versions)
    Source: https://github.com/john9527/asuswrt-merlin : branch 374.43_2-update
    IMPORTANT The github repro was rebased on 29-November-2018.
    If you have a local repo, you should save any custom changes, clone a new copy, then re-apply your changes.

    Following are the major changes (full changelog is in the zip files)

    Update-37E4 Highlights
    • Add DDNS ez-ipupdate support for external ip (double NAT)
    • Update OpenSSL to version 1.0.2q
    • Update Dnsmasq to version 2.80-122392e snapshot
    • Update GetDNS (used in DoT) with latest upstream fixes
    • Update udpxy to build 23
    • Increase allowable key/cert size to 4999 bytes for OpenVPN client/server
      As a reminder, NVRAM is the default location for saving OpenVPN keys/certs. To free NVRAM space, the 'ovpn2jffs' utility may be used as documented in Merlin_Fork_Options.txt
    • Add ability to select DNSSEC validation method for DoT
    • Misc WebUI formatting/content fixes

    Installation Notes
    • Firmware is now packaged as a zip file (consistent with Merlin firmware releases). Remember to extract the .trx file prior to updating the firmware. An sha256sum file is included in the zip file to validate the firmware.
    • For supported routers currently running ASUS firmware 380.3000 or above, or Merlin 380.60 or above, you cannot load this fork using the built in firmware update web interface. You must use the ASUS Firmware Restoration Tool from the ASUS support website or the built in CFE Mini-Web Server to install this fork firmware. You must always perform a factory default reset following the firmware update when moving from ASUS OEM or Merlin firmware above level 374 regardless if you updated via the web interface or Restoration Tool.
    • When using the ASUS Firmware Restoration Tool or CFE Mini-Web Server to install this fork firmware on MIPS based routers (N16, N66 or AC66 non_B1) the upgrade process can take from 40 minutes to 1 hour. Please be patient and do not interrupt the process.
    • Currently, two build streams are maintained.
      • The 'E' Builds are the recommended builds and contain the latest wireless drivers and related fixes, including the fixes for the KRACK exploit on all supported models except the N16 (ASUS never released a KRACK fix for the N16). The 'E' Builds for ARM routers also contain the latest ARM SDK providing support for the newer rev level AC68U and it's variations.
      • The 'L' Builds contain the original wireless drivers (2014 release) and DO NOT address the KRACK exploit, and for ARM routers DO NOT contain the latest SDK providing support for the latest AC68U rev levels. In addition, some fixes dependent on either the latest wireless drivers or latest ARM SDK may not be included in the 'L' builds. Please review the release notes/Changelog for further information.
    • If you are updating an AC56U or AC68U running a fork version V26 or earlier, a factory reset is recommended following the firmware update to V27 or later. You may also need to reformat and restore JFFS due to updates for compatibility with the Merlin releases. Other fork users running an N16, N66U or AC66 can update to the 'E' Build as normal without a factory reset.
    • Please review '@UpgradeMatrix.txt' in the download directory, which describes the upgrade options for all the supported routers. Included are the requirements for a Factory Default Reset or reformat of JFFS.
    • If you need to perform a factory reset and are currently running firmware level 380 or earlier, you may use my NVRAM SAVE/RESTORE utility (check for the latest version) to transfer your user settings from your current firmware to this fork. https://www.snbforums.com/threads/19521/
      Using the NVRAM SAVE/RESTORE utility coming from firmware levels 382 or later is not supported and these users must manually reconfigure following the factory reset.
    • Users are reminded to have a jffs backup. For users with MIPS based routers, changes in the code image size may affect the jffs space. For users of ARM based routers, changes in the jffs partitioning may also affect the jffs allocations. If you are having jffs script errors or cannot access jffs after loading the firmware, please reformat jffs from the Administration page and restore your jffs backup.

    Additional Information
    The fork does include
    • Maintenance for documented security issues
    • Maintenance for supporting open source components (such as dnsmasq, miniupnpd, etc)
    • Backports of applicable fixes and new functions from Merlin's main branch
    • Some unique support for options requested by users, such as DoT, NTP Server and improved Traditional QoS
    • A different IPv6 stack which may work better in some environments
    • A separate build with older versions of the wireless drivers that some feel offer better performance (especially on the MIPS based routers)
    • Less of a lockdown on tweaking power levels
    The fork does not include
    • The new TrendMicro DPI engine functions for ARM routers
    • The enhancements to the networkmap for custom icons, client naming, etc.
    • Some of the enhanced gui formatting of later releases, for instance the new wireless log
    • Support for the ASUS router control app
    • Support for 5 VPN Clients as in Merlin (this fork supports 2 client instances). Note that the N16 does not support VPN Client/Server due to memory limitations.

    Custom features of the fork which are not exposed in the gui can be set by an nvram variable. These custom features are documented in the Merlin_Fork_Options file in the download directory.

    Thanks to all for your continued interest in this fork.

    SHA256
    Code:
    (Default Build - All supported routers)
    609b98530bcd7eee66801de92371c5dccec20016abb01b36aac1ff98c2fa2140  RT-N16_374.43_37E4j9527.trx
    5fbd3ba7d27883be30c46ae57f4bb7131eab8665c225eb91f73b269b5a2d51a0  RT-AC66U_374.43_37E4j9527.trx
    3a34ea8385b9a4fb34acae73b8994a0ec27c11221103c02f7d430fbd4b1c40db  RT-N66U_374.43_37E4j9527.trx
    396df043cf7ff99af2a164e431377038281b6fd1c4d749761bc4a3d340912bd4  RT-AC68U_374.43_37E4j9527.trx
    37ac3069c688e08f071ed9e841576f5b625fd7bc26b1b78842efa788549071ae  RT-AC56U_374.43_37E4j9527.trx
    
    (Legacy Only Builds)
    9d31c752d33488ab619155d0bb6e5326e6c273137b3c5407ef1c45cf3008180a  RT-AC68U_3.0.0.4_374.43_2-37L4j9527.trx
    f6b9ad8d9e96d5773ce13f53c03991ca636ab1eb3567bb301f07af66341bbb13  RT-AC56U_3.0.0.4_374.43_2-37L4j9527.trx
    516d9161ded42d679d677ce9ac76b28d86d42fd3714d89515479aafee8202756  RT-N16_3.0.0.4_374.43_2-37L4j9527.trx
    6914a88daa6e11bf7b7cf73d714a0899acdc22621d203cf9de4a35712dbbe20c  RT-AC66U_3.0.0.4_374.43_2-37L4j9527.trx
    9101a8617ebf0d22743188f1f193c960715bbb3530249ab4f5ec013bfeaf3ef6  RT-N66U_3.0.0.4_374.43_2-37L4j9527.trx
    
     
    Last edited: Nov 29, 2018
    rednic, I am JK, lev and 80 others like this.
  2. Raiu

    Raiu Regular Contributor

    Joined:
    Dec 10, 2013
    Messages:
    186
    This is awesome man! I haven't tried it yet. My wife is in school so I need 100% up time right now lol
     
  3. Builder71

    Builder71 Senior Member

    Joined:
    Oct 14, 2012
    Messages:
    497
    Location:
    The Netherlands
    Awesome!
    A maintenance update for 374.43 :)

    I flashed it on top of 374.43 and so far so good.
    Nice work.

    MD5 checksum I got for the RT-N66U .trx file: E10E98C4F6CF380B00712A6A6BEEE2A1
     
  4. john9527

    john9527 Part of the Furniture

    Joined:
    Mar 28, 2014
    Messages:
    5,925
    Location:
    United States
    Glad to hear that the flash on N66U worked!
    Good point on the MD5 checksum....I added them for all the releases in the first post.
     
  5. Builder71

    Builder71 Senior Member

    Joined:
    Oct 14, 2012
    Messages:
    497
    Location:
    The Netherlands
    Nothing funny in the syslog so far.
    Glad to see my MD5 is the same as your source. :)

    For my understanding, the fixes/changes above are they all from Github?
    Or did you merge them in yourself?
     
  6. kiesa1231

    kiesa1231 Regular Contributor

    Joined:
    Jul 13, 2013
    Messages:
    91
    Please fix to work huawei e3276s 4g modem in 374.43_3 build thanks.
     
  7. Jeffo

    Jeffo New Around Here

    Joined:
    Jul 17, 2014
    Messages:
    4
    Add maintenance of Huawei 3g/4g lte dongle to 374.43

    Same here. Requesting for maintance fix for the Huawei compatibility issue for 3G/4G/LTE dongle. it was working from Merlin 374.40Alpha4 and older also the latest 376.44 series. the firmwares in between doesn't work.
    Using a Huawei e3276s here too.
     
  8. lwizard

    lwizard Regular Contributor

    Joined:
    Jan 27, 2014
    Messages:
    95
    minidlna

    Is it possible also updating minidlna to 1.1.3?

    Thanks for the work.

    I am scared about trying 44 since it seems to cause lot of troubles in very important things like wifi and general speeds... and actually 43.2 is working right for me..
     
  9. Builder71

    Builder71 Senior Member

    Joined:
    Oct 14, 2012
    Messages:
    497
    Location:
    The Netherlands
    Come on gents, cut the Huawei crap.
    That one is complicated and for ASUS to fix.
    Send ASUS a bug report!

    And put the router in question in your signature.
    Do we have to smell what you are using?

    Do try the fork from john9527 and give him some feedback.
    Much better than only asking.
     
    Last edited: Aug 15, 2014
  10. Kal-EL

    Kal-EL Very Senior Member

    Joined:
    Aug 15, 2013
    Messages:
    1,457
    Location:
    Motor City, Michigan-USA
    Can someone running this build explain more about it ? Is this a build that has the fixes for 44 but the interface of 43_2 ? Any comments would be great..
     
  11. Builder71

    Builder71 Senior Member

    Joined:
    Oct 14, 2012
    Messages:
    497
    Location:
    The Netherlands
    Don't be scared, just give 376.44 a try.
    See if it works in your environment and decide yourself.
    If not, simply revert to what you are using now.
     
  12. Builder71

    Builder71 Senior Member

    Joined:
    Oct 14, 2012
    Messages:
    497
    Location:
    The Netherlands
    That seems the case as far as I can see.

    Maybe john9527 can tell us a bit more...
     
  13. john9527

    john9527 Part of the Furniture

    Joined:
    Mar 28, 2014
    Messages:
    5,925
    Location:
    United States
    All the fixes have been committed by Merlin in his master branch. For this build, I merged them in by hand....gave me a chance to double check they were applicable (some I looked at were not) and gave me the chance to work through how git really worked. The exception was the openssl update...that one I let 'git cherry-pick' for me (146 updated files!).
     
  14. john9527

    john9527 Part of the Furniture

    Joined:
    Mar 28, 2014
    Messages:
    5,925
    Location:
    United States
    Merlin kindly tags all his releases in github, so I was able to make a branch of exactly the 374.43 release. With that as a base, I looked at what had been fixed in later builds that may have been seen on the 43 code (a good example is the Plex miniupnpd syslog flood). So I picked up that specific fix and added it to the 43 code.

    So what this is, is the 43 code, with just a couple of fixes on top of it that may help people out who don't want to upgrade to the next major release yet.
     
  15. john9527

    john9527 Part of the Furniture

    Joined:
    Mar 28, 2014
    Messages:
    5,925
    Location:
    United States
    Right now the minidlna update is not in the plan (there is one minidlna fix picked up)....Asus actually picked that up, so it's rolled into Merlin's big merge without a specific commit I can go after (and I need to learn more to do an update that big ;) ) This is unlike the openssl commit where I was just able to grab Merlin's work (only picked up to stay on top of any security issues).

    Also, as you said, for me 43.2 is running pretty well....there were just a couple of things that needed addressing in my environment which led me into this project. I don't want to do too much and end up destabilizing the 43.2 base.
     
  16. Builder71

    Builder71 Senior Member

    Joined:
    Oct 14, 2012
    Messages:
    497
    Location:
    The Netherlands
    Great choice!

    The problem with 376.44 is that you can't localize the router any more.
    This is ASUS crap because of some FCC regulations.
    FCC has no jurisdiction in my country, but ASUS doesn't care.

    This means that with 376.44 I'm stuck with only 4 channels on 5GHz and reduced range on both WiFi bands.

    So I stick with 374.43 unless there are serious security issues that needs to be fixed.
    Probably a lot of people will do the same.
    Such a shame for a great open source project.

    That's why I am happy to see john9527's update on the 374.43 base. :)
     
  17. Builder71

    Builder71 Senior Member

    Joined:
    Oct 14, 2012
    Messages:
    497
    Location:
    The Netherlands
    Running fine, nothing unusual seen in syslog. :)
     

    Attached Files:

  18. DrTeeth

    DrTeeth Senior Member

    Joined:
    Mar 29, 2013
    Messages:
    380
    Many, many thanks indeed. Just what the Dr ordered, no pun intended.

    Please keep up the good work. If you do keep it up, please set up a donation page.
     
    Last edited: Aug 16, 2014
  19. Raiu

    Raiu Regular Contributor

    Joined:
    Dec 10, 2013
    Messages:
    186


    From what I have read those that went to 44 and that wanted to go back were stuck and couldn't get their settings to work right.
     
  20. Kal-EL

    Kal-EL Very Senior Member

    Joined:
    Aug 15, 2013
    Messages:
    1,457
    Location:
    Motor City, Michigan-USA
    I tried 44 two times and went back to 43_2 with no issues just make sure you do a complete factory reset.