Release [FORK][DSL] GNUton's Merlin builds for DSL Router 386.1_2 released.

  • ATTENTION! As of November 1, 2020, you are not able to reply to threads 6 months after the thread is opened if there are more than 500 posts in the thread.
    Threads will not be locked, so posts may still be edited by their authors.
    Just start a new thread on the topic to post if you get an error message when trying to reply to a thread.

GNUton

Senior Member
Hi there,
Today I wanted to finally make available to a big audience the 386 builds for DSL-AC68U and DSL-AX82U.
The build is based on tha latest stable upstream Merlin code.
As always I wanna thank a lot to the @RMerlin and a kudos also to all people who have contibuted to test the DSL-AC68U builds.

I hope to see the same enthusiams for the DSL-AX82U as soon as it gets on the shelves.

Instruction for flashing the firmware.
1. Download the latest image for your model from here. Please download the .trx for DSL-AC68U or the .w for DSL-AX82U.
2. Open http://router.asus.com/Advanced_FirmwareUpgrade_Content.asp in your browser and upload the image
3. Please reset to factory if you are upgrading from stock.

In case you want to revert back to stock firmware. Please download the .trx or .w image from the asus website/support page/your router
And repeat the points 2 and 3.

Enjoy!

PS:
To directly download that firmware for your model - chose from one of the following links ...
DSL-AC68U - https://github.com/gnuton/asuswrt-m...n1/DSL-AC68U_386.01_2-gnuton1_DSL_1.0.5.2.trx
DSL-AX82U - https://github.com/gnuton/asuswrt-m...1/DSL-AX82U_386.01_2-gnuton1_cferom_pureubi.w
 
Last edited:

Osman Elitok

Occasional Visitor
congratulations !
 

Osman Elitok

Occasional Visitor

Zendilar

Regular Contributor
I am sure that very soon Gnuton will add the ability for coffee making onto the firmware:) (Thank you mate for all the grate updates and upgrades)
 

Mr Tvardovsky

Regular Contributor
Thank you, Gnuton! And a quick question: When going from your previous stable build (384.17), will the dirty (direct) upgrade be sufficient, or would you recommend a factory reset following the installation?
 

Zendilar

Regular Contributor
Thank you, Gnuton! And a quick question: When going from your previous stable build (384.17), will the dirty (direct) upgrade be sufficient, or would you recommend a factory reset following the installation?
Just flash the new firmware, I have never reset to factory since 384.10 and never had a problem.
 

julezman

New Around Here
Just flash the new firmware, I have never reset to factory since 384.10 and never had a problem.
@Mr Tvardovsky - I found that the webui would not display for about an hour after I had upgraded from 384.17_0-gnuton1. The login page would appear and accept credentials OK but then that would be it; the main web UI would not load or display. The router was otherwise working OK. However it was showing very heavy CPU usage after the upgrade initially. Once CPU usage had calmed down, the webui worked fine and seems really quick. Maybe there are some post upgrade scripts\migration that take run initially.

Thanks @GNUton for another great release!
 

Zendilar

Regular Contributor
@Mr Tvardovsky - I found that the webui would not display for about an hour after I had upgraded from 384.17_0-gnuton1. The login page would appear and accept credentials OK but then that would be it; the main web UI would not load or display. The router was otherwise working OK. However it was showing very heavy CPU usage after the upgrade initially. Once CPU usage had calmed down, the webui worked fine and seems really quick. Maybe there are some post upgrade scripts\migration that take run initially.

Thanks @GNUton for another great release!
That procedure was normal read my post here https://www.snbforums.com/threads/d...8u-are-now-available.68295/page-3#post-652386
 

JGrana

Very Senior Member
A quick note for users of @GNUton 's DSL builds - he has been added to the Developers Donation link page:


If you want to thank GNUton and make a donation, you will find his donation link on that page.
 

kernol

Very Senior Member
Hi!
I do not think I can make it sticky, or I dunno how to do that if possible.
Only way to achieve that is to make an appeal to @RMerlin to remove the old sticky thread for your DSL firmware and make the latest Release thread sticky.

I recall that Eric is not keen on sticky threads because clearly many folk don't bother to read them ... however it makes sense to me that John's Fork and your Fork should be in the sticky spot ... because otherwise they get buried in the proliferation of individual threads and so many first time potential users will never even know there is Merlinware for their Routers models.

