Release ASUS RT-AC68U Firmware version 3.0.0.4.386_52048 (2025/08/19)

[banger]

No reason other than not wanting to have to setup the mesh node again. That is unless I have to…

I thought that and I have two nodes. It was relatively painless adding the nodes back.

 

[wouterv]

Is there a list of recommended settings for the RT-AC68U particularly wifi? I did a search but nothing looked right.

As already mentioned: factory defaults or best proven.

One very general recommendation to avoid neighbor disturbance is:
Advanced Settings - Wireless - General - 2.4 GHz
Channel bandwidth: 20 MHz

A general little extra security measure is:
Advanced Settings - Wireless - WPS
Enable WPS: OFF

In case of experienced Wi-Fi troubles, disconnects etc., disable the non standard Wi-Fi options:
Advanced Settings - Wireless - Professional - 2.4 GHz
Modulation Scheme: Up to MCS 7 (802.11n)
Airtime Fairness: Disable
Explicit Beamforming: Disable
Universal Beamforming: Disable

Advanced Settings - Wireless - Professional - 5 GHz
Airtime Fairness: Disable
Universal Beamforming: Disable

 

[wouterv]

In general I strongly recommend preparing for factory... recycling of this model and all variants. The radio is early AC Wave 1 and I'm not sure if it ever got out of "draft" specifications. It uses the main CPU for encryption, can't support many active clients, the sensitivity is low compared to newer hardware, the performance is greatly affected by environment noise.

It is sad you keep posting those advises. For very many people the older ASUS Routers appear rock solid and give no reason to be recycled. Everyone understands that newer devices may give a better performance if all conditions are optimal.
For me, and for sure many users, the RT-AC68U performs very well in our small home environment with a scaled down Internet subscription (because also there is no need for the highest speeds), including home working with a business laptop.
You may remember my bad experience with a RT-AX86U Pro which I returned after some days poor performance (yes, I know this may have been a exemplary bad unit, but still). I believe to see that the RT-AX86U Pro stays behind with its firmware compared to newer models, which is no good indication. Oh wait, AX is old these days now we have BE.
For now I have 0.0 reason to purchase a new router, and I guess this is true for many owners.
Finally there is ASUS who appear to keep releasing firmware updates for this old model and all variants.

 

[Tech9]

It is sad you keep posting those advises.

You don't have to follow nor analyze someone else's advice.

 

[taurelio]

It is sad you keep posting those advises. For very many people the older ASUS Routers appear rock solid and give no reason to be recycled. Everyone understands that newer devices may give a better performance if all conditions are optimal.
For me, and for sure many users, the RT-AC68U performs very well in our small home environment with a scaled down Internet subscription (because also there is no need for the highest speeds), including home working with a business laptop.
You may remember my bad experience with a RT-AX86U Pro which I returned after some days poor performance (yes, I know this may have been a exemplary bad unit, but still). I believe to see that the RT-AX86U Pro stays behind with its firmware compared to newer models, which is no good indication. Oh wait, AX is old these days now we have BE.
For now I have 0.0 reason to purchase a new router, and I guess this is true for many owners.
Finally there is ASUS who appear to keep releasing firmware updates for this old model and all variants.

I bought an new BE92U router for wider coverage on the ground floor of my house, i put my old RT-AC66U B1 as an mesh node, wich to some its not good, its 12 year old hardware etc, on the top floor of my house and working great, yes no wifi 6 but also not needed becasuse as you i have a scaledown internet connection, so it really depends on the individual needs, budget and network setup. Any ISP router will be far worse when compared with an RT-AC66U B1, for example on the isp router you cannot change dns settings (on my country) because of internet piracy sites.

 

[Giuliano]

For a mesh nodes or AP a reset is not needed. Any AiMesh changes should be activated when the node reboots after upgrade

I have an Ax88u Pro as my main router, and a few weeks ago I reverted to my old Ac68U as an Aimesh node. After reading this post, I updated the Ac68u's firmware via the Ax88u's management interface. This is my first time doing this. I haven't performed a factory reset yet. Should I do it or not, as it's an Aimesh node? If I do the factory reset, do I have to redo the Aimesh configuration via Ethernet cable, etc.?

 

[John Adler]

The RT-AC68U works perfect!
no issues at all
rock solid

 

[banger]

