Release Asuswrt-Merlin 386.5 is now available

[rd1600]

Since updating my AC86U to 386.5 from 386.4, the router does not want to run on control channel 1 on 2.4g band. Even though its set to run on channel 1, it keeps running on another random channel. I have tried rebooting, disabling and enabling the 2.4 radio. Changing to other channels and back to 1 with no luck. The weird part is that it follows other channel settings like it runs on 6 when set to 6 or runs on 9 when set to 9 but when its set to 1 (what it used to run on), it decides to run on a totally different channel. I would appreciate any suggestions.

 

[L&LD]

Reset and do not use a saved backup config file to connect to your ISP and also secure the router.

 

[RMerlin]

I uploaded 386.5_1 test builds:

OneDrive

www.asuswrt-merlin.net

These contain updates to openssl and openvpn, a few bug fixes, and an update to AiCloud (both security and bug fixes).

 

[Ed_Lei]

@RMerlin How to put two dns ip to one device in Dnsfilter?

 

[Zastoff]

Smooth upgrade from 386.5 to 386.5_1-g8858f16344 on RT-AX88u.
Looking good
Thanks RMerlin

 

[RMerlin]

@RMerlin How to put two dns ip to one device in Dnsfilter?

You can't, because of the way dnsfilter works (with firewall rules that redirects you to a specific DNS - only the first matched rule would get you redirected, and the firewall has no way of knowing if the target server works or not).

 

[kernol]

Upgraded RT-AX86U x 2; RT-AC86U and RT-AC5300 to 386.5_1-g8858f16344 - all working wonderfully well - including OpenVPN. Thanks for your continued efforts.

 

[itpp20]

Dirty flash 384.17 -> RT-AC68U_386.5_1-g8858f16344
No problems so far.

 

[alchemy]

Updated AC86U to 386.5_1 from 386.5 and all seems well.
Thanks @RMerlin!

 

[shabbs]

Updated my APs to the new Test Build 386.5_1-g8858f16344. No issues so far. All devices reconnected.

 

[iJorgen]

Smooth upgrade here too from 386.5 to 386.5_1-g8858f16344

 

[SheikhSheikha]

Dirty flash from 386.5 to 386.5_1 and moving smooth on

 

[roundaway]

Dirty flash from 386.5 to 386.5_1 without incident. Thank you.

 

[capncybo]

Re: 386.5 to 386.5_1-g8858f16344
Upgraded RT-AX86U ... Fine, RT-AC68U ... Fine, but 2nd RT-AC68U ... (Mesh Node) cannot flash, Upgrade pop-up window is blank (tried doing some browser refreshes) no luck, yet

EDIT: Just Tried Again ... & it the node flashed normally. Perhaps my primary RT-AC68U just needed some more time to finish up.

 

[calex]

Dirty upgraded my RT-AC68U from 386.3_2 to 386.5 without any impacting issues so far.

Noticed the following on router logs, but nothing seems to be affected at the moment:

Mar 22 17:07:55 kernel: dcd/3255: potentially unexpected fatal signal 11.
Mar 22 17:07:55 kernel: Pid: 3255, comm:                  dcd
Mar 22 17:07:55 kernel: CPU: 0    Tainted: P             (2.6.36.4brcmarm #1)
Mar 22 17:07:55 kernel: PC is at 0x40151444
Mar 22 17:07:55 kernel: LR is at 0x1c070
Mar 22 17:07:55 kernel: pc : [<40151444>]    lr : [<0001c070>]    psr: 20000010
Mar 22 17:07:55 kernel: sp : bec019a0  ip : 000a1b00  fp : bec01b04
Mar 22 17:07:55 kernel: r10: 00085f8c  r9 : 0000dafc  r8 : 00000068
Mar 22 17:07:55 kernel: r7 : 00085f8c  r6 : 00000000  r5 : bec01c54  r4 : 00000000
Mar 22 17:07:55 kernel: r3 : 00000000  r2 : 00000000  r1 : 00085f8c  r0 : 00000000
Mar 22 17:07:55 kernel: Flags: nzCv  IRQs on  FIQs on  Mode USER_32  ISA ARM  Segment user
Mar 22 17:07:55 kernel: Control: 10c53c7d  Table: 9993804a  DAC: 00000015

 

[Clark Griswald]

Remembered to safely remove usb, then dirty upgraded both Main/AP.
All devices connected appropriately and no LAN/WAN issues detected.

 

[capncybo]

Some Good News... Re: upgrading 386.5 to 386.5_1-g8858f16344 :
With my OpenVPN I can again connect via "different" usernames under the Common Name: client on my RT-AX86U .
Previously on 386.5 It seemed I could only connect via the "root" username & default admin password.
So, Thx ;-)

 

[octopus]

Dirty upgraded my RT-AC68U from 386.3_2 to 386.5 without any impacting issues so far.