Good luck - and SO pleased you have not only continued to provide DSL-AC68U firmware - but have also added another DSL model to the mix :D.
 

GNUton

Senior Member
If the policy of the forum is not to have sticy threads, that's fine for me.
For each new release I am going to have two threads, release and pre-release:
 

Mr Tvardovsky

Regular Contributor
Hi @GNUton and All, here is a short recap of my experience:
- I dirty-flashed the latest 386.1_2 on my DSL-AC68U on Thursday. I was able to access GUI and SSH into the router immediately, without any interruption.
- It worked perfectly in my setup (see my signature - not updated yet) for 2 days.
- Then I decided that since all my devices are now on the latest 386.1_2 firmware, I would combine them all in one AiMesh setup (with the DSL-AC68U as the AiMesh router and the Ac66U_B1s as nodes).

Unfortunately, this plan failed:
- At the first attempt, I managed to add all 3 nodes. The setup worked normally for about an hour and then out of the sudden the nodes got disconnected from the main DSL router. I tried to log in to the router to re-connect them, but at this point this the GUI became unavailable (I tried also SSH and the iOS ASUS router app - nothing). But the LAN ports and WiFi on the main router worked.
- I performed a (WPS) factory reset on the DSL, did some M&M config, and tried to setup the AiMesh again. This time things crashed after adding the second node - with the same symptoms as by the first attempt.

Not sure what is the root cause of my failure. Anyway, I am reporting it in the hope it may help to fine-tune this great fork.
 
Last edited:

RMerlin

Asuswrt-Merlin dev
If the policy of the forum is not to have sticy threads, that's fine for me.
For each new release I am going to have two threads, release and pre-release:
I suggest you create a new "generic" post like John did that I can make sticky. That post could then point to whatever are the latest beta/release threads, you will just have to edit the new sticky when you start new beta/release threads.
 

GNUton

Senior Member
Hi @GNUton and All, here is a short recap of my experience:
- I dirty-flashed the latest 386.1_2 on my DSL-AC68U on Thursday. I was able to access GUI and SSH into the router immediately, without any interruption.
- It worked perfectly in my setup (see my signature - not updated yet) for 2 days.
- Then I decided that since all my devices are now on the latest 386.1_2 firmware, I would combine them all in one AiMesh setup (with the DSL-AC68U as the AiMesh router and the Ac66U_B1s as nodes).

Unfortunately, this plan failed:
- At the first attempt, I was managed to add all 3 nodes. The setup worked normally for about an hour and then out of the sudden the nodes got disconnected from the main DSL router. I tried to log in to the router to re-connect them, but at this point this the GUI became unavailable (I tried also SSH and the iOS ASUS router app - nothing). But the LAN ports and WiFi on the main router worked.
- I performed a (WPS) factory reset on the DSL, did some M&M config, and tried to setup the AiMesh again. This time things crashed after adding the second node - with the same symptoms as by the first attempt.

Not sure what is the root cause of my failure. Anyway, I am reporting it in the hope it may help to fine-tune this great fork.
Hi,
Sad to the hear that.
I have tested AiMesh only with two devices and it worked out for me.
Other people have been running AiMesh with DSL-AC68U and several RT routers for all time we had alphas and betas and as far as I know they just got some issues with guest network that have been partially fixed. But AiMesh is supposed to work.
Do you get any issue also when running two nodes only?
Has anybody else experienced this also?
 

Mr Tvardovsky

Regular Contributor
Hi,
Sad to the hear that.
I have tested AiMesh only with two devices and it worked out for me.
Other people have been running AiMesh with DSL-AC68U and several RT routers for all time we had alphas and betas and as far as I know they just got some issues with guest network that have been partially fixed. But AiMesh is supposed to work.
Do you get any issue also when running two nodes only?
Has anybody else experienced this also?
By the second attempt the issue appeared after adding the second node. I am clear that many alpha- and beta-testers had no problems with AiMesh, so I tend to think it may be faulty hardware of my DSL-AC68U. Anyway, it continues working well as a wireless node with a RT-AC66U_B1 as an AiMesh router :)
 

Latest threads

Sign Up For SNBForums Daily Digest

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