[Release] Asuswrt-Merlin 384.6 is now available

[john9527]

I'm pretty sure that @RMerlin will be well aware of the release of the code folks... give the man time to wake up!

+1
And everyone needs to remember he does this in his 'spare' time.....bugging him about a release may just slow things down....

 

[RMerlin]

I usually receive the GPL archives before you guys even see them on the website, since Asus uploads them on my FTP server. (this time it wasn't the case probably due to a change my hosting provider did with their FTP server, they are now making TLS mandatory for FTP access).

So far this one is looking good, I was able to successfully compile 384.7 with those binary blobs, so thankfully looks like those 382 blobs are still compatible with 384 code. The current latest blobs for the AC3200 are no longer compatible with the 384.7 GPL code however.

 

[AndreiV]

The current latest blobs for the AC3200 are no longer compatible with the 384.7 GPL code however.

384.6 works fine on my AC3200 , I see no need to worry about 384.7

Never could understand this obsession folk have with updating firmware every few weeks.

 

[shsdking]

Could you please help others how exactly you've done?
Many got a chinese version and now lost all other languages (leaving chinese and english) with last stock or Merlin.

I can do so, there's no technical problem. But there are some concerns:
- I've patched the binary thing only for RT-AC86U so far (obviously, had to recompile the firmware);
- It would require manual patching for every model and every time the component changes;
- It's a closed source component, so I guess that it'll become a violation of Asus user agreement (and God knows what else) if I make the hack public...

 

[Grisu]

I can do so, there's no technical problem. But there are some concerns:
- I've patched the binary thing only for RT-AC86U so far (obviously, had to recompile the firmware);
- It would require manual patching for every model and every time the component changes;
- It's a closed source component, so I guess that it'll become a violation of Asus user agreement (and God knows what else) if I make the hack public...

Hard to believe that allowing other languages could violate anything.
We only would need it for RT-AC86U, others dont have this problem right now.

Maybe @RMerlin can tell us what he thinks about it and if he could implement it in his fork.

UPDATE
Workaround for different language support maybe found here: https://www.snbforums.com/threads/t...o-english-on-asus-rt-ac86u.48807/#post-430139

 

[RMerlin]

Hard to believe that allowing other languages could violate anything.
We only would need it for RT-AC86U, others dont have this problem right now.

Maybe @RMerlin can tell us what he thinks about it and if he could implement it in his fork.

I used to remove that limitation, until Asus moved the target code into a closed source binary in a recent update. To me, that's a sign that they don't want me to mess with it, so I won't.

 

[bidi]

Never could understand this obsession folk have with updating firmware every few weeks.

it's the same as other people's obsession of trying to use security exploits daily. newer versions come with security patches.

 

[Grisu]

it's the same as other people's obsession of trying to use security exploits daily. newer versions come with security patches.

you forget that often security problems come WITH an update integrated in a new "feature".

 

[AllanO]

Asuswrt-Merlin 384.6 is now available for all supported models, except for the RT-AC87U

Newbie alert! Sorry if my questions seem trivial.

It's my first time on this forum and first time considering Asuswrt firmware on my 2 x AC86U and 1 x AC68U network using AIMesh. The standard firmware and AIMesh from ASUS has huge problems for me with 2.4ghz band completely trashed and I've had to just have the two 86U's running as a base and a repeater.

1) Does Asuswrt 384.6 support AIMesh?
2) The firmware filetype for the AC86U has changed and can't be loaded and I need a step by step newbie installation description. I assume it needs a factory reset and a CFG reload, but I want to make sure there are no gotchas.

Allan

 

[ColinTaylor]

1) No, Merlin does not support AiMesh on any router.
2) Just load the firmware through the WebUI as normal. A factory reset is advisable but do not reload a saved CFG file as that negates the purpose of the factory reset.

 

[M@rco]

The firmware filetype for the AC86U has changed

Make sure you don't mix up the firmware for the RT-AC68U (*.trx) and the RT-AC86U (*.w)... It's a common mistake.

 

[Grisu]

I used to remove that limitation, until Asus moved the target code into a closed source binary in a recent update. To me, that's a sign that they don't want me to mess with it, so I won't.

Is it allowed for him to post his solution for more languages in this forum?

 

[ColinTaylor]

Is it allowed for him to post his solution for more languages in this forum?

