Release Asuswrt-Merlin 386.5 is now available

[Kitsap]

Use 386.4 when flashing over the CFE mini webui. This is an unfortunate limitation of Asus's new combined firmware image for that model, the new combined image for the RT-AC68U cannot be flashed in recovery mode.

Is this limitation expected to be permanent along with the combined image?

 

[erkme73]

BINGO! Running on 385_6 now. My problem had to do with a auto-reversion due to some "partition" oversights. TY!

 

[KOSU]

Configuration : RT-AC68U
I upgraded from 386.3_2 to 386.5

I have a VPN Server - OpenVPN serwer 1 configured. It is working fine but till the router restart. When the router needs to be restarted, using Reboot Scheduler or after a power failure, an OpenVPN won't startup.

It hangs on the step: Export OpenVPN configuration file.

It saying to wait when the file will be ready, but it never is. The way to run OpenVPN again is to turn it OFF and again ON manually.

no issue on 386.3_2.

Do I need to do some adjustments onw my router, or I need to wait for the next FW release ?

Any hints about the above issue ?

 

[DJones]

Any hints about the above issue ?

Did you do a clean install when you updated? Maybe try a factory reset to clear nvram then manually put the settings back into your router. Might help? Someone else might have another approach that isn’t gonna nuke your settings.

 

[KOSU]

Did you do a clean install when you updated? Maybe try a factory reset to clear nvram then manually put the settings back into your router. Might help? Someone else might have another approach that isn’t gonna nuke your settings.

Putting back all the settings is not an issue, I can do it again, but ..

Any hints how to put back same DDNS domain from asuscomm.com to this router after factory reset ?
what are the steps before the reset to have this domain back on the same device ?

 

[zd59]

From memory:

• 386.3: stable for 150+ days
• 386.3_2: skipped this one, can't recall why
• 386.4 caused various issues including guest 1 not propagating to node properly, wifi instability (both 5GHz and 2.4GHz), and general router instability. Symptoms improved (but did not disappear) after I moved my node to stock.
• 386.5_alpha1: skipped as not available for AC86U
• 386.5_alpha2: problems vanished: wifi stable, guest 1 propagating properly to node, etc.
• 386.5_beta: skipped as not too different from alpha2 and was wanting to test alpha2 stability over time
• 386.5 release: all good so far as reported above.

Thank you.
This is excellent news.
Will upgrade over next weekend.

 

[dethknite]

Upgrade was good. All supporting extras are working fine, however, I did note that my tcp connections to my additional AP have went from < 10ms avg to around 80ms avg after the upgrade. It is plugged in directly to the main router (backhaul) so shouldn't be anything other than noisy chatter on the network. But I scoured all the traffic and even when there was only ~500k of traffic going on.. it still was slow on responses. (Default tcp pings go to port 80 webui, I have tried port 22 as well with the same results). Everything is working okay.. just that the AP connection is slow... and I thought I would share in case it is helpful.

* Notes: Rebooted both devices multiple times. Rebooted other devices as well. No QOS.

(the graph upper is 100ms in this display, as anything higher is inconsequential in network anyways)

MainRtr: AC5300 (386.5 - Router+AiMesh)
- Skynet, Diversion, Pixelserv, YazDHCP, DNScrypt proxy installer.
- Backhaul mode
AP: AC5300 (386.5 - AiMesh Node)

 

[dethknite]

Upgrade was good. All supporting extras are working fine, however, I did note that my tcp connections to my additional AP have went from < 10ms avg to around 80ms avg after the upgrade. It is plugged in directly to the main router (backhaul) so shouldn't be anything other than noisy chatter on the network. But I scoured all the traffic and even when there was only ~500k of traffic going on.. it still was slow on responses. (Default tcp pings go to port 80 webui, I have tried port 22 as well with the same results). Everything is working okay.. just that the AP connection is slow... and I thought I would share in case it is helpful.

* Notes: Rebooted both devices multiple times. Rebooted other devices as well. No QOS.

View attachment 40020
(the graph upper is 100ms in this display, as anything higher is inconsequential in network anyways)

MainRtr: AC5300 (386.5 - Router+AiMesh)
- Skynet, Diversion, Pixelserv, YazDHCP, DNScrypt proxy installer.
- Backhaul mode
AP: AC5300 (386.5 - AiMesh Node)

** Fixed it! Was a broadcast loop on the AP with Home Security.

 

[Natty]

RT-AC66U_B1 succesfully updated from 386.4 to 386.5 manually installed over 386.4 without resetting any settings.

The update went smoothly but a CRC error in syslog caught my eye on the first reboot after the update:

