Release Asuswrt-Merlin 3004.388.4 is now available

[MDM]

From Beta 3 to 3004.388.4 - A-OK

 

[AntonK]

The log messages indicate that the ethernet connection was unstable. If you are getting the same messages after switching to a different LAN port, then there may be something wrong with the plug on that cable (or on the 2.5 gbps LAN port).

Thanks. I will check this out.

 

[pulp]

Wifey Zooming all day and two kids online gaming from their PC's, one upstairs and one in the basement. Blazing fast and solid, thank you Merlin!

 

[learning_curve]

Yes, I had my Desktop connected to it. I have now removed the Desktop's ethernet cable from that port to one of the LAN ports.

FWIW IF I have a MacOS device connected via Ethernet and it's at 'sleeping' status, these 'warnings' plus a confirmatory indication on the Ethernet Ports GUI (yellow not green / 100 mbps not 1000 mbps) are shown. These 'warnings' are not new (for me) to this Firmware Release (they have been present on previous releases) but don't cause any problems at all, other than perhaps. info overload Can't comment on any Non-Apple hardware connected via Ethernet results, I don't have any / don't use any.

Aug 23 05:50:38 kernel: eth4 (Ext switch port: 3) (Logical Port: 11) (phyId: b) Link DOWN.
Aug 23 05:50:40 kernel: eth4 (Ext switch port: 3) (Logical Port: 11) (phyId: b) Link Up at 100 mbps full duplex
Aug 23 05:51:40 kernel: eth4 (Ext switch port: 3) (Logical Port: 11) (phyId: b) Link DOWN.
Aug 23 05:51:43 kernel: eth4 (Ext switch port: 3) (Logical Port: 11) (phyId: b) Link Up at 1000 mbps full duplex
Aug 23 05:52:29 kernel: eth4 (Ext switch port: 3) (Logical Port: 11) (phyId: b) Link DOWN.
Aug 23 05:52:31 kernel: eth4 (Ext switch port: 3) (Logical Port: 11) (phyId: b) Link Up at 100 mbps full duplex
Aug 23 05:55:06 kernel: eth4 (Ext switch port: 3) (Logical Port: 11) (phyId: b) Link DOWN.
Aug 23 05:55:09 kernel: eth4 (Ext switch port: 3) (Logical Port: 11) (phyId: b) Link Up at 1000 mbps full duplex

 

[AntonK]

FWIW IF I have a MacOS device connected via Ethernet and it's at 'sleeping' status, these 'warnings' plus a confirmatory indication on the Ethernet Ports GUI (yellow not green / 100 mbps not 1000 mbps) are shown. These 'warnings' are not new (for me) to this Firmware Release (they have been present on previous releases) but don't cause any problems at all, other than perhaps. info overload Can't comment on any Non-Apple hardware connected via Ethernet results, I don't have any / don't use any.

Thank you for that. Appreciated.

And thanks too @maxbraketorque

 

[Jumpstarter]

tried again. colossal failure. did wps reset. did factory reset. pushed the pin. held buttons. I even did logical reset on backup page. nothing worked. reprogrammed from scratch and reboots still occurred on 3004.388.4. random reboots every 2 minutes.

Loaded factory ASUS version RT-AX88U_PRO_3.0.0.6_102_21514-g9affda2_136-g5d23c_nand_squashfs
absolutely no issues.

I had a similar issue with the AX86. Turns out I had a corrupt storage device plugged into the router. Unplugging it allowed the router to boot properly.

 

[ZNP_83]

Something about this completely hosed my Wireguard VPN connection even after reverting to the prior beta. No matter what I do I cannot get my desktop to actually run through the Wireguard VPN on the router again.

 

[laracroftonline]

Working flawless on my gt-axe11000

 

[jata]