g 27 21:01:58 kernel: Can't add zero mac!
Aug 27 21:01:58 kernel: Can't add zero mac!
Aug 27 21:01:58 kernel: Can't add zero mac!
Aug 27 21:01:58 kernel: Can't add zero mac!
Aug 27 21:01:59 kernel: Can't add zero mac!
Aug 27 21:01:59 kernel: Can't add zero mac!
Aug 27 21:01:59 kernel: Can't add zero mac!
Aug 27 21:01:59 kernel: Can't add zero mac!
Aug 27 21:01:59 kernel: Can't add zero mac!
Aug 27 21:01:59 kernel: Can't add zero mac!
Aug 27 21:01:59 kernel: Can't add zero mac!

Getting a lot of these in the log.

 

[bennor]

g 27 21:01:58 kernel: Can't add zero mac!
Aug 27 21:01:58 kernel: Can't add zero mac!
Aug 27 21:01:58 kernel: Can't add zero mac!
Aug 27 21:01:58 kernel: Can't add zero mac!
Aug 27 21:01:59 kernel: Can't add zero mac!
Aug 27 21:01:59 kernel: Can't add zero mac!
Aug 27 21:01:59 kernel: Can't add zero mac!
Aug 27 21:01:59 kernel: Can't add zero mac!
Aug 27 21:01:59 kernel: Can't add zero mac!
Aug 27 21:01:59 kernel: Can't add zero mac!
Aug 27 21:01:59 kernel: Can't add zero mac!

Getting a lot of these in the log.

Others were getting that log message on different firmware recently. More in the following link:

After Upgrade to 3006.102.5: "Can't Add Zero Mac!"

Router: BE86U Firmware Version: 3006.102.5 I've upgraded the firmware from the previous version and now I keep getting the message below. There's no other information or errors. Why is this happening? How can I troubleshoot and find out what's causing it? Thanks. Log: Aug 5 12:24:02...

www.snbforums.com

 

[banger]

Seems that turning off AI Protection solves it. Tried turning off individual components of AI Protection without success the whole thing has to be off and withdraw from the Policy.

 

[Tech9]

I have updated the one RT-AC66U B1 I support remotely and this is what I see in logs:

