Release Asuswrt-Merlin 384.19 is now available

[ugandy]

I am having some random wifi freeze issue (AC68U 384.17) and plan to upgrade to see any difference.

Looks that most of issues are for AC86U etc, I assume it is safe for AC68U?
To ensure clean install, are these the correct steps: hard reset, upgrade to 384.19 and then another hard reset?

and jffs format i think

 

[henry8866]

and jffs format i think

Thanks.
Another question, after hard reset and reboot, does it have wifi turn on by default, or have to connect to it wired?

 

[ugandy]

Thanks.
Another question, after hard reset and reboot, does it have wifi turn on by default, or have to connect to it wired?

i find it simpler to do it wired with a laptop

 

[Ronald Schwerer]

Thanks.
Another question, after hard reset and reboot, does it have wifi turn on by default, or have to connect to it wired?

Yes, but SSID will change to ASUS (and ASUS_5G IIRC). Plus it's unprotected until you get it configured (no password), so don't procrastinate in finalizing the config.

 

[username0475]

There is the rare case where the jffs does not need to be formatted. As in the case of my AC86U. The jffs was resized and mounted after flashing 384.19.
So, if your /jffs shows as mounted and remounts after a reboot a format is no needed.

How do I see this that the JFFS as mounted?

 

[bbunge]

How do I see this that the JFFS as mounted?

Tools/Internal Storage/JFFS

 

[mine25]

Hello everyone! A question regarding AIProtection notifications on AC86U with Merlin 384.19: I am still receiving "Malicious Sites Blocking" email alerts, even after unchecking the option in GUI. I tried restarting the router, but no change. Any suggestions?

.

 

[Aldione]

I am having some random wifi freeze issue (AC68U 384.17) and plan to upgrade to see any difference.

Looks that most of issues are for AC86U etc, I assume it is safe for AC68U?
To ensure clean install, are these the correct steps: hard reset, upgrade to 384.19 and then another hard reset?

Same issues... did you fix it with Clean install??

i have the issue with the aimesh, i have on the main 384.19 and node asus firm Version 3.0.0.4.384.82072 and the node doesnt work the wifi. i'm thinking to install merlin on both with Clean Install.

good idea?

 

[MarkyPancake]

i have the issue with the aimesh, i have on the main 384.19 and node asus firm Version 3.0.0.4.384.82072 and the node doesnt work the wifi. i'm thinking to install merlin on both with Clean Install.

I've been running an AiMesh setup for several months now with an AC86U router and AC68U node and have always used Merlin firmware on both. Currently running 384.19 on the router and node and it's working without a hitch and is a solid setup for me.

 

[calzor suzay]

I've been running an AiMesh setup for several months now with an AC86U router and AC68U node and have always used Merlin firmware on both. Currently running 384.19 on the router and node and it's working without a hitch and is a solid setup for me.

So Asuswrt merlin works fully with both nodes on it?
Even the changelog recomedends your 'node' as original Asus firmware if I read this right

384.13 (31-July-2019)
- NEW: AiMesh Router and node support. Note that automatic live update of Merlin-based nodes is not supported, you will have to manually update any Merlin-based nodes when a new firmware is available. Asus-based nodes (which is recommended) will be able to make use of the automatic live update.

I currently have an AC68U only but it's starting to creak with my demands and considering adding the AC86U is the primary with the 68 as the node.

 

[QuikSilver]

So Asuswrt merlin works fully with both nodes on it?
Even the changelog recomedends your 'node' as original Asus firmware if I read this right

384.13 (31-July-2019)
- NEW: AiMesh Router and node support. Note that automatic live update of Merlin-based nodes is not supported, you will have to manually update any Merlin-based nodes when a new firmware is available. Asus-based nodes (which is recommended) will be able to make use of the automatic live update.

I currently have an AC68U only but it's starting to creak with my demands and considering adding the AC86U is the primary with the 68 as the node.

You're referring to a changelog from 2019 and firmware 384.13 while the newest is 349.19.

 

[bluzfanmr1]

How do I see this that the JFFS as mounted?

You can use the mount command via ssh:

mount

/dev/mtdblock4 on /jffs type jffs2 (rw,noatime)

 

[Matthew Patrick]

Guys. In a few days I'm gonna fully reset my router. Since my usb that holds my amtm scripts etc just died (1 year sandisk ultra. The fit one. Not good since last week I saw using tune2fs that it's only been used at about 1TB) . I got a new sandisk max endurance 32gb for quite cheap and it should be able to hold of 100+ TBW afaik .