Maybe it's something that could be explained via PM, as the solution would only be of interest to those people capable of patching binary blobs and then compiling their own firmware. And then doing it all again every time a new firmware is released. So probably only applicable to a handful of people.

 

[AllanO]

1) No, Merlin does not support AiMesh on any router.
2) Just load the firmware through the WebUI as normal. A factory reset is advisable but do not reload a saved CFG file as that negates the purpose of the factory reset.

1) Understood. ASUS doesn’t appear to support AIMesh very well either... I have an active problem report with them for losing 2.4 ghz band and losing ability to support Airport Express or other models of small routers with audio jacks.
2) Factory reset is mandatory, I believe, when coming from the vendor firmware. The file type is not supported when Load attempted. I’m unclear about loading a saved CFG after going to Asuswrt? Are the formats incompatible?

 

[ColinTaylor]

2) Factory reset is mandatory, I believe, when coming from the vendor firmware.

There might be something in the release notes for a specific release, but generally the installation instructions say:

• If coming from a non-Asuswrt firmware, you will have to do a factory default reset.
• While it is generally not necessary to restore to factory defaults, it's not a bad idea, especially if there is a big jump in version number (e.g. from 112 to 178).

The file type is not supported when Load attempted.

You are loading the wrong firmware then. See M@rco's post.

I’m unclear about loading a saved CFG after going to Asuswrt? Are the formats incompatible?

Asuswrt is the name of the stock Asus firmware, Asuswrt-Merlin is the name of Merlin's. The CFG file contains a backup of the user and low-level system settings. The point of doing a factory reset is to erase the current settings and let the new firmware generate the new default values. Reloading the CFG file defeats this purpose.

 

[RMerlin]

Is it allowed for him to post his solution for more languages in this forum?

On a forum that gets visited by Asus employees? I don't recommend it... It will only drive them into taking more drastic measures to prevent such hacks from happening in the future, which generally results in more headaches for me to deal with.

Users that are affected by this would be better to contact Asus directly, and explain their case, in hopes that if enough legitimate customers complain, they might change their mind.

 

[Grisu]

Maybe it's something that could be explained via PM, as the solution would only be of interest to those people capable of patching binary blobs and then compiling their own firmware. And then doing it all again every time a new firmware is released. So probably only applicable to a handful of people.

Ok, will PM him how he did.

 

[shsdking]

On a forum that gets visited by Asus employees? I don't recommend it... It will only drive them into taking more drastic measures to prevent such hacks from happening in the future, which generally results in more headaches for me to deal with.

Users that are affected by this would be better to contact Asus directly, and explain their case, in hopes that if enough legitimate customers complain, they might change their mind.

Exactly that is why I was reluctant to publicly tell how I fixed it for myself...
Although would be really nice if someone (an ASUS employee?) could explain what is the reason of not allowing me to switch to English in a Japanese model.
Looking at how faithfully they keep fighting against changing the interface language I can only think of some really serious concern. The Japanese model isn't any cheaper than its international analogues - so it's not about the price. There could be a legal reason (we know that WiFi frequencies and TX power are different among regions), but as a customer I can't see why I have to struggle with the Japanese interface using the router in Japan. I even heard a guess that they might have to independently certify every language in Japan, which costs extra money for ASUS - but I don't know how much truth is there in this rumor.
Anyway, it's quite obvious that they are not going to change their mind regardless of customer complaints. And it's not just ASUS in fact, many other companies have special versions of their products for Japan, where the only language available is Japanese.
I wonder if there is a similar reason for China.

 

[MoonPie2000]

I am confused by some earlier conversation about 3200 support - will 3200 continue to be supported or has Asus discontinued their support resulting in Merlin discontinuing development of new firmware for 3200 after this release? Thanks...

 

[RMerlin]

Exactly that is why I was reluctant to publicly tell how I fixed it for myself...
Although would be really nice if someone (an ASUS employee?) could explain what is the reason of not allowing me to switch to English in a Japanese model.

The second-hand information I received (i.e. not from Asus themselves) was to combat grey market, since some Japanese models were selling for far less than in other regions. So maybe that's the case for very specific markets, I don't know.

So basically, it was purely a business decision.

I am confused by some earlier conversation about 3200 support - will 3200 continue to be supported or has Asus discontinued their support resulting in Merlin discontinuing development of new firmware for 3200 after this release? Thanks...

Note sure why you would think that, I never said anything about dropping the RT-AC3200.