Release ASUS RT-AX86U Firmware version 3.0.0.4.386_49447 (2022/06/20)

[bbunge]

Added the USB3 thumb drive (32 GB Sandisk), set up AiCloud Sync to my Asus cloud account, connected with my Win11 PC and tried to copy to/from the share on the USB drive. Transfer to started slow, was choppy and took a long time for the 1.5 GB file. Also maxed out the router RAM and froze the GUI until about two minutes after the transfer finished. Copying from the USB drive was almost impossible! As I had saved settings before doing the test I was able to go back easily. Net result, don't use the router to store files. Even small files from the web storage (which I have done for years on prior routers/firmware).

Next I enabled AiProtect and QOS with an update to the Trend signature files. Small impact on RAM which has not changed in four hours. Disabled all USB Applications. Expect this to be the stable config for a while as the router seems to be working well. I really do not need AiCloud Sync so it will stay off for a while.

I have reported the file transfer issue to Asus. Will they ever fix it? Only the Shadow knows...

 

[willyburz]

This firmware version has new wireless drivers and they may detect better DFS channel radio communications. The fact 160MHz used to work before doesn't necessarily mean this firmware is worse. It can be actually better following DFS rules.

What is odd, is that when I had it at 160 my AX devices hit their highest testing ever with this update. I'm on Gig with 2.5 modem to router 2.5 connection, and at highest I've tested 1.4gig at router...My Ax devices hit anywhere from 620-766 historically, I've hit 823 and 815 at about 20-25 feet out after this latest update, but it kicks back to 80 hz so not sure how that'll impact the max/consistancy??

 

[Tech9]

I hate the syslog on this firmware. Pages and pages of useless messages.

Jun 29 17:03:55 kernel: CONSOLE: 166594.850 tx:prep:802.1x
Jun 29 17:03:55 kernel: CONSOLE: 166594.851 tx:prep:802.1x
Jun 29 17:03:55 kernel: CONSOLE: 166594.852 tx:prep:802.1x
Jun 29 17:03:55 kernel: CONSOLE: 166594.852 tx:prep:802.1x
Jun 29 17:03:55 kernel: CONSOLE: 166594.853 tx:prep:802.1x
Jun 29 17:03:55 kernel: CONSOLE: 166594.857 rx:tohost:802.1x
Jun 29 17:03:55 kernel: CONSOLE: 166595.081 tx:prep:802.1x
Jun 29 17:03:55 kernel: CONSOLE: 166595.172 tx:prep:802.1x
Jun 29 17:03:55 kernel: CONSOLE: 166595.375 tx:prep:802.1x
Jun 29 17:03:55 kernel: CONSOLE: 166595.376 tx:prep:802.1x
Jun 29 17:03:56 kernel: CONSOLE: 166595.477 tx:prep:802.1x
Jun 29 17:03:56 kernel: CONSOLE: 166595.581 tx:prep:802.1x
Jun 29 17:04:12 kernel: CONSOLE: 166612.148 wl1: r0hole: tx_exp_seq 0x1e1, seq 0x1e2
Jun 29 17:04:17 kernel: CONSOLE: 166616.704 wl1: r0hole: tx_exp_seq 0x4, seq 0x5
Jun 29 17:04:32 kernel: CONSOLE: 166631.504 wl1: r0hole: tx_exp_seq 0xd4e, seq 0xd4f
Jun 29 17:16:46 kernel: CONSOLE: 167362.378 wlc_ap_authresp: status 0
Jun 29 17:16:46 kernel: CONSOLE: 167362.380 wlc_ap_process_assocreq_done status 0
Jun 29 17:16:46 kernel: CONSOLE: 167362.384 iov:SCB_DEAUTH
Jun 29 17:16:46 kernel: CONSOLE: 167362.386 tx:prep:802.1x
Jun 29 17:16:46 kernel: CONSOLE: 167362.389 tx:prep:802.1x
Jun 29 17:16:46 kernel: CONSOLE: 167362.392 wl1: wlc_rrm_send_nbrrep: Neighbor Report element is empty
Jun 29 17:16:46 kernel: CONSOLE: 167362.392 iov:SCB_AUTH

 

