Release RT-AC68U Firmware version 3.0.0.4.386.43129

[Nemesis200SX]

Hello

same problem here. I found this thread while I was looking for troubleshooting in the internet. I have RT-AC68U Mesh Router with RT-AC66U B1 Mesh Node. Both are running with 41634. Tried to update both to 43129 with the Asus App which didn't work. Then i tried to update both with automatical update through the web gui which also didn't work. Then I tried manual update only the RT68U, the process goes until 100% and says "completed" but firmware stays on 41634. Now I have the problem that my AC66U isn't shown up in the network anymore. Thank you Asus!

 

[Domdus]

WAN/DNS Server 1 and 2 need to be the IP address of upstream resolvers. The Pi-Hole IP goes in LAN/DHCP Server/DNS Server. Or you can manually assign an IP address and include the Pi-Hole address in DNS Server

Exactly that was always my understanding of this config. However in the past it was not enough to just set DHCP DNS - clients would bypass the Pi-hole in some cases. Only with the "faulty" local DNS in WAN config it worked reliable.

I appreciate if it handles in the correct way now. (Still testing)
Also it would finally act correctly as fallback when the local Pi-Hole DNS is not reachable.

 

[bbunge]

Hello

same problem here. I found this thread while I was looking for troubleshooting in the internet. I have RT-AC68U Mesh Router with RT-AC66U B1 Mesh Node. Both are running with 41634. Tried to update both to 43129 with the Asus App which didn't work. Then i tried to update both with automatical update through the web gui which also didn't work. Then I tried manual update only the RT68U, the process goes until 100% and says "completed" but firmware stays on 41634. Now I have the problem that my AC66U isn't shown up in the network anymore. Thank you Asus!

I had no problems with the upgrade. Did the AC68U mesh nodes first then the AC66U_B1 router. All with manual upload. And the system I upgraded is 30 miles away. I have a PC on the remote LAN running Teamviewer which I used to do the upgrade.

 

[jerrytouille]

43129 is 43129, not sure what other number you expect.

Is the 43129 in asus fw version 3.0.0.4.386.43129 the GPL? If not then is there a way to tell what GPL it is? Thank you

 

[Nemesis200SX]

I had no problems with the upgrade. Did the AC68U mesh nodes first then the AC66U_B1 router. All with manual upload. And the system I upgraded is 30 miles away. I have a PC on the remote LAN running Teamviewer which I used to do the upgrade.

fine... will you upgrade mine too?

 

[Intrepid]

fine... will you upgrade mine too?

The firmware has a bug. Too many people can't update using the GUI. The vast majority of home users only know how to use this method. And in your case, even a manual upload didn't work. Asus will have to fix it. I submitted a ticket. I'll wait.
The more Asus Support Tickets that are submitted, the better. Here is where to submit your ticket - you'll need your router serial number:

Contact Us | ASUS

RE: The new firmware 3.0.0.4.386.43129 for the RT-AC68U will NOT install using the GUI in the router.
Update via the Router GUI (Administration, Firmware Upgrade) appears to install and the router reboots, but the firmware version in the router stays the same! Firmware will NOT install using Router GUI.

 

[RMerlin]

Is the 43129 in asus fw version 3.0.0.4.386.43129 the GPL? If not then is there a way to tell what GPL it is? Thank you

GPL archives are generated from firmware release code, not the other way around. The content of the 3.0.0.4.386_41329 GPL archive is the code that was used to build the 3.0.0.4.386_41329 firmware.

 

[ForkWNY]

No issues with the 68U upgrade to 43129 via GUI...upgraded all 4 of my 68U AiMesh nodes from the GUI in the same manner. Had to manually update since they were on the beta release.

 

[banger]

Unexpected errors during the night. Note: after a factory reset and initialize.