Following my upgrade, my log was filling with:
May 5 01:05:49 acsd: eth7: Selecting 5g band ACS policy
May 5 01:05:49 acsd: acs_init_run(1111): acs_start eth7 cannot select chanspec with the wrong info
May 5 01:05:52 acsd: eth7: Selecting 5g band ACS policy
May 5 01:05:52 acsd: acs_init_run(1111): acs_start eth7 cannot select chanspec with the wrong info
May 5 01:05:55 acsd: eth7: Selecting 5g band ACS policy
May 5 01:05:55 acsd: acs_init_run(1111): acs_start eth7 cannot select chanspec with the wrong info

I reset my 5-Ghz channel and width and all is wonderful for about 24 hours.

@Morris - I had the same issue with the beta. The issue was that i had set fixed channel 36 for 5g band. I fixed the issue by switching to auto on 5g and it was resolved.

Maybe there is an issue with AX86U/S with the this GPL and fixed channel 36 on 5g

 

[grateful70]

I had a similar issue with the AX86. Turns out I had a corrupt storage device plugged into the router. Unplugging it allowed the router to boot properly.

Yesterday, I had suspected the usb thumb drive but today's adventures were no better with the usb completely unplugged. I'm a network guy but certainly not a coder. Despite my efforts there must be something that doesn't get wiped by either factory reset or wps reset. even with everything wiped when I went back to 388..2.2, it knew about my old dhcp pool. regardless, I'll leave it on Asus code for now. I work from home and I need something stable.

 

[bbunge]

Yesterday, I had suspected the usb thumb drive but today's adventures were no better with the usb completely unplugged. I'm a network guy but certainly not a coder. Despite my efforts there must be something that doesn't get wiped by either factory reset or wps reset. even with everything wiped when I went back to 388..2.2, it knew about my old dhcp pool. regardless, I'll leave it on Asus code for now. I work from home and I need something stable.

Known issue with the AX86U that a hard factory reset doesn't always clear the settings. Factory reset with initialize usually works.

 

[grateful70]

Known issue with the AX86U that a hard factory reset doesn't always clear the settings. Factory reset with initialize usually works.

For reason nothing worked for 388.4
I did a logical reset to factory then I reset holding a pin. A wps reset. No USB drive. It always ended up with unstable Reboots. I then loaded asus 3.0.0.6 and all was good. I then tried 388.4 again and it still failed. Went back to 3.0.0.6.

 

[ZeustheAsus]

Is the next version of RMerlin going to be based on 3.0.0.6 out of curiosity?

 

[AntonK]

Is the next version of RMerlin going to be based on 3.0.0.6 out of curiosity?

See this from RMerlin.

 

[MNoisy]

Great work as always, Merlin. Thank you!

I updated this morning from beta to 3004.388.4_0_rog on my ax16000 (with AiMesh ETH backhaul for all nodes ax58, ac88, and ac5300). AX on the latest merlin build and ac's on the latest alpha builds.

The only issue I noticed after some quick testing was my asus ddns config said "inactive" despite it being operational and the certificate being active and valid. It was resolved by completely removing the ddns and adding it again.

When I got back home from work, I saw the log was flooded with the same error every 30 seconds or so. I wanted to check to see if others are seeing anything similar before I go down the rabbit hole to troubleshoot.

Aug 22 22:09:41 rc_service: watchdog 3038:notify_rc stop_aae
Aug 22 22:09:41 rc_service: watchdog 3038:notify_rc start_mastiff
Aug 22 22:09:41 rc_service: waitting "stop_aae" via watchdog ...
Aug 22 22:09:42 Mastiff: init

Downgrading back to beta 3 on just the axe16000 resolves the issue. Upgrade to the latest again and it starts occurring right away.

Since I have alpha builds on the AC models, I wanted to check here before starting to troubleshoot deeper. I wasn't able to determine exactly what the message means and what issues, if any, it is causing. I didn't find anything in the changelog that was related, but since a downgrade resolved it, I was hoping anyone could chime in before I start taking the steps to troubleshoot.

Thank you!

 

[Yiannis]

I am getting random router reboots (RT-AX86U Pro). The issue started on beta3 and is present on latest 388.4. I did also a WPS factory reset and reinstall but the reboot issue remains.