[SwampKracker]

I hate the syslog on this firmware. Pages and pages of useless messages.

Jun 29 17:03:55 kernel: CONSOLE: 166594.850 tx:prep:802.1x
Jun 29 17:03:55 kernel: CONSOLE: 166594.851 tx:prep:802.1x
Jun 29 17:03:55 kernel: CONSOLE: 166594.852 tx:prep:802.1x
Jun 29 17:03:55 kernel: CONSOLE: 166594.852 tx:prep:802.1x
Jun 29 17:03:55 kernel: CONSOLE: 166594.853 tx:prep:802.1x
Jun 29 17:03:55 kernel: CONSOLE: 166594.857 rx:tohost:802.1x
Jun 29 17:03:55 kernel: CONSOLE: 166595.081 tx:prep:802.1x
Jun 29 17:03:55 kernel: CONSOLE: 166595.172 tx:prep:802.1x
Jun 29 17:03:55 kernel: CONSOLE: 166595.375 tx:prep:802.1x
Jun 29 17:03:55 kernel: CONSOLE: 166595.376 tx:prep:802.1x
Jun 29 17:03:56 kernel: CONSOLE: 166595.477 tx:prep:802.1x
Jun 29 17:03:56 kernel: CONSOLE: 166595.581 tx:prep:802.1x
Jun 29 17:04:12 kernel: CONSOLE: 166612.148 wl1: r0hole: tx_exp_seq 0x1e1, seq 0x1e2
Jun 29 17:04:17 kernel: CONSOLE: 166616.704 wl1: r0hole: tx_exp_seq 0x4, seq 0x5
Jun 29 17:04:32 kernel: CONSOLE: 166631.504 wl1: r0hole: tx_exp_seq 0xd4e, seq 0xd4f
Jun 29 17:16:46 kernel: CONSOLE: 167362.378 wlc_ap_authresp: status 0
Jun 29 17:16:46 kernel: CONSOLE: 167362.380 wlc_ap_process_assocreq_done status 0
Jun 29 17:16:46 kernel: CONSOLE: 167362.384 iov:SCB_DEAUTH
Jun 29 17:16:46 kernel: CONSOLE: 167362.386 tx:prep:802.1x
Jun 29 17:16:46 kernel: CONSOLE: 167362.389 tx:prep:802.1x
Jun 29 17:16:46 kernel: CONSOLE: 167362.392 wl1: wlc_rrm_send_nbrrep: Neighbor Report element is empty
Jun 29 17:16:46 kernel: CONSOLE: 167362.392 iov:SCB_AUTH

The standard syslog settings should hide that nonsense, but the standard settings are set to allow far too much logging. I use warning/warning and have very few messages appear in syslog. If there is a problem, I can increase the verbosity to see all the useless messages and hopefully, the problem I am trying to solve.

 

[SteverinoLA]

I hate the syslog on this firmware. Pages and pages of useless messages.