Now I'm on an AC86U and I've been keeping up to date with this thread and I know that jffs format and normal format is necessary to clean start it, but do I need to do the wps wipe thingy? Does it actually do anything different? Since I think I saw that wps wipe is kinda different in AC86U. Thanks !

 

[calzor suzay]

You're referring to a changelog from 2019 and firmware 384.13 while the newest is 349.19.

Yes but then no mention of it since then to 349.19 which I'm on, no mention of it searching for "aimesh" so one would conclude nothing has changed since then.

 

[QuikSilver]

Yes but then no mention of it since then to 349.19 which I'm on, no mention of it searching for "aimesh" so one would conclude nothing has changed since then.

Nothing from Merlin's side because as Merlin has said before it is closed source.

 

[calzor suzay]

My point being the changelog did and still does recommend using an Asus based node whereas MarkyPancake says they are using Merlin on both so I asked if this works fully aka well, no issues etc. out of interest as I might take this path in the near future.

I'm not sure what your problem is other than stating a fact I'd already quoted.

 

[QuikSilver]

I'm not sure what your problem is other than stating a fact I'd already quoted.

You asked a question regarding AiMesh. I made an observation regarding the outdated firmware that I assumed you were on since you provided none. I then answered your question again regarding AiMesh. My apologies if you thought "I have a problem" but I thought an answer to your question would be of use either to you or others who browse this thread. I can refrain from answering your questions in the future though.

 

[Vimes]

Per my earlier posts, the issues with the /JFFS + AC86U + many AMTM scripts (J* scripts) which default to using the /JFFS, have to do with the heavier I/O workload actually hitting the /JFFS. The J* scripts write A LOT to the /JFFS file system unless you set them to use the /USB filesystem. Under 384.19 that higher I/O rate appears to lead to the NAND the /JFFS is running on not being able to perform GC (garbage collection) b/c it cannot juggle and consolidate all the "used but not released" space being deleted with the blocks it needs to perform that consolidation properly. The TLDR: details on how NAND works is beyond the scope of this thread. But quick summary for those that care...is when the /JFFS NAND is written to so often, it seems with 384.19 the /JFFS NAND does not have time (or space) to properly perform GC (garbage collection). A symptom of that is GC and other related errors start appearing. When that happens, the /JFFS becomes "read-only / out-of-space" and it's game over. Most of us who had been running the 384.18 + many of the AMTM scripts were using the /JFFS as the storage target. Doing the same on 384.19 seems to lead to the GC issues. At first it was blamed on "you have corrupt files" on the existing /JFFS which one backed up and restored it properly and that could be very true. But then 384.18 + same scripting was not generating nor was the NAND complaining about GC errors and was running great for months. YMMV.

For those of you with an AC86U + 384.19 + running LITTLE ELSE from AMTM or just a handful of custom scripts which do not hammer the /JFFS with I/O, then all indications I have, are you will likely to have few issues with AC86U + 384.19 if you follow the guidelines.

Others have have been reporting wireless issues... but I have seen none of those b/c I fix the channels to set bands, and turn off all the "Smart" stuff and few other wireless BP which are documented for stability elsewhere in our community.

My current 384.19 + AC86U + several (but not all of the J* scripts) has now been up ~ 10 days. Before it would stay up maybe 24 hours before rebooting itself or start having GC issues. (I also turned off AI Protect which stopped the unplanned reboots) I've gotten this far only after several "AC86U ASUS HARD Factory Resets" (look that up) and starting over from ground zero with every setting on every page. The family was howling about the constant issues so at this point, I'm just leaving it be for now until I get all the J* scripts running again without /JFFS NAND or other reboot issues. Stay safe, stay alive.

Great news that you seem to have found stability with this build, I do hope that it continues for you. It has been a rough journey for some of us.

 

[MarkyPancake]

So Asuswrt merlin works fully with both nodes on it?

Since I decided to dust off my AC68U and try it out as an AiMesh node, both the router and node have only used Merlin firmware. I haven't used ASUS' stock firmware for years.

My AC86U was on Merlin 384.17 when I first added the AC68U as a node, so I updated it to that version, then when 384.18 came out, I updated the router and node to that version, and now both are on 384.19. No issues with my mesh setup on any of these Merlin versions in my environment.

 

[calzor suzay]

Since I decided to dust off my AC68U and try it out as an AiMesh node, both the router and node have only used Merlin firmware. I haven't used ASUS' stock firmware for years.

My AC86U was on Merlin 384.17 when I first added the AC68U as a node, so I updated it to that version, then when 384.18 came out, I updated the router and node to that version, and now both are on 384.19. No issues with my mesh setup on any of these Merlin versions in my environment.

Thanks and sounds good, I might keep my eye out for any deals on 86Us