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

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

  1. john9527

    john9527 Part of the Furniture

    Joined:
    Mar 28, 2014
    Messages:
    4,750
    Location:
    United States
    LATEST RELEASE: Update-28E8, including support new rev AC68 class routers
    20-November-2017
    Merlin fork 374.43_28E8j9527
    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 (and the retail R versions)

    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. 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.
    • 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.
    • A separate firmware release is provided which only supports the older AC68U rev A1,A2,B1 ('L' Builds). Users of the earlier rev AC68U's can continue on the original fork SDK/wireless drivers by moving to this release branch.
    • 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, 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/
    • 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.

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

    Update-28E8 Highlights
    • OpenSSL updated to 1.0.2m
    • OpenVPN updated to 2.4.4
    • Update ASUS OUI db
    • Update modprobe aliases to support xt_set, ipt_set and cifs
    • Support gettunnelip from Merlin
    • Fixed MIPS CTF not working with some ISPs
    • Standardized reporting to be Kb/s and Mb/s instead of Kib/s and Mib/s (1K=1000 vs 1K=1024) per telecom standards
      This may require you to readjust your QoS Download/Upload targets
    • Move traffic monitor units setting from Tools>Other Settings to traffic monitor page
    • Fix QOS units being reset when changing QoS parameters under IE
    • Fix broken guest network page when using French locale
    • Include USB HID support for ARM routers
      Note this is only included in the new SDK (28E8) build and NOT included in the Legacy (28L8) build (the earlier SDK did not include the support)

    Update-28E2 Highlights
    • DNSMASQ updated to 2.78, including fixes for recently published CVE's
    • Fix for 5GHz radio not working on Japan region ARM routers
    • NEW: Option to block IPv6 internet access when an OpenVPN client is active. This prevents IPv6 'leaks' outside of the OpenVPN tunnel. Note that IPv6 internet access is blocked for all clients, not only those using the OpenVPN client. Local IPv6 access is still permitted. Also, in order to not have delays when browsing the internet, your browser must support RFC6555 (otherwise known as 'Happy Eyeballs'). Chrome, Firefox and Safari all have implemented this RFC and have minimal to no browsing impact. IE/Edge has not, and you may experience delays with using this option.
      You may also encounter applications that have not been coded to correctly retry with IPv4 if IPv6 cannot connect. If this occurs, these applications were previously leaking outside of the VPN tunnel.
    • NEW: A new QoS option to 'Suspend' QoS without causing a router reboot. This option turns off QoS, but does NOT restart CTF (HW Acceleration). Suspended status will be reset on a reboot.
    • OpenVPN client options 'persist-tun' and 'persist-key' are not longer added by default to the OpenVPN configuration. If desired, they may be added in the Custom Configuration section. They will also be set if part of an imported .ovpn file.
    • NEW: Add direction labels to traffic monitor summary data
    • Fix for LED Stealth and Power-LED modes not working on the ARM routers
    • Fix for moving ssh certs to JFFS
    • Fix to add missing 'ip6tables-save' command


    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:
    (Default Build - All supported routers)
    3685b9864c421deedc44fd5e77b23592e1e874f5c5f29822d5617b39ba987eaa  RT-AC56U_374.43_28E8j9527.trx
    90d9574ff289df0d9390c766b0f296b18534067db8957ab3ed2830b587888493  RT-AC66U_374.43_28E8j9527.trx
    051f3cba12d57d4e734f6ab7465144b84c0a33ee4fcdb42df1e57f9cce7fbce8  RT-AC68U_374.43_28E8j9527.trx
    0a1cb8db2add55748f7bd4f808a1ccb4037db8d518a17ca92130ee451988d6ba  RT-N16_374.43_28E8j9527.trx
    d0c245d7ab5dcbe6f8fe0b90c6140499f86f5118e10e0a35caf25669cb09d6f0  RT-N66U_374.43_28E8j9527.trx
    
    (Legacy Only Builds)
    51d97b784a2ac237f76e8c98c03eaaaa4e96f64a638a3e825ad521e3b99cf6ec  RT-AC68U_3.0.0.4_374.43_2-28L8j9527.trx
    65b3b0bc0c63e3af521cd4b649383268e447d4a5facff2bdd8b369fe900beabf  RT-AC56U_3.0.0.4_374.43_2-28L8j9527.trx
    
     
    Last edited: Nov 20, 2017 at 2:55 PM
  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:
    490
    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,750
    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:
    490
    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:
    490
    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,271
    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:
    490
    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:
    490
    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,750
    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,750
    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,750
    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:
    490
    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:
    490
    Location:
    The Netherlands
    Running fine, nothing unusual seen in syslog. :)
     

    Attached Files:

  18. DrTeeth

    DrTeeth Senior Member

    Joined:
    Mar 29, 2013
    Messages:
    382
    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,271
    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