I would like to post the log entires between two consequtive reboots happened within 30 minutes, but the page doesn't let me.

 

[Thermaltake]

Flashed yesterday, everything is working fine.

few things in log I don't know what they are

Aug 22 22:34:58 kernel: bcm_i2c: bus 0: Failed to detect SFP: 100 retries exhausted
Aug 22 22:35:23 rc_service: rc 2835:notify_rc restart_wrs
Aug 22 22:35:26 BWDPI: fun bitmap = 43f
Aug 22 22:39:20 wlceventd: wlceventd_proc_event(685): eth6: Auth E8:7F:6B:FF:75:63, status: Successful (0), rssi:0
Aug 22 22:39:20 wlceventd: wlceventd_proc_event(722): eth6: Assoc E8:7F:6B:FF:75:63, status: Successful (0), rssi:-48
Aug 22 22:42:14 wlceventd: wlceventd_proc_event(685): eth7: Auth E4:0E:EE:240:35, status: Successful (0), rssi:0
Aug 22 22:42:14 wlceventd: wlceventd_proc_event(722): eth7: Assoc E4:0E:EE:240:35, status: Successful (0), rssi:-62
Aug 22 22:42:15 wlceventd: wlceventd_proc_event(685): eth7: Auth 76:28:EC:BC:F4:38, status: Successful (0), rssi:0
Aug 22 22:42:15 wlceventd: wlceventd_proc_event(722): eth7: Assoc 76:28:EC:BC:F4:38, status: Successful (0), rssi:-52
Aug 22 22:44:36 wlceventd: wlceventd_proc_event(685): eth7: Auth F6:0B:91:EA:AF:13, status: Successful (0), rssi:0
Aug 22 22:44:36 wlceventd: wlceventd_proc_event(722): eth7: Assoc F6:0B:91:EA:AF:13, status: Successful (0), rssi:-54
Aug 22 22:45:57 wlceventd: wlceventd_proc_event(645): eth6: Deauth_ind 84:0D:8E:0D:26:F4, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:-67
Aug 22 22:45:57 wlceventd: wlceventd_proc_event(645): eth6: Deauth_ind 84:0D:8E:0D:26:F4, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:-67
Aug 22 22:45:58 wlceventd: wlceventd_proc_event(662): eth6: Disassoc 84:0D:8E:0D:26:F4, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Aug 22 22:41:10 kernel: eth4 (Ext switch port: 3) (Logical Port: 11) (phyId: b) Link DOWN.
Aug 23 06:39:26 kernel: eth4 (Ext switch port: 3) (Logical Port: 11) (phyId: b) Link UP at 1000 mbps full duplex
Aug 23 06:39:34 kernel: eth4 (Ext switch port: 3) (Logical Port: 11) (phyId: b) Link DOWN.
Aug 23 06:39:46 kernel: eth4 (Ext switch port: 3) (Logical Port: 11) (phyId: b) Link UP at 1000 mbps full duplex

last one is probably when I turn on my computer in the morning

 

[Dedel66]

This is the fixed channel config:

I chose these settings because my S23 Ultra wasn't triggering the 160MHz:

Maybe you can try that?

 

[GSpock]

After upgrade of my RT-AX86U (with 2 AX56U Mesh), syslog gets flowded with these messages every seconds:

Aug 23 08:34:21 acsd: acs_init_run(1111): acs_start eth7 cannot select chanspec with the wrong info
Aug 23 08:34:24 acsd: eth7: Selecting 5g band ACS policy

 

[Jumpstarter]

After upgrade of my RT-AX86U (with 2 AX56U Mesh), syslog gets flowded with these messages every seconds:

Aug 23 08:34:21 acsd: acs_init_run(1111): acs_start eth7 cannot select chanspec with the wrong info
Aug 23 08:34:24 acsd: eth7: Selecting 5g band ACS policy

I noticed the same thing. Never seen these messages in the log before today.