Aug 22 06:53:34 kernel: dcd/5581: potentially unexpected fatal signal 11.
Aug 22 06:53:34 kernel: Pid: 5581, comm:                  dcd
Aug 22 06:53:34 kernel: CPU: 0    Tainted: P             (2.6.36.4brcmarm #1)
Aug 22 06:53:34 kernel: PC is at 0x32dcc
Aug 22 06:53:34 kernel: LR is at 0x32ce8
Aug 22 06:53:34 kernel: pc : [<00032dcc>]    lr : [<00032ce8>]    psr: 80000010
Aug 22 06:53:34 kernel: sp : bef7cb30  ip : 000a19c4  fp : bef7cb54
Aug 22 06:53:34 kernel: r10: bef7cca8  r9 : 0000dafc  r8 : 0000a620
Aug 22 06:53:34 kernel: r7 : bef7ce57  r6 : 00000008  r5 : bef7cd34  r4 : 403ca4f8
Aug 22 06:53:34 kernel: r3 : 00000000  r2 : 4051ac04  r1 : 4051ad30  r0 : 00000000
Aug 22 06:53:34 kernel: Flags: Nzcv  IRQs on  FIQs on  Mode USER_32  ISA ARM  Segment user
Aug 22 06:53:34 kernel: Control: 10c53c7d  Table: 9a2cc04a  DAC: 00000015
Aug 22 06:55:42 kernel: asd/5821: potentially unexpected fatal signal 11.
Aug 22 06:55:42 kernel: Pid: 5821, comm:                  asd
Aug 22 06:55:42 kernel: CPU: 0    Tainted: P             (2.6.36.4brcmarm #1)
Aug 22 06:55:42 kernel: PC is at 0x404f57a8
Aug 22 06:55:42 kernel: LR is at 0x404f0050
Aug 22 06:55:42 kernel: pc : [<404f57a8>]    lr : [<404f0050>]    psr: a0000010
Aug 22 06:55:42 kernel: sp : bef7f990  ip : 40524da0  fp : 00000000
Aug 22 06:55:42 kernel: r10: 0000001c  r9 : bef7fb18  r8 : 00000020
Aug 22 06:55:42 kernel: r7 : 00000000  r6 : 00000163  r5 : 0000000b  r4 : bef7fa10
Aug 22 06:55:42 kernel: r3 : 00000163  r2 : 00000000  r1 : ffffffff  r0 : 00000163
Aug 22 06:55:42 kernel: Flags: NzCv  IRQs on  FIQs on  Mode USER_32  ISA ARM  Segment user
Aug 22 06:55:42 kernel: Control: 10c53c7d  Table: 9da2c04a  DAC: 00000015

Aug 24 08:42:25 kernel: dcd/21869: potentially unexpected fatal signal 11.
Aug 24 08:42:25 kernel: Pid: 21869, comm:                  dcd
Aug 24 08:42:25 kernel: CPU: 1    Tainted: P             (2.6.36.4brcmarm #1)
Aug 24 08:42:25 kernel: PC is at 0x32dcc
Aug 24 08:42:25 kernel: LR is at 0x32ce8
Aug 24 08:42:25 kernel: pc : [<00032dcc>]    lr : [<00032ce8>]    psr: 80000010
Aug 24 08:42:25 kernel: sp : beff5b30  ip : 000a19c4  fp : beff5b54
Aug 24 08:42:25 kernel: r10: beff5ca8  r9 : 0000dafc  r8 : 0000a620
Aug 24 08:42:25 kernel: r7 : beff5e57  r6 : 00000008  r5 : beff5d34  r4 : 401f64f8
Aug 24 08:42:25 kernel: r3 : 00000000  r2 : 4065f874  r1 : 4065f9dc  r0 : 00000000
Aug 24 08:42:25 kernel: Flags: Nzcv  IRQs on  FIQs on  Mode USER_32  ISA ARM  Segment user
Aug 24 08:42:25 kernel: Control: 10c53c7d  Table: 9a33804a  DAC: 00000015
Aug 24 08:49:18 kernel: asd/22107: potentially unexpected fatal signal 11.
Aug 24 08:49:18 kernel: Pid: 22107, comm:                  asd
Aug 24 08:49:18 kernel: CPU: 1    Tainted: P             (2.6.36.4brcmarm #1)
Aug 24 08:49:18 kernel: PC is at 0x404af7a8
Aug 24 08:49:18 kernel: LR is at 0x404aa050
Aug 24 08:49:18 kernel: pc : [<404af7a8>]    lr : [<404aa050>]    psr: a0000010
Aug 24 08:49:18 kernel: sp : becae990  ip : 404deda0  fp : 00000000
Aug 24 08:49:18 kernel: r10: 0000001c  r9 : becaeb18  r8 : 00000020
Aug 24 08:49:18 kernel: r7 : 00000000  r6 : 00000163  r5 : 0000000b  r4 : becaea10
Aug 24 08:49:18 kernel: r3 : 00000163  r2 : 00000000  r1 : ffffffff  r0 : 00000163
Aug 24 08:49:18 kernel: Flags: NzCv  IRQs on  FIQs on  Mode USER_32  ISA ARM  Segment user
Aug 24 08:49:18 kernel: Control: 10c53c7d  Table: 9a3f404a  DAC: 00000015
Aug 24 08:49:26 rc_service: service 1238:notify_rc restart_firewall
Aug 24 23:31:34 kernel: dcd/1025: potentially unexpected fatal signal 11.
Aug 24 23:31:34 kernel: Pid: 1025, comm:                  dcd
Aug 24 23:31:34 kernel: CPU: 1    Tainted: P             (2.6.36.4brcmarm #1)
Aug 24 23:31:34 kernel: PC is at 0x32dcc
Aug 24 23:31:34 kernel: LR is at 0x32ce8
Aug 24 23:31:34 kernel: pc : [<00032dcc>]    lr : [<00032ce8>]    psr: 80000010
Aug 24 23:31:34 kernel: sp : bea4bb30  ip : 000a19c4  fp : bea4bb54
Aug 24 23:31:34 kernel: r10: bea4bca8  r9 : 0000dafc  r8 : 0000a620
Aug 24 23:31:34 kernel: r7 : bea4be57  r6 : 00000008  r5 : bea4bd34  r4 : 4036d4f8
Aug 24 23:31:34 kernel: r3 : 00000000  r2 : 4048e838  r1 : 4048ea18  r0 : 00000000
Aug 24 23:31:34 kernel: Flags: Nzcv  IRQs on  FIQs on  Mode USER_32  ISA ARM  Segment user
Aug 24 23:31:34 kernel: Control: 10c53c7d  Table: 0754404a  DAC: 00000015
Aug 24 23:35:28 kernel: asd/1211: potentially unexpected fatal signal 11.
Aug 24 23:35:28 kernel: Pid: 1211, comm:                  asd
Aug 24 23:35:28 kernel: CPU: 1    Tainted: P             (2.6.36.4brcmarm #1)
Aug 24 23:35:28 kernel: PC is at 0x404d97a8
Aug 24 23:35:28 kernel: LR is at 0x404d4050
Aug 24 23:35:28 kernel: pc : [<404d97a8>]    lr : [<404d4050>]    psr: a0000010
Aug 24 23:35:28 kernel: sp : be88f990  ip : 40508da0  fp : 00000000
Aug 24 23:35:28 kernel: r10: 0000001c  r9 : be88fb18  r8 : 00000020
Aug 24 23:35:28 kernel: r7 : 00000000  r6 : 00000163  r5 : 0000000b  r4 : be88fa10
Aug 24 23:35:28 kernel: r3 : 00000163  r2 : 00000000  r1 : ffffffff  r0 : 00000163

DCD, ASD, DCD, ASD...

 

[wouterv]

Some would recommend recycling of this model and all variants, I don't.
Did you follow ASUS recommendation performing a factory-default reset after the firmware upgrade?
ASD errors relate to the Asus Security Daemon, are the daily AHS updates successful?

 

[Tech9]

I obviously can’t reset a remote router. It has to hold for few more weeks before being replaced.

 

[wouterv]

One thing I recently noticed is that the RT-AC1900U set as Media Bridge to the RT-AC68U Router often had to restart its wireless:

rc_service: psta_monitor 2979:notify_rc restart_wlcmode 0

Which in my case cause interruption of IP TV that sits behind the Media Bridge.
This is not related to the 52048 upgrade, the problem started weeks before.
At first I believed this was related to the 5 GHz connection changing channels (set to Auto channel in the Router), the first step was to change the Media Bridge connection to 2.4 GHz at 20 MHz with fixed channel 6. This didn't help much while the RSSI for the Media Bridge connection in average is -50 dBm.
Some days ago I changed the Router > Advanced Settings > Wireless > Professional > 2.4 GHz > Roaming assistant to Disable
The threshold was default -70 dBm and the Roaming assistant is Enabled by default. Just because, I also disabled roaming for 5 GHz.
This solved until now the wireless restarts of the Media Bridge.
Maybe a neighbor has changed or added some wireless equipment, causing more disturbance.

[EDIT] Over a week has passed after disabling roaming and the Media Bridge appears rock solid.
It is strange roaming is enabled by default even there is nothing else to roam to in our setup (no Mesh setup).

[EDIT2]
For unknown reason (either the last or previous firmware update or aging hardware) the RT-AC1900U as Media Bridge is no longer stable as it has been for years, showing infrequent drop outs.
I went for the best solution and finally pulled a network cable to the destination.

 

[banger]

Is a mesh node suitable for VOIP adaptor? Had some dropouts when ping my mesh nodes.

 

[LastSilmaril]

With a main router running merlin's final 386.14_2 release and 4-5 nodes running mainline Asus 386_51733, worth upgrading said nodes to this for security features that they don't make use of? Is it possible that the changes introduce could trigger a need to reset and reconfigure each node?

 

[OzarkEdge]

With a main router running merlin's final 386.14_2 release and 4-5 nodes running mainline Asus 386_51733, worth upgrading said nodes to this for security features that they don't make use of?

Probably not necessary for a working node, but I'd do it to keep current. Perhaps do just one node first and see how it runs.

Is it possible that the changes introduce could trigger a need to reset and reconfigure each node?

To be sure, I would update a node, remove it from the AiMesh to automatically reset it, and then add it back to the AiMesh. Done.

OE

 

[LastSilmaril]

Probably not necessary for a working node, but I'd do it to keep current. Perhaps do just one node first and see how it runs.



To be sure, I would update a node, remove it from the AiMesh to automatically reset it, and then add it back to the AiMesh. Done.

OE

Noted, will try next time nobody's around, thank you

 

[banger]

Had to do a factory reset as changing from router to AP wasn't working but did after reset, and it was relatively easy to add mesh nodes back, did it first try.