Release Asuswrt-Merlin 386.9 is now available for AC models

[diabolyk]

It would likely help others if you posted the portion of the log before, and including, the reboot (if possible) which may give a clue as to what caused the reboot.

I don't know why but i have nothing before this....

 

[Traderdude]

Hi I think there is a problem with the latest update file I have tried several times I'm on a mesh system and it fails every time to update. I've never had any issues ever before. I just wondering if it could be the wrong file by any chance? RT-ac-86u

 

[Traderdude]

Hi I'm using an rt-ac68u there is a problem with the latest update it is the wrong file format it needs to be a trx file format

 

[ColinTaylor]

Hi I'm using an rt-ac68u there is a problem with the latest update it is the wrong file format it needs to be a trx file format

It is a trx file. Perhaps you downloaded the firmware for a different model, like the RT-AC86U.

 

[bennor]

Hi I'm using an rt-ac68u there is a problem with the latest update it is the wrong file format it needs to be a trx file format

There isn't a problem. No issues updating an RT-AC68U to 386.9 on my end. Make sure to download the correct file (RT-AC68U_386.9_0.zip). Extract (or uncompress) the "AC68U_386.9_0.zip" file contents, and there should be a file called: RT-AC68U_386.9_0.trx among the four extracted/uncompressed files.

Edit to add: If using AImesh, make sure to update the main router first.

 

[[Daniel]]

Successful dirty Update from RT-AC86U_386.5 to RT-AC86U_386.9... only a few minutes have gone by, but so far so good.

 

[Brczko]

Hello all,

since the update to 386.9 I see in my syslog following entries. It repeats every day at 5:09, 11:09, 17:09 and 23:09 and every time it is about 295 rows.

Jan 10 05:09:45 kernel: EXT4-fs error (device sda1): ext4_readdir:198: inode #11: block 8485: comm find: bad entry in directory: rec_len is smaller than minimal - offset=0(0), inode=0, rec_len=2, name_len=0
Jan 10 05:09:45 kernel: EXT4-fs error (device sda1): ext4_readdir:198: inode #11: block 8485: comm find: bad entry in directory: rec_len is smaller than minimal - offset=0(0), inode=0, rec_len=2, name_len=0
Jan 10 05:09:45 kernel: EXT4-fs error (device sda1): ext4_readdir:198: inode #11: block 8485: comm find: bad entry in directory: rec_len is smaller than minimal - offset=0(0), inode=0, rec_len=2, name_len=0
Jan 10 05:09:45 kernel: EXT4-fs error (device sda1): ext4_readdir:198: inode #11: block 8485: comm find: bad entry in directory: rec_len is smaller than minimal - offset=0(0), inode=0, rec_len=2, name_len=0
Jan 10 05:09:45 kernel: EXT4-fs error (device sda1): ext4_readdir:198: inode #11: block 8485: comm find: bad entry in directory: rec_len is smaller than minimal - offset=0(0), inode=0, rec_len=2, name_len=0
Jan 10 05:09:45 kernel: EXT4-fs error (device sda1): ext4_readdir:198: inode #11: block 8485: comm find: bad entry in directory: rec_len is smaller than minimal - offset=0(0), inode=0, rec_len=2, name_len=0
Jan 10 05:09:45 kernel: EXT4-fs error (device sda1): ext4_readdir:198: inode #11: block 8485: comm find: bad entry in directory: rec_len is smaller than minimal - offset=0(0), inode=0, rec_len=2, name_len=0
Jan 10 05:09:45 kernel: EXT4-fs error (device sda1): ext4_readdir:198: inode #11: block 8485: comm find: bad entry in directory: rec_len is smaller than minimal - offset=0(0), inode=0, rec_len=2, name_len=0
Jan 10 05:09:45 kernel: EXT4-fs error (device sda1): ext4_readdir:198: inode #11: block 8485: comm find: bad entry in directory: rec_len is smaller than minimal - offset=0(0), inode=0, rec_len=2, name_len=0
Jan 10 05:09:45 kernel: EXT4-fs error (device sda1): ext4_readdir:198: inode #11: block 8485: comm find: bad entry in directory: rec_len is smaller than minimal - offset=0(0), inode=0, rec_len=2, name_len=0
Jan 10 05:09:45 kernel: EXT4-fs error (device sda1): ext4_readdir:198: inode #11: block 8485: comm find: bad entry in directory: rec_len is smaller than minimal - offset=0(0), inode=0, rec_len=2, name_len=0
Jan 10 05:09:45 kernel: EXT4-fs error (device sda1): ext4_readdir:198: inode #11: block 8485: comm find: bad entry in directory: rec_len is smaller than minimal - offset=0(0), inode=0, rec_len=2, name_len=0
Jan 10 05:09:45 kernel: EXT4-fs error (device sda1): ext4_readdir:198: inode #11: block 8485: comm find: bad entry in directory: rec_len is smaller than minimal - offset=0(0), inode=0, rec_len=2, name_len=0
Jan 10 05:09:45 kernel: EXT4-fs error (device sda1): ext4_readdir:198: inode #11: block 8485: comm find: bad entry in directory: rec_len is smaller than minimal - offset=0(0), inode=0, rec_len=2, name_len=0
Jan 10 05:09:45 kernel: EXT4-fs error (device sda1): ext4_readdir:198: inode #11: block 8485: comm find: bad entry in directory: rec_len is smaller than minimal - offset=0(0), inode=0, rec_len=2, name_len=0
Jan 10 05:09:45 kernel: EXT4-fs error (device sda1): ext4_readdir:198: inode #11: block 8485: comm find: bad entry in directory: rec_len is smaller than minimal - offset=0(0), inode=0, rec_len=2, name_len=0
Jan 10 05:09:45 kernel: EXT4-fs error (device sda1): ext4_readdir:198: inode #11: block 8485: comm find: bad entry in directory: rec_len is smaller than minimal - offset=0(0), inode=0, rec_len=2, name_len=0

