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

[cybrnook]

1.4 (GHz?) or 2.0.0.6?

Sorry, 1.4 Ghz.

I normally only ever modified the CFE to bake in high clock values. That and cross flashing the R7000/EA6900 in the past.

 

[jrmwvu04]

Sorry, 1.4 Ghz.

I normally only ever modified the CFE to bake in high clock values. That and cross flashing the R7000/EA6900 in the past.

My interests are elsewhere, with DFS

 

[john9527]

1.4 (GHz?) or 2.0.0.6?

He's just teasing everyone since he is helping in the development of my fork build that supports the later rev AC68 variants (He's running an AC1900P, stock clock is 1400 MHz).

Cleaning up a few loose ends.....public beta is around the corner

 

[cybrnook]

My interests are elsewhere, with DFS

If you have time now, hggomes's collection has the 1900P (2.0.0.6) in there. You could poke at that one.

https://www.snbforums.com/threads/asus-routers-cfe-dumps-collection.17793/

 

[john9527]

A small update to keep things current.....

LATEST RELEASE: Update-26E4
5-August-2017
Merlin fork 374.43_2-26E4j9527
Download http://bit.ly/1YdgUcP
============================

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)
• Added missing samba36 file to the git repo - @Santiago C

As always, a reminder to have a backup of /jffs in case the jffs space needs to be reformatted due to increases in firmware size.

SHA256

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

 

[MarCoMLXXV]

A small update to keep things current.....

... and the level of tension continues to mount ...

 

[john9527]

... and the level of tension continues to mount ...

LTS Beta for the new rev AC68U router is out! Going to track this one in a separate thread
https://www.snbforums.com/threads/fork-374-43-lts-beta-for-new-rev-ac68u-routers.40610/

 

[MarCoMLXXV]

Awesome! <insert cheering emoticon here>
Thanks @john9527 for coding and @cybrnook for risking the wrath of the lady of the house.

Now got to find some time to make a fresh start... (summer holidays here, nine-year-old at home, so this takes careful planning But it'll be soon...

 

[MarCoMLXXV]

The following routers were released after the base code used for this fork was available, and are NOT supported.

• ... AC68U Rev C1 and E1 ...

Maybe an idea to link to the beta fork for the models mentioned above in the first post?

 

[john9527]

Maybe an idea to link to the beta fork for the models mentioned above in the first post?

Done....Thanks!

 

[R1-Limited]

Its true I am leaving the Johns Fork and returning to Merlin, I know Shocked huh, I understand.

Sorry, just cannot deal with constantly having to reboot my routers to get IP address's Was fine until the last build again.

Best of luck all

 

[john9527]

Its true I am leaving the Johns Fork and returning to Merlin, I know Shocked huh, I understand.

Sorry, just cannot deal with constantly having to reboot my routers to get IP address's Was fine until the last build again.

Best of luck all

Use whichever works best for you......if it's Merlin, great. In all honesty, I hadn't changed anything that would affect Media Bridge between the builds you say worked and those that didn't because I couldn't identify anything to fix. Whatever is affecting your setup, I don't know what it is, even after tearing down my setup and putting in a Media Bridge just to test. I hope that Merlin works out better for you.

 

[jrmwvu04]

Well I, on the other hand, am adding the fork to a previously unsupported model through some kind of programming black magic.

 

[thelonelycoder]

Question about the dual WAN settings:

(ignore the text overlay, that is for another script)
The numbers do not add up, compared to Merlin calculations, can you elaborate why?

In Merlin the following is true:
Failover is: Interval*Failover
Failback is: Interval*Failback

In your 26E3 this appears to be this:
Failover is: Interval*Failover
Failback is: (Interval+Delay)*Failback
Now, if I test it with this formula, the actual times are higher than the calculate ones.
Say, Failover is 4*2 = 6 seconds. But the failover kicks in much later, at about 12 seconds.
The same is for Failback time.

Is there a reason why they are off by a large margin in your fork?
In Merlin I can count on these calculations, they work 100% accurate, at least since 380.67.

 

[john9527]

Is there a reason why they are off by a large margin in your fork?

The answer is.....I have no idea. Someone would have to try to do a compaison going through their uncommented code. And since I have no way to test dual-wan, it's not something I'm really inclined to try.

 

[thelonelycoder]

The answer is.....I have no idea. Someone would have to try to do a compaison going through their uncommented code. And since I have no way to test dual-wan, it's not something I'm really inclined to try.

I thought you were tinkering in that field an expected a clarifying replay...
No problem, I'll figure it out.

 

[RMerlin]

Someone would have to try to do a compaison going through their uncommented code.

Earlier today, I was telling another firmware developer how the wanduck code should be thrown into a room, a grenade tossed into that room, and the door locked.

 

[john9527]

I thought you were tinkering in that field an expected a clarifying replay...
No problem, I'll figure it out.

I tinkered with a couple of things on some specific issues, but nothing comes immediately to mind. I'll take a look to see if anything pops out.

 

[john9527]

Earlier today, I was telling another firmware developer how the wanduck code should be thrown into a room, a grenade tossed into that room, and the door locked.

LOL.....can I pull the pin?

 

[thelonelycoder]

LOL.....can I pull the pin?

Need a helping hand?