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 (V26E4)

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

  1. john9527

    john9527 Part of the Furniture

    Joined:
    Mar 28, 2014
    Messages:
    4,496
    Location:
    United States
    LATEST RELEASE: Update-26E4
    5-August-2017
    Merlin fork 374.43_2-26E4j9527
    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) and AC68P (and the retail and color versions, R and W, of each router)
    The following routers were released after the base code used for this fork was available, and are NOT supported.
    • AC66U-B1 (ARM based), AC68U Rev C1 and E1, AC1900, AC1900P, AC87U, AC3100, AC3200, AC88U, AC5300 (and the retail R versions)
    Note: A beta release is available that supports the

    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 to install this fork firmware.
    • A factory default reset is NOT required if coming from any level of the fork or Merlin 374.42 or 374.43 code. Coming from any other level does require a factory default reset after the code is loaded.
    • MIPS users are reminded to have a jffs backup as changes in the code image size may affect the jffs space! 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.

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

    Update-26E4 Highlights
    • Fixes for networkmap CVE-2017-11344, CVE-2017-11345 and CVE-2017-11420 (KiloFoxtrotPapa/Merlin backports)
    • Fix guest access to samba shares if you changed the default login name - @Lotta Cox
    • Change the behavior of the On/Off slider on the QoS page
      The slider is now a true On/Off, consistent with other On/Off firmware switches. User the Save button to save changes to the QoS parameters.
    • Further improvements in managing http authorizations
      Note: The various browsers are tightening http auth security in different ways. Chrome has implemented changes that essentially disable the 'Cancel' button under all http authorizations. You must now close the associated browser window if you with to abort the authorization process. For IE, trying to 'Cancel' the http authorization will result in the 'IP Address has changed' page instead of the expected 401 error, and you will again need to close the associated browser window to proceed.
    • Fix for some cases where Port Forwarding/UPNP may not work when CTF is active (Merlin backport)

    Update-26E3 Highlights
    • Updated versions of:
      • nano to 2.8.4
      • dropbear to 2017.75
      • ipset-arm to 6.32
      • avahi to 0.6.32
      • dnscrypt to 1.9.5
      • curl to 7.54
      • ASUS protection server to 380.7627
    • NEW: Samba - update to 3.6.25 which includes SMB2 support (enable on the USB servers page)
    • NEW: Support for IPSET 6 extended set types and options on the AC56/AC68. All set types/options listed in the IPSET 6 help page should now be supported.
    • NEW: Added inactivity timeout for SSH sessions, default set to 20min. This can be changed or disabled via a new option on the Administration>System page. (This has worked correctly in my fork testing as opposed to some problems seen on the latest Merlin builds).
    • NEW: An enhancement to force a revalidation of http credentials after an auto logoff or disconnect
      Note: When first loading V26 you will receive an http authentication challenge at the end of the firmware update. Future updates after 26BA will not receive this challenge following the firmware update.[/B]
    • NEW: New OpenVPN client options for the way the 'VPN block routed clients if tunnel goes down' is handled, and an indicator on the VPN status page if the clients are being blocked.
      There are now three options
      • Always - the previous 'Yes' behavior, clients will be blocked even if the client is manually disabled
      • Only when client is enabled - clients will not be blocked if you manually disable the client
      • Never - never block clients if the tunnel is down
      If the clients are being blocked, it will now show on the VPN Status page.
    • NEW: Miniupnp update to 2.0 with a new Port Forwarding syslog page which can track UPNP lease times.
    • NEW: A new option to clear existing miniupnpd leases
    • An upstream fix for dnsmasq when running in strict mode
      Note: Although dnsmasq 2.77 has been released, IMO it seems a bit unstable. Going to hold off on migrating to the latest build and only migrate selected fixes to my 2.76 'fork' release.
    • Fixes for incorrect incorrect trigger rules generation with port ranges and iptables-save of trigger rules.
    • Fix formatting problem in Wireless Log when connect time reaches 100 hours
    • Several backports from the latest Merlin builds in OpenVPN and Firewall support

    Some notes on this fork...

    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
    • A different IPv6 stack which may work better in some environments
    • 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
    • All the changes/tweaks that ASUS may have made since the original code was released (and any new introduced bugs :) )

    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.

    Source: https://github.com/john9527/asuswrt-merlin : branch 374.43_2-update

    SHA256
    Code:
    2eea1c549ce01810a7d62859694079c061c75d4c0faff1a714828f83295a28f7  RT-AC68U_3.0.0.4_374.43_2-26E4j9527.trx
    444ca62a7a5ed1407d45754f9e38ba5e1a3dd9ad5230b1fb7931b59e6519e0ed  RT-AC56U_3.0.0.4_374.43_2-26E4j9527.trx
    f4f601ea38bebcdf417e8dc437cbaf96ddfcc52c2a0d5a04f206b5bde954538c  RT-N16_3.0.0.4_374.43_2-26E4j9527.trx
    21a9013eb2042b124e34b55ef91dce3606926818997bdb467410372046884ad3  RT-AC66U_3.0.0.4_374.43_2-26E4j9527.trx
    00dc6ff83bbd4eb1922d7abea3b9e143361784f9aa8e0f85cd1dd4690fb28431  RT-N66U_3.0.0.4_374.43_2-26E4j9527.trx
    
     
    Last edited: Aug 10, 2017
  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:
    433
    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:
    4,496
    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:
    433
    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:
    89
    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:
    6
    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:
    433
    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,251
    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:
    433
    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:
    433
    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:
    4,496
    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:
    4,496
    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:
    4,496
    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:
    433
    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:
    433
    Location:
    The Netherlands
    Running fine, nothing unusual seen in syslog. :)
     

    Attached Files:

  18. DrTeeth

    DrTeeth Senior Member

    Joined:
    Mar 29, 2013
    Messages:
    381
    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,251
    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.
     

Share This Page