Release ASUS RT-AC88U Firmware version 3.0.0.4.386.43129

[CraigUK]

Hello

I noticed this update 3.0.0.4.386.43129 was available on my RT-AC88U last night -- recommended due to vulnerability fixes.

I allowed the router to upgrade and it went well until I realised there was no Internet connection. I rebooted several times and what's odd is the Internet light on the router is white, but there is no active connection. I guess this means nothing, but it does do it's thing from red to pink to white when you reconnect the WAN cable. The router portal shows the Internet as 'Disconnected' though.

Here's what's really odd though. I have Internet connection via 2 devices only, wireless 5GHz, my phone and a Roku box. Most of my devices are wired and they have no Internet connection due to this sodding firmware.

I then tried a router reset, which has not resolved the issue at all. I'm really disappointed in Asus over this. I ditched TPLink for this very issue and spent fairly decent money for what I hopped would be a sound investment -- it was until now.

Has anyone found a solution? I'm a bit reluctant to downgrade, as vulnerabilities were addressed in this update.

I believe this router supports an Open Source firmware release (I need research it again) and maybe I'll have better luck there.

Many thanks for reading.

Craig.

 

[Squall Leonhart]

I then tried a router reset, which has not resolved the issue at all. I'm really disappointed in Asus over this. I ditched TPLink for this very issue and spent fairly decent money for what I hopped would be a sound investment -- it was until now.

spontaneous hardware failure, nothing to do with the firmware.

 

[CraigUK]

Having spent a few hours on this today, I decided to install the latest version again but this time manually. It went through fine, but still no Internet.

I tried to install the previous two versions and to my amazement the router wouldn't accept them, with a pop up saying they're invalid.

So I installed the latest Asuswrt-Merlin version and now everything is back to normal, fully working again. Phew. Shoddy firmware no more!

 

[Squall Leonhart]

nothing wrong with the firmware, the issue is yours alone.

 

[FSTL]

I too had the same results after updating to 3.0.0.4.386_43129-g60defb2 from a 3.0.0.4.384 version on my RT-AC5300. After the update the router will not get a DHCP address on the WAN side, error "WAN Connection: ISP's DHCP did not function properly.". A rollback to previous 384 version restores functionality. I haven't tried a factory reset yet, or a manual upgrade.

 

[slimwallet]

I got 5 RT-AC88u in a mesh, 1 router and 4 nodes. After this update only 3 nodes will stay connected. I did factory restore on all of them and it didn't help. I rolled back to 3.0.0.4.386_41700 and it seems to be working fine again.

I think 43129 was using 2.4ghz as backhaul even if I set Backhaul Connection Priority to 5ghz. That might've caused the issue.

 

[FSTL]

I've done a lot more testing with my RT-AC5300 with 386_43129. Even when DHCP on the WAN side works (rarely), I still have trouble passing traffic via wired and wireless nodes. Seems to be DNS related. Same results with Merlin 386.2_6 & 386.2_4.

 

[FIN]

Spoiler: does anyone know what this means and how bad it is?