May  5 06:05:04 kernel: Creating 2 MTD partitions on "brcmnand":
May  5 06:05:04 kernel: 0x000004000000-0x000007ec0000 : "brcmnand"
May  5 06:05:04 kernel: 0x000007ec0000-0x000008000000 : "asus"
May  5 06:05:04 kernel: VFS: Mounted root (squashfs filesystem) readonly on device 31:3.
May  5 06:05:04 kernel: Empty flash at 0x01fb5598 ends at 0x01fb5800
May  5 06:05:04 kernel: JFFS2 notice: (46) check_node_data: wrong data CRC in data node at 0x01fb4f1c: read 0xf4092c1b, calculated 0xf84ce7b1.
May  5 06:05:04 kernel: emf: module license 'Proprietary' taints kernel.

Subsequent reboots show no CRC error:

May  5 06:05:04 kernel: Creating 2 MTD partitions on "brcmnand":
May  5 06:05:04 kernel: 0x000004000000-0x000007ec0000 : "brcmnand"
May  5 06:05:04 kernel: 0x000007ec0000-0x000008000000 : "asus"
May  5 06:05:04 kernel: VFS: Mounted root (squashfs filesystem) readonly on device 31:3.
May  5 06:05:04 kernel: emf: module license 'Proprietary' taints kernel.

Probably nothing to worry about then. Thanks @RMerlin .

@yenic did you find the root cause of your RT-AC66U B1 issue, and could it be fixed?

 

[RMerlin]

Is this limitation expected to be permanent along with the combined image?

Yes, unless Asus upgrade the CFE at some point to handle the new dual image, which is currently unlikely.

 

[barutchiev]

RT-AC66U_B1 successfully updated from 386.4 to 386.5. Many versions passed without resetting and I decided to do a nuclear reset.Manually entered settings. I formatted the USB and installed all the add-ons clean. No problems installing everything.
Thank you @RMerlin

 

[Morris]

Dirty upgrade from 386.4 to 386.5. .4 ran perfectly for me and so far no issues with .5

Thank you @RMerlin

Morris

 

[heysoundude]

Smooth upgrade for both (AC86/AC88).
Survived online classes (gaming) from teens and all the other network abuses The Family seems to accomplish daily.

Still experiencing the same Very Senior Member issues:
-Downloading wrong fw, due to small print or wishful thinking.
-failing to safely remove usb before fw upgrade.
although, I haven't experienced any negative issues from not removing usb.

I, too, forgot to unmount my USB before flashing, but I've learned that it just takes a 2nd and sometimes 3rd reboot for the router to fix itself when I miss that checklist item.
...and that's what happened this time, too. Again. as expected, thankfully.
All good - this version is probably the best one yet.

 

[banger]