Anything to be worried about? Thank you!

 

[maxbraketorque]

Hello all,

since the update to 386.9 I see in my syslog following entries. It repeats every day at 5:09, 11:09, 17:09 and 23:09 and every time it is about 295 rows.

Jan 10 05:09:45 kernel: EXT4-fs error (device sda1): ext4_readdir:198: inode #11: block 8485: comm find: bad entry in directory: rec_len is smaller than minimal - offset=0(0), inode=0, rec_len=2, name_len=0
Jan 10 05:09:45 kernel: EXT4-fs error (device sda1): ext4_readdir:198: inode #11: block 8485: comm find: bad entry in directory: rec_len is smaller than minimal - offset=0(0), inode=0, rec_len=2, name_len=0
Jan 10 05:09:45 kernel: EXT4-fs error (device sda1): ext4_readdir:198: inode #11: block 8485: comm find: bad entry in directory: rec_len is smaller than minimal - offset=0(0), inode=0, rec_len=2, name_len=0
Jan 10 05:09:45 kernel: EXT4-fs error (device sda1): ext4_readdir:198: inode #11: block 8485: comm find: bad entry in directory: rec_len is smaller than minimal - offset=0(0), inode=0, rec_len=2, name_len=0
Jan 10 05:09:45 kernel: EXT4-fs error (device sda1): ext4_readdir:198: inode #11: block 8485: comm find: bad entry in directory: rec_len is smaller than minimal - offset=0(0), inode=0, rec_len=2, name_len=0
Jan 10 05:09:45 kernel: EXT4-fs error (device sda1): ext4_readdir:198: inode #11: block 8485: comm find: bad entry in directory: rec_len is smaller than minimal - offset=0(0), inode=0, rec_len=2, name_len=0
Jan 10 05:09:45 kernel: EXT4-fs error (device sda1): ext4_readdir:198: inode #11: block 8485: comm find: bad entry in directory: rec_len is smaller than minimal - offset=0(0), inode=0, rec_len=2, name_len=0
Jan 10 05:09:45 kernel: EXT4-fs error (device sda1): ext4_readdir:198: inode #11: block 8485: comm find: bad entry in directory: rec_len is smaller than minimal - offset=0(0), inode=0, rec_len=2, name_len=0
Jan 10 05:09:45 kernel: EXT4-fs error (device sda1): ext4_readdir:198: inode #11: block 8485: comm find: bad entry in directory: rec_len is smaller than minimal - offset=0(0), inode=0, rec_len=2, name_len=0
Jan 10 05:09:45 kernel: EXT4-fs error (device sda1): ext4_readdir:198: inode #11: block 8485: comm find: bad entry in directory: rec_len is smaller than minimal - offset=0(0), inode=0, rec_len=2, name_len=0
Jan 10 05:09:45 kernel: EXT4-fs error (device sda1): ext4_readdir:198: inode #11: block 8485: comm find: bad entry in directory: rec_len is smaller than minimal - offset=0(0), inode=0, rec_len=2, name_len=0
Jan 10 05:09:45 kernel: EXT4-fs error (device sda1): ext4_readdir:198: inode #11: block 8485: comm find: bad entry in directory: rec_len is smaller than minimal - offset=0(0), inode=0, rec_len=2, name_len=0
Jan 10 05:09:45 kernel: EXT4-fs error (device sda1): ext4_readdir:198: inode #11: block 8485: comm find: bad entry in directory: rec_len is smaller than minimal - offset=0(0), inode=0, rec_len=2, name_len=0
Jan 10 05:09:45 kernel: EXT4-fs error (device sda1): ext4_readdir:198: inode #11: block 8485: comm find: bad entry in directory: rec_len is smaller than minimal - offset=0(0), inode=0, rec_len=2, name_len=0
Jan 10 05:09:45 kernel: EXT4-fs error (device sda1): ext4_readdir:198: inode #11: block 8485: comm find: bad entry in directory: rec_len is smaller than minimal - offset=0(0), inode=0, rec_len=2, name_len=0
Jan 10 05:09:45 kernel: EXT4-fs error (device sda1): ext4_readdir:198: inode #11: block 8485: comm find: bad entry in directory: rec_len is smaller than minimal - offset=0(0), inode=0, rec_len=2, name_len=0
Jan 10 05:09:45 kernel: EXT4-fs error (device sda1): ext4_readdir:198: inode #11: block 8485: comm find: bad entry in directory: rec_len is smaller than minimal - offset=0(0), inode=0, rec_len=2, name_len=0