Jun 29 17:03:55 kernel: CONSOLE: 166594.850 tx:prep:802.1x
Jun 29 17:03:55 kernel: CONSOLE: 166594.851 tx:prep:802.1x
Jun 29 17:03:55 kernel: CONSOLE: 166594.852 tx:prep:802.1x
Jun 29 17:03:55 kernel: CONSOLE: 166594.852 tx:prep:802.1x
Jun 29 17:03:55 kernel: CONSOLE: 166594.853 tx:prep:802.1x
Jun 29 17:03:55 kernel: CONSOLE: 166594.857 rx:tohost:802.1x
Jun 29 17:03:55 kernel: CONSOLE: 166595.081 tx:prep:802.1x
Jun 29 17:03:55 kernel: CONSOLE: 166595.172 tx:prep:802.1x
Jun 29 17:03:55 kernel: CONSOLE: 166595.375 tx:prep:802.1x
Jun 29 17:03:55 kernel: CONSOLE: 166595.376 tx:prep:802.1x
Jun 29 17:03:56 kernel: CONSOLE: 166595.477 tx:prep:802.1x
Jun 29 17:03:56 kernel: CONSOLE: 166595.581 tx:prep:802.1x
Jun 29 17:04:12 kernel: CONSOLE: 166612.148 wl1: r0hole: tx_exp_seq 0x1e1, seq 0x1e2
Jun 29 17:04:17 kernel: CONSOLE: 166616.704 wl1: r0hole: tx_exp_seq 0x4, seq 0x5
Jun 29 17:04:32 kernel: CONSOLE: 166631.504 wl1: r0hole: tx_exp_seq 0xd4e, seq 0xd4f
Jun 29 17:16:46 kernel: CONSOLE: 167362.378 wlc_ap_authresp: status 0
Jun 29 17:16:46 kernel: CONSOLE: 167362.380 wlc_ap_process_assocreq_done status 0
Jun 29 17:16:46 kernel: CONSOLE: 167362.384 iov:SCB_DEAUTH
Jun 29 17:16:46 kernel: CONSOLE: 167362.386 tx:prep:802.1x
Jun 29 17:16:46 kernel: CONSOLE: 167362.389 tx:prep:802.1x
Jun 29 17:16:46 kernel: CONSOLE: 167362.392 wl1: wlc_rrm_send_nbrrep: Neighbor Report element is empty
Jun 29 17:16:46 kernel: CONSOLE: 167362.392 iov:SCB_AUTH

Same with this update. I went and set loglevel to 2 hoping to get the crap gone and the few things I do care about, but nope, loglevel=2 removes everything useful and gives 1300 of these rows every 24 hours:

Jun 29 00:06:35 acsd: acs_candidate_score_intf(1108): eth7: intf check failed for chanspec: 0xe832 (36/160)
Jun 29 00:06:35 acsd: acs_candidate_score_bgnoise(1573): eth7: bgnoise check failed for chanspec: 0xe832 (36/160)
Jun 29 00:06:35 acsd: acs_candidate_score_txop(1831): eth7: txop check failed for chanspec: 0xe832 (36/160)
Jun 29 00:06:35 acsd: acs_candidate_score_intf(1108): eth7: intf check failed for chanspec: 0xe932 (40/160)
Jun 29 00:06:35 acsd: acs_candidate_score_bgnoise(1573): eth7: bgnoise check failed for chanspec: 0xe932 (40/160)
Jun 29 00:06:35 acsd: acs_candidate_score_txop(1831): eth7: txop check failed for chanspec: 0xe932 (40/160)
Jun 29 00:06:35 acsd: acs_candidate_score_intf(1108): eth7: intf check failed for chanspec: 0xea32 (44/160)
Jun 29 00:06:35 acsd: acs_candidate_score_bgnoise(1573): eth7: bgnoise check failed for chanspec: 0xea32 (44/160)
Jun 29 00:06:35 acsd: acs_candidate_score_txop(1831): eth7: txop check failed for chanspec: 0xea32 (44/160)
Jun 29 00:06:35 acsd: acs_candidate_score_intf(1108): eth7: intf check failed for chanspec: 0xeb32 (48/160)
Jun 29 00:06:35 acsd: acs_candidate_score_bgnoise(1573): eth7: bgnoise check failed for chanspec: 0xeb32 (48/160)
Jun 29 00:06:35 acsd: acs_candidate_score_txop(1831): eth7: txop check failed for chanspec: 0xeb32 (48/160)

 

[SteverinoLA]

The standard syslog settings should hide that nonsense, but the standard settings are set to allow far too much logging. I use warning/warning and have very few messages appear in syslog. If there is a problem, I can increase the verbosity to see all the useless messages and hopefully, the problem I am trying to solve.

