Release ASUS RT-AC68U Firmware version 3.0.0.4.386.51665

[wouterv]

Hmmm... my RT-AC68U Router did the same over night:

May 24 00:59:50 kernel: asd/181: potentially unexpected fatal signal 11.
May 24 00:59:50 kernel: Pid: 181, comm:                  asd
May 24 00:59:50 kernel: CPU: 1    Tainted: P             (2.6.36.4brcmarm #1)
May 24 00:59:50 kernel: PC is at 0x404ff5b0
May 24 00:59:50 kernel: LR is at 0x405001b4
May 24 00:59:50 kernel: pc : [<404ff5b0>]    lr : [<405001b4>]    psr: 20000010
May 24 00:59:50 kernel: sp : bea3e448  ip : 4050c994  fp : ffffffff
May 24 00:59:50 kernel: r10: 40503648  r9 : 405043bc  r8 : 00016900
May 24 00:59:50 kernel: r7 : 00016958  r6 : bea3e46c  r5 : 4050c8c8  r4 : 0001e960
May 24 00:59:50 kernel: r3 : 000306e8  r2 : 00000010  r1 : 00000400  r0 : 00000000
May 24 00:59:50 kernel: Flags: nzCv  IRQs on  FIQs on  Mode USER_32  ISA ARM  Segment user
May 24 00:59:50 kernel: Control: 10c53c7d  Table: 9ee8804a  DAC: 00000015
May 24 00:59:54 rc_service: service 31020:notify_rc restart_firewall

And RAM usage changed:

See my post of last Friday with 116 MB Used:

Reported to ASUS via the Router Feedback feature.

The RT-AC1900U as Media Bridge connected to the Router did continue without log messages.

 

[wouterv]

Just as reference, the RT-AC1900U Media Bridge RAM usage:

Surprisingly high for a Media Bridge with one wired client device (the TV settop box) which is standby during the screenshot.
The RT-AC68U Router RAM ussage is not really changed yet.

 

[wouterv]

RAM usage is stable over night for both the Router and Media Bridge.
Here the reply from ASUS:

Dear Valued Customer,

During routine security maintenance, our technical team discovered an error in the configuration of our server settings file, which could potentially cause an interruption in network connectivity on part of the routers.

Our technical team has urgently addressed the server issue and impacted routers should return to normal operation. If your device was affected, we recommend the following:

• Manually reboot your router
• If rebooting does not resolve the issue, please save the settings file, perform a hard reset (factory default), and then re-upload the settings file (follow the directions in the https://www.asus.com/support/FAQ/1050464)
• If you cannot access the user interface to save settings or perform a reset, you can press the RESET button for about 5-10 seconds until the power LED indicator on the router starts to blink, which means the reset is completed. https://www.asus.com/support/FAQ/1000925/#m2

If there are any further developments around this issue, we will immediately update our users.

We deeply apologize for any inconvenience this incident may have caused and are committed to preventing such an incident from happening again.

Thank you for your understanding and support.

It looks like a quite generic reply that may apply to different routers.
Later today I may perform a hard reset for both and manual configure them.

 

[wouterv]

RAM usage of the RT-AC1900U Media Bridge creep-ed up to 98 MB (see post #42) and after a plain reboot it dropped to around 60 MB:

Let's see what it does over time.
The RT-AC68U Router RAM usage seems stable to around 84 MB.

 

[Justinh]

When I logout of the web UI, it doesn't completely log me out - very strange. I can browse back to the login page (https://...:8443) and I'm not prompted to login, I go straight to the "Network Map" page, and that page shows 0 clients and no defined wireless SSIDs. I have to open a private window or restart the browser for things to be right again.

 

[ieatsoop]

I can browse back to the login page (https://...:8443) and I'm not prompted to login,

This happened to me but on an RT-AX89X. The solution I found was to change the URL to https://router_ip: port/Main_Login.asp then I consistently got the login page. It was eventually resolved with beta FW. It seems that using https://router_ip: port does not redirect to the correct URL. However, in my case I tried using the URL https://router_ip: port/index.asp, and that redirected correctly to https://router_ip: port/Main_Login.asp. Try submitting feedback to Asus to see if they can get it resolved for you.

 

[Arctic Ace]

I have encountered critical AiMesh connectivity issues with Asus RT-AC68U and Asus RP-AX56 after the firmware update. After turning RP-AX56 on, AiMesh works few mins but after that connectivity to AC68U disappears and RP's led will turn from blue to red.

Separate post here.

 

[sol1109]

Since updating to this version my WiFi drops out several times a day. I will do a factory default and reenter setups as soon as I can get everyone off the network for an hour.

 

[wouterv]

See also post #40 and #41, check your router: maybe a plain reboot will do.
No WiFi issues here with the 3.0.0.4.386.51665 firmware.

 

[banger]

Memory use seems to have settled down after 29 days uptime. Settled at 100mb free.

 

[wouterv]

RT-AC68U Router, uptime 30 days (with some memory action in between, see post #41):

RT-AC1900U Media Bridge, uptime 12 days (see post #44):

Both seems to be stable as well.

 

[Poomba1]

NE1 tried this firmware on a an AC68U in AiMesh node mode?
I have basically given up, "3.0.0.4.386_48262" is the last known stable firmware version for these units I use with my GT-AX11000.
In AiMesh node mode they only talk to the Master node anyways so security is less of an issue, they're not doing much else nor can you log into them directly (OTA).

 

[Justinh]

I can no longer add an address to the Network Services Filter. Has anyone else tried with this firmware build?

After I hit apply and it processes, the table is empty.

I had this address in the table when I upgraded, but needed to temporarily remove it. Now I can't add it back.

 

[sol1109]

See also post #40 and #41, check your router: maybe a plain reboot will do.
No WiFi issues here with the 3.0.0.4.386.51665 firmware.

Not sure how #40 and 41 (memory issues) apply to me. Anyway I did the factory default and reentered my settings. I still see WIFI occasionally drop off but have not been able to catch anything on the router end yet.

 

[wouterv]

What is this I found in the General log??

Jun 16 17:14:15 kernel: SHN Release Version: 2.0.2 7812743e
Jun 16 17:14:15 kernel: UDB Core Version: 0.2.20
Jun 16 17:14:15 kernel: sizeof forward pkt param = 192
Jun 16 17:14:16 BWDPI: fun bitmap = 3

 

[wouterv]

Not sure how #40 and 41 (memory issues) apply to me. Anyway I did the factory default and reentered my settings. I still see WIFI occasionally drop off but have not been able to catch anything on the router end yet.

Have you tried these settings:

• 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]

Is the router degrading or is it a firmware issue?

Jun 19 13:46:48 kernel: asd/31013: potentially unexpected fatal signal 11.
Jun 19 13:46:48 kernel: Pid: 31013, comm:                  asd
Jun 19 13:46:48 kernel: CPU: 0    Tainted: P             (2.6.36.4brcmarm #1)
Jun 19 13:46:48 kernel: PC is at 0x405105b0
Jun 19 13:46:48 kernel: LR is at 0x405111b4
Jun 19 13:46:48 kernel: pc : [<405105b0>]    lr : [<405111b4>]    psr: 20000010
Jun 19 13:46:48 kernel: sp : bec21448  ip : 4051d994  fp : ffffffff
Jun 19 13:46:48 kernel: r10: 40514648  r9 : 405153bc  r8 : 00016900
Jun 19 13:46:48 kernel: r7 : 00016958  r6 : bec2146c  r5 : 4051d8c8  r4 : 000187a8
Jun 19 13:46:48 kernel: r3 : 0001f020  r2 : 61745f6c  r1 : 00000400  r0 : 00000000
Jun 19 13:46:48 kernel: Flags: nzCv  IRQs on  FIQs on  Mode USER_32  ISA ARM  Segment user
Jun 19 13:46:48 kernel: Control: 10c53c7d  Table: 9a96804a  DAC: 00000015
Jun 19 13:46:55 rc_service: service 670:notify_rc restart_firewall

See also post #40 and #41.

 

[banger]

Is the router degrading or is it a firmware issue?

Jun 19 13:46:48 kernel: asd/31013: potentially unexpected fatal signal 11.
Jun 19 13:46:48 kernel: Pid: 31013, comm:                  asd
Jun 19 13:46:48 kernel: CPU: 0    Tainted: P             (2.6.36.4brcmarm #1)
Jun 19 13:46:48 kernel: PC is at 0x405105b0
Jun 19 13:46:48 kernel: LR is at 0x405111b4
Jun 19 13:46:48 kernel: pc : [<405105b0>]    lr : [<405111b4>]    psr: 20000010
Jun 19 13:46:48 kernel: sp : bec21448  ip : 4051d994  fp : ffffffff
Jun 19 13:46:48 kernel: r10: 40514648  r9 : 405153bc  r8 : 00016900
Jun 19 13:46:48 kernel: r7 : 00016958  r6 : bec2146c  r5 : 4051d8c8  r4 : 000187a8
Jun 19 13:46:48 kernel: r3 : 0001f020  r2 : 61745f6c  r1 : 00000400  r0 : 00000000
Jun 19 13:46:48 kernel: Flags: nzCv  IRQs on  FIQs on  Mode USER_32  ISA ARM  Segment user
Jun 19 13:46:48 kernel: Control: 10c53c7d  Table: 9a96804a  DAC: 00000015
Jun 19 13:46:55 rc_service: service 670:notify_rc restart_firewall

See also post #40 and #41.

Firmware. Send Feedback.

 

[sol1109]

Have you tried these settings:
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

What I am seeing in the log is a lot of Deauth_ind followed by Auth & Assoc for the same MAC address. In the below example I was watching YouTube on the smart TV when this occurred.

Jun 30 07:38:25 syslog: wlceventd_proc_event(494): eth2: Deauth_ind MAC#, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:0​

Jun 30 07:38:30 syslog: wlceventd_proc_event(530): eth2: Auth MAC#, status: Successful (0), rssi:0​

Jun 30 07:38:30 syslog: wlceventd_proc_event(559): eth2: Assoc MAC#, status: Successful (0), rssi:0​

On both bands these were the settings. I will try each one and see if any difference is found.

• Modulation was set to MCS 9
• Airtime Fairness was Enable
• Explicit Beamforming Enable
• Universal Beamforming Enable

 

[wouterv]

Make all the suggested settings at once, they are all features that are beyond the 802.11ac standard.