May 25 04:07:38 kernel: cfg_server/19329: potentially unexpected fatal signal 11.
May 25 04:07:38 kernel: Pid: 19329, comm: cfg_server
May 25 04:07:38 kernel: CPU: 0 Tainted: P (2.6.36.4brcmarm #1)
May 25 04:07:38 kernel: PC is at 0x405a5bdc
May 25 04:07:38 kernel: LR is at 0x20607c
May 25 04:07:38 kernel: pc : [<405a5bdc>] lr : [<0020607c>] psr: 80000010
May 25 04:07:38 kernel: sp : be1ff910 ip : 405c64b0 fp : 000009e0
May 25 04:07:38 kernel: r10: 000000e8 r9 : 405c6180 r8 : 00000001
May 25 04:07:38 kernel: r7 : 405c61b4 r6 : 00080938 r5 : 405c04f8 r4 : 000000d8
May 25 04:07:38 kernel: r3 : 0000001b r2 : 405c61ac r1 : 00000000 r0 : 0020607d
May 25 04:07:38 kernel: Flags: Nzcv IRQs on FIQs on Mode USER_32 ISA ARM Segment user
May 25 04:07:38 kernel: Control: 10c53c7d Table: 9c98804a DAC: 00000015
May 25 04:07:39 kernel: cfg_server/19328: potentially unexpected fatal signal 11.
May 25 04:07:39 kernel: cfg_server/791: potentially unexpected fatal signal 11.
May 25 04:07:39 kernel: Pid: 791, comm: cfg_server
May 25 04:07:39 kernel: CPU: 0 Tainted: P (2.6.36.4brcmarm #1)
May 25 04:07:39 kernel: PC is at 0x4056a4cc
May 25 04:07:39 kernel: LR is at 0x5ab6c
May 25 04:07:39 kernel: pc : [<4056a4cc>] lr : [<0005ab6c>] psr: 20000010
May 25 04:07:39 kernel: sp : bed95c20 ip : 00075434 fp : 00000000
May 25 04:07:39 kernel: r10: 00075c44 r9 : 0005d2f0 r8 : bed95c38
May 25 04:07:39 kernel: r7 : 0000008e r6 : 00000001 r5 : 00000000 r4 : 00000000
May 25 04:07:39 kernel: r3 : 00000000 r2 : 00000000 r1 : bed95c38 r0 : fffffdfe
May 25 04:07:39 kernel: Flags: nzCv IRQs on FIQs on Mode USER_32 ISA ARM Segment user
May 25 04:07:39 kernel: Control: 10c53c7d Table: 9c98804a DAC: 00000015
May 25 04:07:39 kernel: cfg_server/1022: potentially unexpected fatal signal 11.
May 25 04:07:39 kernel: Pid: 1022, comm: cfg_server
May 25 04:07:39 kernel: CPU: 0 Tainted: P (2.6.36.4brcmarm #1)
May 25 04:07:39 kernel: PC is at 0x40569890
May 25 04:07:39 kernel: LR is at 0x403b4ee4
May 25 04:07:39 kernel: pc : [<40569890>] lr : [<403b4ee4>] psr: 60000010
May 25 04:07:39 kernel: sp : be5ffd70 ip : 403bede8 fp : 00000064
May 25 04:07:39 kernel: r10: 00062447 r9 : 0000005a r8 : 00075754
May 25 04:07:39 kernel: r7 : 000000a2 r6 : 60abbe84 r5 : be5ffdb8 r4 : be5ffdb8
May 25 04:07:39 kernel: r3 : 00000000 r2 : 00000230 r1 : be5ffdb8 r0 : fffffdfc
May 25 04:07:39 kernel: Flags: nZCv IRQs on FIQs on Mode USER_32 ISA ARM Segment user
May 25 04:07:39 kernel: Control: 10c53c7d Table: 9c98804a DAC: 00000015
May 25 04:07:39 kernel: Pid: 19328, comm: cfg_server
May 25 04:07:39 kernel: CPU: 1 Tainted: P (2.6.36.4brcmarm #1)
May 25 04:07:39 kernel: PC is at 0x40569890
May 25 04:07:39 kernel: LR is at 0x403b4ee4
May 25 04:07:39 kernel: pc : [<40569890>] lr : [<403b4ee4>] psr: 60000010
May 25 04:07:39 kernel: sp : be3ff8b0 ip : 403bede8 fp : 00000120
May 25 04:07:39 kernel: r10: 00000000 r9 : 403c33dc r8 : 405c127c
May 25 04:07:39 kernel: r7 : 000000a2 r6 : 001e8481 r5 : be3ff8d8 r4 : 00000000
May 25 04:07:39 kernel: r3 : 00000001 r2 : 00000230 r1 : 00000000 r0 : fffffdfc
May 25 04:07:39 kernel: Flags: nZCv IRQs on FIQs on Mode USER_32 ISA ARM Segment user
May 25 04:07:39 kernel: Control: 10c53c7d Table: 9c98804a DAC: 00000015

 

[master_o_trunks]

Upgraded to 3.0.0.4.386_43129 via RT-AC3100 gui just fine. My RT-AC68U is my AiMesh node. However, after upgrade to this new firmware, I can no longer transfer files into my NAS at a full 1Gbps, the RT-AC68U AiMesh node seems to throttle my speeds down to 600mbps~.

I removed the RT-AC68U as a node from the RT-AC3100 and set it as an AP and I was able to regain my transfers speeds of 1Gbps back to my NAS. My topology from my PC to the NAS is as follows:

PC ethernet -> RT-AC68U LAN 1 -> RT-AC68U WAN -> RT-AC3100 LAN 4 -> RT-AC3100 LAN 1 -> NAS (everything is ethernet backhauled and obviously hardwired cat5e)

Anyone experiencing LAN speed problems with their AiMesh on this current firmware? See attached screencaps.

 

[Intrepid]

Unexpected errors during the night. Note: after a factory reset and initialize.

Were these errors present before the new firmware? Do you know if these errors are benign?
For example, in the Windows event viewer you have to know which warnings/errors are benign and which are not.

 

[banger]

Were these errors present before the new firmware? Do you know if these errors are benign?
For example, in the Windows event viewer you have to know which warnings/errors are benign and which are not.

No these are new errors and the potentially fatal error line was a bit worrying. Will monitor and see if they re-occur.

 

[Ronald Schwerer]

My RT-AC68U is my AiMesh node. However, after upgrade to this new firmware, I can no longer transfer files into my NAS at a full 1Gbps, the RT-AC68U AiMesh node seems to throttle my speeds down t

Are you sure that the node's connection priority didn't get set to Auto instead of Ethernet?

 

[master_o_trunks]

Are you sure that the node's connection priority didn't get set to Auto instead of Ethernet?

It was previously set to ethernet backhaul and I double checked to see if it was the same and it was/is. I even toggle the option on and off and the results are the same. I am currently running the RT-AC68U as an AP now and my speeds are working like they were before this firmware update.

 

[bitsbytes]

Tried updating yesterday using the gui and after going through the update process successfully I'm still on the previous firmware. I only tried once, I'll download the update and try manually later.

 

[Intrepid]

Tried updating yesterday using the gui and after going through the update process successfully I'm still on the previous firmware. I only tried once, I'll download the update and try manually later.

There are several people who posted (including me) with the same problem. At least one couldn't even update manually. There is obviously an issue with the firmware which is a new format (twice the size). I created a support ticket with Asus. The more that do the better - See: http://www.snbforums.com/threads/rt-ac68u-firmware-version-3-0-0-4-386-43129.72638/post-690649

 

[banger]

No repeat of fatal errors although router didnt crash. Mesh still not stable.

 

[RainGater96]

I could flash to this version only using "ASUSTek - CFE miniWeb Server" after setting it to rescue mode. After that, I setup everything from scratch and it's all fine now.

 

[Intrepid]

I could flash to this version only using "ASUSTek - CFE miniWeb Server" after setting it to rescue mode. After that, I setup everything from scratch and it's all fine now.

Thanks for the update. Of course, this shouldn't be necessary. Something is odd with this firmware. By the way, does the act of flashing from rescue mode using miniWeb Server keep your prior user settings or clear your prior settings?

 

[RainGater96]

Thanks for the update. Of course, this shouldn't be necessary. Something is odd with this firmware. By the way, does the act of flashing from rescue mode using miniWeb Server keep your prior user settings or clear your prior settings?

I think it retains the settings but I did a hard reset (WPS procedure) after flashing it as I wanted to configure it fresh. Since I have a script to setup some of the settings, the upgrade process took about 15 - 20 minutes for me.