What the commands to do what you are doing?

 

[SwampKracker]

What the commands to do what you are doing?

No commands. System Log, General Log, Default message log level - warning and Log only messages more urgent than - warning.

 

[SteverinoLA]

I don't see those options:

 

[SteverinoLA]

And now WTF, AIMesh bindings aren't working either. Can't bind to the right mesh node, and all bindings just show unbound icon.

 

[Tech9]

No commands. System Log, General Log, Default message log level - warning and Log only messages more urgent than - warning.

This thread is for Asuswrt, not Asuswrt-Merlin.

 

[SwampKracker]

I don't see those options:

View attachment 42287

My apologies. I did not consider that Merlin may have added features to allow for changing the level of logging via the GUI. I believe there are NVRAM commands one can use to change the log levels.

nvram set message_loglevel=4
nvram set log_level=4
nvram commit

 

[SAL9K]

What’s the difference btwn log_level and message_loglevel?

 

[SwampKracker]

What’s the difference btwn log_level and message_loglevel?

One sets the log level for the firmware. The other determines which log messages gets stored in syslog. Not sure which is responsible for what without some experimentation.

 

[Tech9]

A new development in my firmware testing on AX86U:

Release - Asuswrt-Merlin 386.7 is now available for all models

My initial setup was running only the RT-AX86U that replaced my pair of AC86U units. No Smart Connect but same SSID on both bands and Roam Assist turned on on both bands. It was a couple of my 2.4g IoT devices that kept dropping of and reconnecting while running 386.7 I decided to add one of my...

www.snbforums.com

I found the previous wireless drivers used in Asuswrt 46061 indeed work better in my Wi-Fi environment.

 

[DiGz_Au]

A new development in my firmware testing on AX86U:

Release - Asuswrt-Merlin 386.7 is now available for all models

My initial setup was running only the RT-AX86U that replaced my pair of AC86U units. No Smart Connect but same SSID on both bands and Roam Assist turned on on both bands. It was a couple of my 2.4g IoT devices that kept dropping of and reconnecting while running 386.7 I decided to add one of my...

www.snbforums.com

I found the previous wireless drivers used in Asuswrt 46061 indeed work better in my Wi-Fi environment.

Agreed 100%

 

[neil0311]

A new development in my firmware testing on AX86U:

Release - Asuswrt-Merlin 386.7 is now available for all models

My initial setup was running only the RT-AX86U that replaced my pair of AC86U units. No Smart Connect but same SSID on both bands and Roam Assist turned on on both bands. It was a couple of my 2.4g IoT devices that kept dropping of and reconnecting while running 386.7 I decided to add one of my...

www.snbforums.com

I found the previous wireless drivers used in Asuswrt 46061 indeed work better in my Wi-Fi environment.

Same here. Nothing on this version worked better for me than 46061 does.

Hoping the next spin of the wheel has better prizes.

 

[bbunge]

Agreed 100%

Not having problems here with WIFI. Using default settings with DFS enabled and WPA2/ WPA3-Personal.

 

[DiGz_Au]

Not having problems here with WIFI. Using default settings with DFS enabled and WPA2/ WPA3-Personal.

Lucky you, I'm seeing micro disconnects on my phone's on either bands. Manual or auto channel. Seems a few people encountered this also. Older wifi drivers are perfect in my eyes

 

[BobbyFlobby]

Lucky you, I'm seeing micro disconnects on my phone's on either bands. Manual or auto channel. Seems a few people encountered this also. Older wifi drivers are perfect in my eyes

yep, this release was awful with my setup, wifi was drunk. older version no issues.

 

[DiGz_Au]

yep, this release was awful with my setup, wifi was drunk. older version no issues.

I use Merlin( do test both stock and Merlin btw) and I did return to the latest update based on this stock firmware. I didn't factory reset, I turned dfs on for 5ghz and moved the wifi country to Australia which appears now. Things improved it seems.