[Release] Asuswrt-Merlin 384.14 (and 384.13_2) are now available

[luckyseven]

Cannot upgrade from .14 beta2 on the AC86U.

Firmware upgrade unsuccessful. This may result from incorrect image or error transmission. Please check the version of firmware and try again.

 

[EmeraldDeer]

Cannot upgrade from .14 beta2 on the AC86U.

Firmware upgrade unsuccessful. This may result from incorrect image or error transmission. Please check the version of firmware and try again.

I got the same error upgrading from 384.13 to 384.14 on an RT-AX88U. The SHA-256 hash matched so I know the firmware download was not corrupted.

When I tried a second time, it worked.

 

[DarkWolfSLV]

I'm experiencing a few IPv6 errors on 384.13, let's see if this fix it.
more info here: https://www.snbforums.com/threads/ipv6-bug.60641/

 

[luckyseven]

I got the same error upgrading from 384.13 to 384.14 on an RT-AX88U. The SHA-256 hash matched so I know the firmware download was not corrupted.

When I tried a second time, it worked.

Thanks, but after trying 5 times both with wireless and wired, I did a system restore, and then it worked.

 

[dev_null]

Try setting the channel width bandwidth to 40mhz

...and make sure that you select a specific channel active in your region. Sometimes "auto" channel causes problems (I experienced this more on 5gHz, but other have reported it on 2.4gHz).

 

[macster2075]

so is the updated firmware stable to use for the RT68P or should I keep waiting for the next update? - I just don't want to install it if it's not 100% as I am not experiencing any issues with 384.13.

 

[miroco]

Don't fix something that isn't broken!

 

[D_Day]

Updated to 384.14 from beta 3, 4 days uptime and not a single problem. Running AC86U and AC68U as AiMesh with connected Usb3 HDD with no access problems whatsoever.
If I’m being picky the only issue I have spotted is with web history by device, it initially loads the device history but then floods with the other device history but it not a problem for me.
Great work Merlin

 

[JaimeZX]

Thanks for the update man!

 

[consorts]

simple question,

for ac3100 (on 384.13 now)

which should i go with?

384.14 or 384.13_2

 

[dave14305]

simple question,

for ac3100 (on 384.13 now)

which should i go with?

384.14 or 384.13_2

Only 384.14 is available for AC3100.

 

[bbunge]

so is the updated firmware stable to use for the RT68P or should I keep waiting for the next update? - I just don't want to install it if it's not 100% as I am not experiencing any issues with 384.13.

You should be OK. My AC66U_B1 runs like a champ and I am updating two AC68U's tomorrow.
Should add that .14 fixed a memory leak on the AC68U's.

 

[consorts]

Only 384.14 is available for AC3100.

ok, but what does that mean? will 13_2 come out later for ac3100, or is 13_2 not appropriate for ac3100?

sorry to ask for clarification, but i can't understand the gobbledygook merlin wrote in the OP

 

[dave14305]

ok, but what does that mean? will 13_2 come out later for ac3100, or is 13_2 not appropriate for ac3100?

sorry to ask for clarification, but i can't understand the gobbledygook merlin wrote in the OP

13_2 was a special build for those few models not able to get .14 due to Asus not releasing necessary code for them. An awesome gesture by Merlin.

 

[htismaqe]

I'm definitely having issues with 384.14 stable. I have to wonder if it's not something with DHCP causing it. Yesterday I noted that my router locked up when I unplugged the WAN cable and plugged it back in. Today, I turned up a new Roku TV that had never been on the network before and when I plugged in the network cable to the switch, it requested a DHCP address and my router GUI locked up. I could ping and pass traffic but couldn't login to the router at all via HTTPS. I ended up having to hard reboot it.

 

[Snoopotic]

Hi,
someone already asked but it did not get an answer:
I have a RT-AC88U and came from .13 to .14

After 23 hours all looks good so far and is running but there are lot of mog messages from dnsmasq:

Dec 18 11:39:23 tackaman dnsmasq-script[2237]: connect error: No such file or directory
Dec 18 11:39:23 tackaman dnsmasq-script[2237]: [SEND_AMAS_NODE_EVENT:(4684)] ERROR connecting:No such file or directory.
Dec 18 11:39:23 tackaman dnsmasq-script[2237]: connect error: No such file or directory
Dec 18 11:39:23 tackaman dnsmasq-script[2237]: [SEND_AMAS_NODE_EVENT:(4684)] ERROR connecting:No such file or directory.
Dec 18 11:39:23 tackaman dnsmasq-script[2237]: connect error: No such file or directory
Dec 18 11:39:23 tackaman dnsmasq-script[2237]: [SEND_AMAS_NODE_EVENT:(4684)] ERROR connecting:No such file or directory.
Dec 18 11:39:23 tackaman dnsmasq-script[2237]: connect error: No such file or directory
Dec 18 11:39:23 tackaman dnsmasq-script[2237]: [SEND_AMAS_NODE_EVENT:(4684)] ERROR connecting:No such file or directory.
Dec 18 11:39:23 tackaman dnsmasq-script[2237]: connect error: No such file or directory
Dec 18 11:39:23 tackaman dnsmasq-script[2237]: [SEND_AMAS_NODE_EVENT:(4684)] ERROR connecting:No such file or directory.
Dec 18 11:39:23 tackaman dnsmasq-script[2237]: connect error: No such file or directory
Dec 18 11:39:23 tackaman dnsmasq-script[2237]: [SEND_AMAS_NODE_EVENT:(4684)] ERROR connecting:No such file or directory.
Dec 18 11:39:23 tackaman dnsmasq-script[2237]: connect error: No such file or directory
Dec 18 11:39:23 tackaman dnsmasq-script[2237]: [SEND_AMAS_NODE_EVENT:(4684)] ERROR connecting:No such file or directory.
Dec 18 11:39:23 tackaman dnsmasq[2237]: failed to send packet: Operation not permitted
Dec 18 11:39:23 tackaman dnsmasq[2237]: failed to send packet: Operation not permitted
Dec 18 11:39:23 tackaman dnsmasq[2237]: failed to send packet: Operation not permitted
Dec 18 11:39:23 tackaman dnsmasq[2237]: failed to send packet: Operation not permitted
Dec 18 11:39:23 tackaman dnsmasq[2237]: failed to send packet: Operation not permitted
Dec 18 11:39:23 tackaman dnsmasq[2237]: failed to send packet: Operation not permitted
Dec 18 11:39:23 tackaman dnsmasq[2237]: failed to send packet: Operation not permitted
Dec 18 11:39:23 tackaman dnsmasq[2237]: failed to send packet: Operation not permitted
Dec 18 11:39:23 tackaman dnsmasq[2237]: failed to send packet: Operation not permitted

Is there an explanation? I am using DoT mainly if this is related. Can I do something to analyse it further with your help? thanks.

 

[thaMini]

Any chance the AX92u will be supported for this build ?

 

[DocUmibozu]

Well, I can confirm that this firmware is not as stable as previous version.
My two Ac66u refused for the second time in two days to login via web interface.
I can login via ssh but every command I issue it hangs.
384.13 had a uptime of 63 days when I installed 384.14.

 

[RMerlin]

Any chance the AX92u will be supported for this build ?

No.

 

[The Chief]

LetsEncrypt cert issue is still here.

Dec 18 21:24:49 kernel: Cert success.
Dec 18 21:24:49 kernel: cat: write error: Invalid argument

And cert.pem/chain.pem nor created, nor updated properly.