Noticed the following on router logs, but nothing seems to be affected at the moment:

Mar 22 17:07:55 kernel: dcd/3255: potentially unexpected fatal signal 11.
Mar 22 17:07:55 kernel: Pid: 3255, comm:                  dcd
Mar 22 17:07:55 kernel: CPU: 0    Tainted: P             (2.6.36.4brcmarm #1)
Mar 22 17:07:55 kernel: PC is at 0x40151444
Mar 22 17:07:55 kernel: LR is at 0x1c070
Mar 22 17:07:55 kernel: pc : [<40151444>]    lr : [<0001c070>]    psr: 20000010
Mar 22 17:07:55 kernel: sp : bec019a0  ip : 000a1b00  fp : bec01b04
Mar 22 17:07:55 kernel: r10: 00085f8c  r9 : 0000dafc  r8 : 00000068
Mar 22 17:07:55 kernel: r7 : 00085f8c  r6 : 00000000  r5 : bec01c54  r4 : 00000000
Mar 22 17:07:55 kernel: r3 : 00000000  r2 : 00000000  r1 : 00085f8c  r0 : 00000000
Mar 22 17:07:55 kernel: Flags: nzCv  IRQs on  FIQs on  Mode USER_32  ISA ARM  Segment user
Mar 22 17:07:55 kernel: Control: 10c53c7d  Table: 9993804a  DAC: 00000015

You are not alone.......

Mar 21 23:35:31 kernel: potentially unexpected fatal signal 11.
Mar 21 23:35:31 kernel: CPU: 3 PID: 30281 Comm: sh Tainted: P O 4.1.52 #2
Mar 21 23:35:31 kernel: Hardware name: Broadcom-v8A (DT)
Mar 21 23:35:31 kernel: task: ffffffc02dddeb80 ti: ffffffc02a0e8000 task.ti: ffffffc02a0e8000
Mar 21 23:35:31 kernel: PC is at 0xf7249f70
Mar 21 23:35:31 kernel: LR is at 0xf724cf78
Mar 21 23:35:31 kernel: pc : [<00000000f7249f70>] lr : [<00000000f724cf78>] pstate: 00000010
Mar 21 23:35:31 kernel: sp : 00000000ff756020
Mar 21 23:35:31 kernel: x12: 00000000f7319010
Mar 21 23:35:31 kernel: x11: 00000000ff756354 x10: 0000000000000001
Mar 21 23:35:31 kernel: x9 : 0000000000000001 x8 : 0000000000000000
Mar 21 23:35:31 kernel: x7 : 000000000000007f x6 : 00000000f74754d0
Mar 21 23:35:31 kernel: x5 : 0000000000000400 x4 : 00000000f73197f4
Mar 21 23:35:31 kernel: x3 : 000000000000040b x2 : 00000000001be008
Mar 21 23:35:31 kernel: x1 : 0000000000000400 x0 : 00000000f73197f4
Mar 21 23:35:39 kernel: potentially unexpected fatal signal 11.

Mar 21 23:35:39 kernel: CPU: 0 PID: 31165 Comm: sh Tainted: P O 4.1.52 #2
Mar 21 23:35:39 kernel: Hardware name: Broadcom-v8A (DT)
Mar 21 23:35:39 kernel: task: ffffffc02cb3a040 ti: ffffffc02a0e8000 task.ti: ffffffc02a0e8000
Mar 21 23:35:39 kernel: PC is at 0x40500
Mar 21 23:35:39 kernel: LR is at 0x406e8
Mar 21 23:35:39 kernel: pc : [<0000000000040500>] lr : [<00000000000406e8>] pstate: 80080010
Mar 21 23:35:39 kernel: sp : 00000000ff67ef20
Mar 21 23:35:39 kernel: x12: 00000000ff67f178
Mar 21 23:35:39 kernel: x11: 0000000000000001 x10: 00000000ffffffff
Mar 21 23:35:39 kernel: x9 : 000000000032eefc x8 : 0000000000000000
Mar 21 23:35:39 kernel: x7 : 0000000000320b0c x6 : 0000000000000000
Mar 21 23:35:39 kernel: x5 : 000000000031f540 x4 : 0000000000000002
Mar 21 23:35:39 kernel: x3 : 0000000000072af4 x2 : 000000000037b0d6
Mar 21 23:35:39 kernel: x1 : 0000000000000000 x0 : 0000000000320c34

 

[ColDen]

Unmounted first my USB devices (as usual) then dirty upgraded from 386.5 to 386.5_1-g8858f16344. So far so good.

Thanks, Éric

 

[GaselK]

Trying to flash 386.5_1 on my AX68U but i keep getting the
"Firmware upgrade unsuccessful. This may result from incorrect image or error transmission. Please check the version of firmware and try again." message.
Clear browser cache, tried Chrome and Edge no luck.
Downloaded twice, sha256sum confirmed.
I am on 386.5