Anything to be worried about? Thank you!

A drive attached to your router has an error. Needs to be repaired. There is an option in the router GUI to run a disk check, but I've never tried it. If you are handy with the command line, you could run the amtm disk check routine which is which a built-in add-on with Merlin FW.

 

[PhilG1300]

Using RT-AC86U
Does this new firmware support WireGuard on the VPN section of the GUI?
Using external WireGuard VPN server at the moment.
Have tried Merlin firmware in the past but currently using stock ASUS.
Thanks.

 

[Ripshod]

Using RT-AC86U
Does this new firmware support WireGuard on the VPN section of the GUI?
Using external WireGuard VPN server at the moment.
Have tried Merlin firmware in the past but currently using stock ASUS.
Thanks.

There's no specific mention of it in the changelog link in the first post.

 

[bennor]

Using RT-AC86U
Does this new firmware support WireGuard on the VPN section of the GUI?

See the Change Log (mentioned at the start of this thread) or here: https://www.asuswrt-merlin.net/changelog. It answers your question. The answer is apparently no. Currently it is the 388.x firmware for the AX series of routers has the Wireguard support built in and a new Wireguard client/server webui VPN section. This 386.9 firmware does not have Wireguard built in per the change log.

388.1 (3-Dec-2022)
- NOTE: This release is only available for AX models.
AC models will remain on the 386_xx release branch.
....
- NEW: (Asus 388) WireGuard client and server. The server uses
the new 388 VPN server webui. Implemented a webui for
clients, based on the early development UI from Asus.