Mar  7 19:13:30 kernel: Pid: 669, comm:              roamast
Mar  7 19:13:30 kernel: CPU: 1    Tainted: P             (2.6.36.4brcmarm #1)
Mar  7 19:13:30 kernel: PC is at 0x40604340
Mar  7 19:13:30 kernel: LR is at 0x400fb214
Mar  7 19:13:30 kernel: pc : [<40604340>]    lr : [<400fb214>]    psr: 60000010
Mar  7 19:13:30 kernel: sp : be1ff9a8  ip : 40105e5c  fp : 00197898
Mar  7 19:13:30 kernel: r10: 000000d8  r9 : 001899d8  r8 : 00193eb8
Mar  7 19:13:30 kernel: r7 : 00000025  r6 : 00000006  r5 : 0000029d  r4 : 40106038
Mar  7 19:13:30 kernel: r3 : 40106038  r2 : 00000803  r1 : 00000006  r0 : 00000000
Mar  7 19:13:30 kernel: Flags: nZCv  IRQs on  FIQs on  Mode USER_32  ISA ARM  Segment user
Mar  7 19:13:30 kernel: Control: 10c53c7d  Table: 9cca004a  DAC: 00000015
Mar  7 19:13:30 kernel: roamast/671: potentially unexpected fatal signal 6.
Mar  7 19:13:30 kernel: Pid: 671, comm:              roamast
Mar  7 19:13:30 kernel: CPU: 1    Tainted: P             (2.6.36.4brcmarm #1)
Mar  7 19:13:30 kernel: PC is at 0x40605498
Mar  7 19:13:30 kernel: LR is at 0x400fb96c
Mar  7 19:13:30 kernel: pc : [<40605498>]    lr : [<400fb96c>]    psr: 80000010
Mar  7 19:13:30 kernel: sp : bdffe8c8  ip : 40105f50  fp : 00000c04
Mar  7 19:13:30 kernel: r10: 00000001  r9 : 001899d8  r8 : 4065c27c
Mar  7 19:13:30 kernel: r7 : 0000009e  r6 : 001e8481  r5 : bdffe8d8  r4 : 00000000
Mar  7 19:13:30 kernel: r3 : 00000001  r2 : 00000230  r1 : bdfffea0  r0 : 00000000
Mar  7 19:13:30 kernel: Flags: Nzcv  IRQs on  FIQs on  Mode USER_32  ISA ARM  Segment user
Mar  7 19:13:30 kernel: Control: 10c53c7d  Table: 9cca004a  DAC: 00000015
Mar  7 19:13:30 kernel: roamast/288: potentially unexpected fatal signal 6.
Mar  7 19:13:30 kernel: Pid: 288, comm:              roamast
Mar  7 19:13:30 kernel: CPU: 0    Tainted: P             (2.6.36.4brcmarm #1)
Mar  7 19:13:30 kernel: PC is at 0x40604890
Mar  7 19:13:30 kernel: LR is at 0x400fbee4
Mar  7 19:13:30 kernel: pc : [<40604890>]    lr : [<400fbee4>]    psr: 60000010
Mar  7 19:13:30 kernel: sp : bea72730  ip : 40105de8  fp : 00000000
Mar  7 19:13:30 kernel: r10: 00000000  r9 : 001899d8  r8 : 4065c27c
Mar  7 19:13:30 kernel: r7 : 000000a2  r6 : 001e8481  r5 : bea72758  r4 : 00000000
Mar  7 19:13:30 kernel: r3 : 00000001  r2 : 00000258  r1 : 00000000  r0 : 00000000
Mar  7 19:13:30 kernel: Flags: nZCv  IRQs on  FIQs on  Mode USER_32  ISA ARM  Segment user
Mar  7 19:13:30 kernel: Control: 10c53c7d  Table: 9cca004a  DAC: 00000015
Mar  7 19:13:30 kernel: roamast/662: potentially unexpected fatal signal 6.
Mar  7 19:13:30 kernel: Pid: 662, comm:              roamast
Mar  7 19:13:30 kernel: CPU: 0    Tainted: P             (2.6.36.4brcmarm #1)
Mar  7 19:13:30 kernel: PC is at 0x40604954
Mar  7 19:13:30 kernel: LR is at 0x400fbf2c
Mar  7 19:13:30 kernel: pc : [<40604954>]    lr : [<400fbf2c>]    psr: 60000010
Mar  7 19:13:30 kernel: sp : be3ff9a8  ip : 40105ebc  fp : 00000000
Mar  7 19:13:30 kernel: r10: 000000d8  r9 : 001899d8  r8 : 00193eb8
Mar  7 19:13:30 kernel: r7 : 00000005  r6 : 00194004  r5 : 00145d25  r4 : 4018af49
Mar  7 19:13:30 kernel: r3 : be3ff9e4  r2 : 00000000  r1 : 00000801  r0 : 00000007
Mar  7 19:13:30 kernel: Flags: nZCv  IRQs on  FIQs on  Mode USER_32  ISA ARM  Segment user
Mar  7 19:13:30 kernel: Control: 10c53c7d  Table: 9cca004a  DAC: 00000015
Mar  7 19:13:30 haveged: haveged: Stopping due to signal 15

Seeing the above now and again on AC68U. Anything to be worried about? Also dont Factory reset the system or you cant add the node. Have to upload stock firmware to node to get mesh back up and working.

 

[skeal]

Mar  7 19:13:30 kernel: Pid: 669, comm:              roamast
Mar  7 19:13:30 kernel: CPU: 1    Tainted: P             (2.6.36.4brcmarm #1)
Mar  7 19:13:30 kernel: PC is at 0x40604340
Mar  7 19:13:30 kernel: LR is at 0x400fb214
Mar  7 19:13:30 kernel: pc : [<40604340>]    lr : [<400fb214>]    psr: 60000010
Mar  7 19:13:30 kernel: sp : be1ff9a8  ip : 40105e5c  fp : 00197898
Mar  7 19:13:30 kernel: r10: 000000d8  r9 : 001899d8  r8 : 00193eb8
Mar  7 19:13:30 kernel: r7 : 00000025  r6 : 00000006  r5 : 0000029d  r4 : 40106038
Mar  7 19:13:30 kernel: r3 : 40106038  r2 : 00000803  r1 : 00000006  r0 : 00000000
Mar  7 19:13:30 kernel: Flags: nZCv  IRQs on  FIQs on  Mode USER_32  ISA ARM  Segment user
Mar  7 19:13:30 kernel: Control: 10c53c7d  Table: 9cca004a  DAC: 00000015
Mar  7 19:13:30 kernel: roamast/671: potentially unexpected fatal signal 6.
Mar  7 19:13:30 kernel: Pid: 671, comm:              roamast
Mar  7 19:13:30 kernel: CPU: 1    Tainted: P             (2.6.36.4brcmarm #1)
Mar  7 19:13:30 kernel: PC is at 0x40605498
Mar  7 19:13:30 kernel: LR is at 0x400fb96c
Mar  7 19:13:30 kernel: pc : [<40605498>]    lr : [<400fb96c>]    psr: 80000010
Mar  7 19:13:30 kernel: sp : bdffe8c8  ip : 40105f50  fp : 00000c04
Mar  7 19:13:30 kernel: r10: 00000001  r9 : 001899d8  r8 : 4065c27c
Mar  7 19:13:30 kernel: r7 : 0000009e  r6 : 001e8481  r5 : bdffe8d8  r4 : 00000000
Mar  7 19:13:30 kernel: r3 : 00000001  r2 : 00000230  r1 : bdfffea0  r0 : 00000000
Mar  7 19:13:30 kernel: Flags: Nzcv  IRQs on  FIQs on  Mode USER_32  ISA ARM  Segment user
Mar  7 19:13:30 kernel: Control: 10c53c7d  Table: 9cca004a  DAC: 00000015
Mar  7 19:13:30 kernel: roamast/288: potentially unexpected fatal signal 6.
Mar  7 19:13:30 kernel: Pid: 288, comm:              roamast
Mar  7 19:13:30 kernel: CPU: 0    Tainted: P             (2.6.36.4brcmarm #1)
Mar  7 19:13:30 kernel: PC is at 0x40604890
Mar  7 19:13:30 kernel: LR is at 0x400fbee4
Mar  7 19:13:30 kernel: pc : [<40604890>]    lr : [<400fbee4>]    psr: 60000010
Mar  7 19:13:30 kernel: sp : bea72730  ip : 40105de8  fp : 00000000
Mar  7 19:13:30 kernel: r10: 00000000  r9 : 001899d8  r8 : 4065c27c
Mar  7 19:13:30 kernel: r7 : 000000a2  r6 : 001e8481  r5 : bea72758  r4 : 00000000
Mar  7 19:13:30 kernel: r3 : 00000001  r2 : 00000258  r1 : 00000000  r0 : 00000000
Mar  7 19:13:30 kernel: Flags: nZCv  IRQs on  FIQs on  Mode USER_32  ISA ARM  Segment user
Mar  7 19:13:30 kernel: Control: 10c53c7d  Table: 9cca004a  DAC: 00000015
Mar  7 19:13:30 kernel: roamast/662: potentially unexpected fatal signal 6.
Mar  7 19:13:30 kernel: Pid: 662, comm:              roamast
Mar  7 19:13:30 kernel: CPU: 0    Tainted: P             (2.6.36.4brcmarm #1)
Mar  7 19:13:30 kernel: PC is at 0x40604954
Mar  7 19:13:30 kernel: LR is at 0x400fbf2c
Mar  7 19:13:30 kernel: pc : [<40604954>]    lr : [<400fbf2c>]    psr: 60000010
Mar  7 19:13:30 kernel: sp : be3ff9a8  ip : 40105ebc  fp : 00000000
Mar  7 19:13:30 kernel: r10: 000000d8  r9 : 001899d8  r8 : 00193eb8
Mar  7 19:13:30 kernel: r7 : 00000005  r6 : 00194004  r5 : 00145d25  r4 : 4018af49
Mar  7 19:13:30 kernel: r3 : be3ff9e4  r2 : 00000000  r1 : 00000801  r0 : 00000007
Mar  7 19:13:30 kernel: Flags: nZCv  IRQs on  FIQs on  Mode USER_32  ISA ARM  Segment user
Mar  7 19:13:30 kernel: Control: 10c53c7d  Table: 9cca004a  DAC: 00000015
Mar  7 19:13:30 haveged: haveged: Stopping due to signal 15

Seeing the above now and again on AC68U. Anything to be worried about? Also dont Factory reset the system or you cant add the node. Have to upload stock firmware to node to get mesh back up and working.

If you use Pixelserv-tls with Diversion, disable it. There is a conflict between it and AIProtection.

 

[dave14305]

If you use Pixelserv-tls with Diversion, disable it. There is a conflict between it and AIProtection.

That’s only relevant for dcd crashes. This is roamast.

 

[RMerlin]

If you use Pixelserv-tls with Diversion, disable it. There is a conflict between it and AIProtection.

His crash is in the Roaming Assistant, not the TrendMicro DCD. Different issue.

Unfortunately roamast is closed source, so outside of my control.

 

[Dent]

Are there any fixes in the newly released official ASUS RT-AC86U Firmware version 3.0.0.4.386.46092 that are not in this new Merlin release?

 

[banger]

His crash is in the Roaming Assistant, not the TrendMicro DCD. Different issue.

Unfortunately roamast is closed source, so outside of my control.

I was going to suggest disabling Roaming Assistant as a fix but it is already disabled on both bands.

 

[L&LD]

@Dent compare changelogs to find out.