Jun 14 13:15:07 kernel: cfg_server/16175: potentially unexpected fatal signal 11.
Jun 14 13:15:07 kernel: Pid: 16175, comm: cfg_server
Jun 14 13:15:07 kernel: CPU: 0 Tainted: P (2.6.36.4brcmarm #1)
Jun 14 13:15:07 kernel: PC is at 0x2b049bdc
Jun 14 13:15:07 kernel: LR is at 0x4e6c
Jun 14 13:15:07 kernel: pc : [<2b049bdc>] lr : [<00004e6c>] psr: 80000010
Jun 14 13:15:07 kernel: sp : 7e1ff910 ip : 2b06a4b0 fp : 000009e0
Jun 14 13:15:07 kernel: r10: 000000b8 r9 : 2b06a180 r8 : 00000001
Jun 14 13:15:07 kernel: r7 : 2b06a1b4 r6 : 000883b8 r5 : 2b0644f8 r4 : 000000a8
Jun 14 13:15:07 kernel: r3 : 00000015 r2 : 2b06a1ac r1 : 00000000 r0 : 00004e6d
Jun 14 13:15:07 kernel: Flags: Nzcv IRQs on FIQs on Mode USER_32 ISA ARM Segment user
Jun 14 13:15:07 kernel: Control: 10c53c7d Table: 5920804a DAC: 00000015
Jun 14 13:15:07 kernel: cfg_server/16174: potentially unexpected fatal signal 11.
Jun 14 13:15:07 kernel: cfg_server/1250: potentially unexpected fatal signal 11.
Jun 14 13:15:07 kernel: Pid: 1250, comm: cfg_server
Jun 14 13:15:07 kernel: CPU: 0 Tainted: P (2.6.36.4brcmarm #1)
Jun 14 13:15:07 kernel: PC is at 0x2b00d890
Jun 14 13:15:07 kernel: LR is at 0x2abfeee4
Jun 14 13:15:07 kernel: pc : [<2b00d890>] lr : [<2abfeee4>] psr: 60000010
Jun 14 13:15:07 kernel: sp : 7e5ffd70 ip : 2ac08de8 fp : 00000064
Jun 14 13:15:07 kernel: r10: 00064ed3 r9 : 0000005a r8 : 0007865c
Jun 14 13:15:07 kernel: r7 : 000000a2 r6 : 60c6b8ac r5 : 7e5ffdb8 r4 : 7e5ffdb8
Jun 14 13:15:07 kernel: r3 : 00000000 r2 : 00000230 r1 : 7e5ffdb8 r0 : fffffdfc
Jun 14 13:15:07 kernel: Flags: nZCv IRQs on FIQs on Mode USER_32 ISA ARM Segment user
Jun 14 13:15:07 kernel: Control: 10c53c7d Table: 5920804a DAC: 00000015
Jun 14 13:15:07 kernel: cfg_server/940: potentially unexpected fatal signal 11.
Jun 14 13:15:07 kernel: Pid: 940, comm: cfg_server
Jun 14 13:15:07 kernel: CPU: 0 Tainted: P (2.6.36.4brcmarm #1)
Jun 14 13:15:07 kernel: PC is at 0x2b00e4cc
Jun 14 13:15:07 kernel: LR is at 0x5d57c
Jun 14 13:15:07 kernel: pc : [<2b00e4cc>] lr : [<0005d57c>] psr: 20000010
Jun 14 13:15:07 kernel: sp : 7ede9c30 ip : 00078328 fp : 00000000
Jun 14 13:15:07 kernel: r10: 00078b1c r9 : 0005fd80 r8 : 7ede9c48
Jun 14 13:15:07 kernel: r7 : 0000008e r6 : 00000001 r5 : 00000000 r4 : 00000000
Jun 14 13:15:07 kernel: r3 : 00000000 r2 : 00000000 r1 : 7ede9c48 r0 : fffffdfe
Jun 14 13:15:07 kernel: Flags: nzCv IRQs on FIQs on Mode USER_32 ISA ARM Segment user
Jun 14 13:15:07 kernel: Control: 10c53c7d Table: 5920804a DAC: 00000015
Jun 14 13:15:07 kernel: cfg_server/16176: potentially unexpected fatal signal 11.
Jun 14 13:15:07 kernel: Pid: 16176, comm: cfg_server
Jun 14 13:15:07 kernel: CPU: 1 Tainted: P (2.6.36.4brcmarm #1)
Jun 14 13:15:07 kernel: PC is at 0x2b00d890
Jun 14 13:15:07 kernel: LR is at 0x2abfeee4
Jun 14 13:15:07 kernel: pc : [<2b00d890>] lr : [<2abfeee4>] psr: 60000010
Jun 14 13:15:07 kernel: sp : 7dfff8c0 ip : 2ac08de8 fp : 00000001
Jun 14 13:15:07 kernel: r10: 00000000 r9 : 00088308 r8 : 2b06527c
Jun 14 13:15:07 kernel: r7 : 000000a2 r6 : 001e8481 r5 : 7dfff8e8 r4 : 00000000
Jun 14 13:15:07 kernel: r3 : 00000001 r2 : 00000230 r1 : 00000000 r0 : 00000000
Jun 14 13:15:07 kernel: Flags: nZCv IRQs on FIQs on Mode USER_32 ISA ARM Segment user
Jun 14 13:15:07 kernel: Control: 10c53c7d Table: 5920804a DAC: 00000015
Jun 14 13:15:07 kernel: Pid: 16174, comm: cfg_server
Jun 14 13:15:07 kernel: CPU: 1 Tainted: P (2.6.36.4brcmarm #1)
Jun 14 13:15:07 kernel: PC is at 0x2b00e498
Jun 14 13:15:07 kernel: LR is at 0x2abfe96c
Jun 14 13:15:07 kernel: pc : [<2b00e498>] lr : [<2abfe96c>] psr: 80000010
Jun 14 13:15:07 kernel: sp : 7e3ff8b8 ip : 2ac08f50 fp : 00c9b403
Jun 14 13:15:07 kernel: r10: 00000000 r9 : 2ac0d3dc r8 : 2b06527c
Jun 14 13:15:07 kernel: r7 : 0000009e r6 : 001e8481 r5 : 7e3ff8c8 r4 : 00000000
Jun 14 13:15:07 kernel: r3 : 00000001 r2 : 00000000 r1 : 7e3ff8c8 r0 : 00000000
Jun 14 13:15:07 kernel: Flags: Nzcv IRQs on FIQs on Mode USER_32 ISA ARM Segment user
Jun 14 13:15:07 kernel: Control: 10c53c7d Table: 5920804a DAC: 00000015
Jun 14 13:15:15 rc_service: watchdog 492:notify_rc start_cfgsync

 

[Pergola Fabio]

guys, i also recent bought the ac88u, always used merlin
but seems this router have issues with port 5-8 , that fails

is this issue still present in this firmware?

 

[Ken Atkinson]

Had this issue on every firmware occasionally, a reboot returns the missing ports , suspect more a hardware fault , tho if some one can say definately doesn't happen under Merlin i'd probably switch.

 

[Pergola Fabio]

ok, gonna contact asus, but if they replace, i probably have the same issue then?
gonna ask for AX then

 

[Ken Atkinson]

Maybe a new one won't have issue if they fixed it, mine is 3 1/2 years old. Good luck I've always found support about as useful as an ashtray on a motorbike , post how you get on .

 

[Pergola Fabio]

will do, mine is only 4 months old
i submitted a complaint

 

[Ken Atkinson]

Oh that would suggest they haven't fixed it in later production runs then , pretty shocking