WG client routing is handled by VPN Director - you must
configure redirection rules through it, same as on stock
firmware which requires configuring rules through
VPN Fusion.

DNS handling will be identical to OpenVPN's Exclusive DNS
mode, forcing clients to use the DNS provided by it
(if any is provided).

Note that enabling WireGuard will disable hardware
NAT acceleration due to compatibility reasons.

 

[RMerlin]

Does this new firmware support WireGuard on the VPN section of the GUI?

WireGuard is only available on the 388 series of firmwares.

 

[jerry6]

working perfectly on my rt 5300 one day i'll have to set up my ax1100e see if it makes a big difference on my ax6 clients ..
Thanks for 10 years of trouble free FW

 

[akb]

Hi All, I am having an issue with upgrading my AC88u with this firmware. So i have it as an Aimesh node from my AX86u and when I try to upgrade it from the UI as a Aimesh upgrade, it seems like it works fine uploading the upgrade and rebooting the node, but it never changes from the version it is currently at. It has 386.7_2. I rebooted and attempted the upgrade a few times.

Is there a way to upgrade the AiMesh node directly? I can ssh into and and wget the upgrade file, is there a command to upgrade the node?

Thanks

 

[heywire]

Is there a way to upgrade the AiMesh node directly?

Well, there is the laboursome but working step-by-step fallback: Do a WPS reset and set it up as a normal router, run upgrade, do a WPS reset and set ut up as an Aimesh node again.

That being said, I prefer running stock firmware on my Aimesh nodes - i reserve Merlin for the main router, as it offers no advantage on an Aimesh node. You also have the advantage of being able to do firmware by semi-automatically in the GUI (simply click "update" when there is a new update detected). Stock firmware is also newer.

 

[heywire]

I have two suggestions for vastly improving these feedback-theads, if these could be made mandatory in the first-post:
- provide a full description of your network - including Aimesh nodes with router model, and whether they are wired or wireless. This is what signature fields are for.
- Don't post silly, useless messages like "dirty upgrade two minutes ago, working so far". You have to run it for at least a couple hours and test different clients in order to see if there are any issues. Describe what you actually have tested.

 

[CriticJay]

Comparing 386.9 to 386.7_2 I feel like I've noticed a difference in dnsmasq behaviour:

In 386.7_2 I would frequently notice the dnsmasq log showing IPv6 addresses in response to AAAA requests
In 386.9 I think I'm seeing "NODATA" or "NODATA-ipv6" in response to AAAA requests

On my network, IPv6 was disabled under both .7_2 and .9

This is not a problem per se (I have not noticed any negative impacts due to this) but more a difference in behaviour and just reporting it for the record. Hopefully I'm not misinterpreting dnsmasq logs. (I assume this change in behaviour is due to the updated dnsmasq in 386.9)

 

[ColinTaylor]

In 386.7_2 I would frequently notice the dnsmasq log showing IPv6 addresses in response to AAAA requests
In 386.9 I think I'm seeing "NODATA" or "NODATA-ipv6" in response to AAAA requests

Do you have some example domains that return "NODATA" or "NODATA-ipv6" that we can test?

 

[Yota]

The code for displaying MAC address manufacturer information appears to have been updated from the new codebase.

Previously these MAC addresses couldn't be shown because its a new company, but now it's correctly stated that it's an Android 11 device, the company still doesn't show up because the router is local and doesn't have access to the online OUI database, and the local OUI database is not updated.



Another noticeable change is a friendlier popup when confirming to hide the SSID.


thanks for this version

 

[alchemy]

386.9 running great for 2.5 days on RT-AC86U!
Previously had like 121 days up time on 386.7_2.