Release Asuswrt-Merlin 3006.102.5 is now available

[Howard_inGA]

Has been working now for over 10 days without the slightest hiccup:

View attachment 67360

GREAT WORK @RMerlin !

Ditto!!!

 

[Ripshod]

Has been working now for over 10 days without the slightest hiccup:

View attachment 67360

GREAT WORK @RMerlin !

+1

And fantastic results for the wifi too (I know, it's the broadcom drivers).

 

[dineshgyl]

Has the format of files changed in latest 3006-102-5 when compared to 3004.388.8_4

I am on RT-AX86U Pro

custom_clientlist
dhcp_staticlist
qos_rulelist


Also what does file nc_setting_conf used for?

I am planning to upgrade from 3004.388.8_4 to 3006-102-5, so i just first factory reset via GUI then load the new firmware and configure all setting from scratch? Anything else I should be concerned of?

 

[RMerlin]

custom_clientlist
dhcp_staticlist
qos_rulelist

I don't know as I don't pay attention to it. If Asus did any change, they are generally forward-compatible. When they aren't, they get converted on the first boot, in code located in rc/format.c.

Also what does file nc_setting_conf used for?

Notification Center. That's an internal service that Asus uses with their mobile application, possibly with other services.

I am planning to upgrade from 3004.388.8_4 to 3006-102-5, so i just first factory reset via GUI then load the new firmware and configure all setting from scratch? Anything else I should be concerned of?

The factory default reset must be done after the upgrade, not before. You want any new default settings to be from the new firmware.

 

[dineshgyl]

This does not work in new version?

nvram set led_disable=1
service restart_leds


I dont see led's getting disabled. Any alternative way to enable/disable via command line?

 

[Pir8pete]

@Marlin

Whats the reason for this coming up over and over in the logs:

Aug 15 18:36:12 WATCHDOG: [NOTI_NEW_FW_AVAIL][noti_new_fw_available:(8818)]fw_version report is not exist.
Aug 15 18:36:12 WATCHDOG: [NOTI_NEW_FW_AVAIL][noti_new_fw_available:(8836)]final_fw_ver_obj = [null]
Aug 15 18:36:12 WATCHDOG: [NOTI_NEW_FW_AVAIL][noti_new_fw_available:(8952)]No need to send new fw event
Aug 15 18:36:42 WATCHDOG: [NOTI_NEW_FW_AVAIL][noti_new_fw_available:(8818)]fw_version report is not exist.
Aug 15 18:36:42 WATCHDOG: [NOTI_NEW_FW_AVAIL][noti_new_fw_available:(8836)]final_fw_ver_obj = [null]
Aug 15 18:36:42 WATCHDOG: [NOTI_NEW_FW_AVAIL][noti_new_fw_available:(8952)]No need to send new fw event

Never had this come up in any of the other releases, and I haven't changed nothing.


Scheduled check for new firmware availability: set to NO

 

[RMerlin]

This does not work in new version?

nvram set led_disable=1
service restart_leds


I dont see led's getting disabled. Any alternative way to enable/disable via command line?

No. The old Merlin-specific LED handling has been removed, and replaced with the Asus LED handling, to avoid duplicate code, and also ensure compatibility with AiMesh LED control.

@Marlin

Whats the reason for this coming up over and over in the logs:

Aug 15 18:36:12 WATCHDOG: [NOTI_NEW_FW_AVAIL][noti_new_fw_available:(8818)]fw_version report is not exist.
Aug 15 18:36:12 WATCHDOG: [NOTI_NEW_FW_AVAIL][noti_new_fw_available:(8836)]final_fw_ver_obj = [null]
Aug 15 18:36:12 WATCHDOG: [NOTI_NEW_FW_AVAIL][noti_new_fw_available:(8952)]No need to send new fw event
Aug 15 18:36:42 WATCHDOG: [NOTI_NEW_FW_AVAIL][noti_new_fw_available:(8818)]fw_version report is not exist.
Aug 15 18:36:42 WATCHDOG: [NOTI_NEW_FW_AVAIL][noti_new_fw_available:(8836)]final_fw_ver_obj = [null]
Aug 15 18:36:42 WATCHDOG: [NOTI_NEW_FW_AVAIL][noti_new_fw_available:(8952)]No need to send new fw event

Never had this come up in any of the other releases, and I haven't changed nothing.


Scheduled check for new firmware availability: set to NO

That notification isn't about the firmware having checked for a new firmware, it's about whether it should notify you (through the mobile app I suppose) if there is one.

If it does repeat itself every 30 seconds then it's probably because it requires a version check to have happened at least once. That might be a side-effect of now allowing new firmware checks to be completely disabled, in which case the only solution for now is to manually run one check, and see if it satisfies the notification task.

 

[Theraser]

Didn't notice before, but you're right, they are missing. May be they realized it didn't work anyway

You were right in the new 3.0.0.6.102_38961 firmware it was removed the options.

 

[perka.home]

All good here. One little thing is my wireless Canon printer doesn't show it's name in the wireless log. It does show up everywhere else including arp -a. The printer is up to date with the latest drivers so not sure if it's a Canon thing or not but it's not a big deal as everything works just fine.

Same problem here.
None of my devices names show up under "System Log - Wireless Log"
Only MAC addresses are displayed
Tried deleting the cache for the webpage, tried a different browser, tried factory defaults and setting up the router from scratch.
None worked.

 

[dave14305]

setting up the router from scratch

That’s a limitation of AP mode. The name info is usually on the router, not an AP.

 

[bluepoint]

That’s a limitation of AP mode. The name info is usually on the router, not an AP.

In addition to @dave14305, if the clients MAC are set to private most clients nowadays, it'll will not show the names, hence private. Maybe if you set a static IP for all real MAC's of each Client then it would.

 

[Bhoot®]

Hey. Running 102.5 on AXE16000. Every time I connect any SSD to USB 2.0 port the aimesh wireless backhaul drops dramatically in speed and 1x node complete goes offline. Rebooting all the routers does not help. Not using any QOS, no SD VLANs. Disconnect USB drive & it all comes back to normal. Checked both SSDs - both of them are fine, no errors, etc. Any ideas?

 

[RMerlin]

Hey. Running 102.5 on AXE16000. Every time I connect any SSD to USB 2.0 port the aimesh wireless backhaul drops dramatically in speed and 1x node complete goes offline. Rebooting all the routers does not help. Not using any QOS, no SD VLANs. Disconnect USB drive & it all comes back to normal. Checked both SSDs - both of them are fine, no errors, etc. Any ideas?

Try a longer or better shielded USB cable.

 

[agfac]

Hi,

What's the reason for this coming up in the logs (RT-BE88U running 3006.102.5)?

Aug 19 11:58:52 RT-BE88U-37A0 networkmap: Error locking /var/lock//usr/networkmap/nmp_conv_type.js.lock: 2 No such file or directory
Aug 19 11:58:52 RT-BE88U-37A0 networkmap: Error unlocking -1: 9 Bad file descriptor
Aug 19 11:58:52 RT-BE88U-37A0 networkmap: Error locking /var/lock//usr/networkmap/nmp_vendor_type.js.lock: 2 No such file or directory
Aug 19 11:58:52 RT-BE88U-37A0 networkmap: Error unlocking -1: 9 Bad file descriptor
Aug 19 11:58:52 RT-BE88U-37A0 networkmap: Error locking /var/lock//usr/networkmap/nmp_bwdpi_type.js.lock: 2 No such file or directory
Aug 19 11:58:52 RT-BE88U-37A0 networkmap: Error unlocking -1: 9 Bad file descriptor
Aug 19 11:58:52 RT-BE88U-37A0 networkmap: start scan...

 

[ColinTaylor]

Hi,

What's the reason for this coming up in the logs (RT-BE88U running 3006.102.5)?

Aug 19 11:58:52 RT-BE88U-37A0 networkmap: Error locking /var/lock//usr/networkmap/nmp_conv_type.js.lock: 2 No such file or directory
Aug 19 11:58:52 RT-BE88U-37A0 networkmap: Error unlocking -1: 9 Bad file descriptor
Aug 19 11:58:52 RT-BE88U-37A0 networkmap: Error locking /var/lock//usr/networkmap/nmp_vendor_type.js.lock: 2 No such file or directory
Aug 19 11:58:52 RT-BE88U-37A0 networkmap: Error unlocking -1: 9 Bad file descriptor
Aug 19 11:58:52 RT-BE88U-37A0 networkmap: Error locking /var/lock//usr/networkmap/nmp_bwdpi_type.js.lock: 2 No such file or directory
Aug 19 11:58:52 RT-BE88U-37A0 networkmap: Error unlocking -1: 9 Bad file descriptor
Aug 19 11:58:52 RT-BE88U-37A0 networkmap: start scan...

It means the networkmap process was restarted. That can happen for all sorts of reasons, usually because some change was made to the router's configuration.

 

[TnF]

There is something seriously wrong with this FW and WLAN on my RT-BE92U.

In regards to my previous post, i've done numerous tests with different combinations of "Wifi7 mode" disabled, making sure "MLO" in wireless settings and "MLO overhaul for clients" are disabled, changed security authentication methods, re-creating the network from scratch, making sure to reboot the device, etc and more.

The main problem is that the 2.4Ghz network keeps disappearing even though the router looks to raise no alarm. I've posted a syslog in my other post.
For the first 5-10mins it will keep appearing and disappearing every like 1-2mins then it completely disappears and doesn't come back.

Scanning the SSIDs with fresh bootup and all other wireless devices in home turned off i came up with this list:

SSID BSSID Desc

2.4Ghz:
631EFC6379BD241585FE80187C66EDAD XX:SS:SS:SS:SS:44 bootup only
ASUS XX:SS:SS:SS:SS:41 appears and disappears
HIDDEN YY:SS:SS:SS:SS:40 appears and disappears

5Ghz:
HIDDEN YY:SS:SS:SS:SS:44 active
ASUS_5G ZZ:SS:SS:SS:SS:45 active

6Ghz:
ASUS_6G YY:SS:SS:SS:SS:49 active

Also i've noticed the MACs don't correspond to
10:C3:7B:**:**:** "ASUSTek COMPUTER INC."
like on my old RT-AC68U

Still there is some weird pattern matching while the middle octets match between all BSSIDs.

This smells something broken with Wifi7/MLO/Mesh probably. Now i will downgrade just so i stop thinking i am crazy.

EDIT: Downgraded to 3006.102.4, still the exact same issue. I don't remember if it was working properly in that version though either, so it could be caused by something else (Although a downgrade might have messed up with parameters). Not sure how to proceed now. Is there some deeper logging i can do? Could it be a hardware issue?

EDIT2: AFTER SPENDING 2 HOURS CHANGING DELETING NETWORKS, CHANGING SETTINGS, ETC I FOUND THE ISSUE. SETTING A FIXED 2.4GHZ CONTROL CHANNEL BREAKS THE NETWORK. Channel bandwidth setting does not affect it.
I have 2 other routers at home with same SSIDs so devices can be roaming, i normally set manual channels per device so that there is no overlapping. For whatever reason on this device it's a problem.

 

[Pir8pete]

That notification isn't about the firmware having checked for a new firmware, it's about whether it should notify you (through the mobile app I suppose) if there is one.

If it does repeat itself every 30 seconds then it's probably because it requires a version check to have happened at least once. That might be a side-effect of now allowing new firmware checks to be completely disabled, in which case the only solution for now is to manually run one check, and see if it satisfies the notification task.

I don't use or ever used the mobile app. Crazy that Asus requires people to install their app on the phone just to get rid of this log message. bumbaclarts

Aug 16 18:36:12 WATCHDOG: [NOTI_NEW_FW_AVAIL][noti_new_fw_available:(8818)]fw_version report is not exist.
Aug 16 18:36:12 WATCHDOG: [NOTI_NEW_FW_AVAIL][noti_new_fw_available:(8836)]final_fw_ver_obj = [null]
Aug 16 18:36:12 WATCHDOG: [NOTI_NEW_FW_AVAIL][noti_new_fw_available:(8952)]No need to send new fw event
Aug 16 18:36:42 WATCHDOG: [NOTI_NEW_FW_AVAIL][noti_new_fw_available:(8818)]fw_version report is not exist.
Aug 16 18:36:42 WATCHDOG: [NOTI_NEW_FW_AVAIL][noti_new_fw_available:(8836)]final_fw_ver_obj = [null]
Aug 16 18:36:42 WATCHDOG: [NOTI_NEW_FW_AVAIL][noti_new_fw_available:(8952)]No need to send new fw event

Aug 17 18:36:12 WATCHDOG: [NOTI_NEW_FW_AVAIL][noti_new_fw_available:(8818)]fw_version report is not exist.
Aug 17 18:36:12 WATCHDOG: [NOTI_NEW_FW_AVAIL][noti_new_fw_available:(8836)]final_fw_ver_obj = [null]
Aug 17 18:36:12 WATCHDOG: [NOTI_NEW_FW_AVAIL][noti_new_fw_available:(8952)]No need to send new fw event
Aug 17 18:36:42 WATCHDOG: [NOTI_NEW_FW_AVAIL][noti_new_fw_available:(8818)]fw_version report is not exist.
Aug 17 18:36:42 WATCHDOG: [NOTI_NEW_FW_AVAIL][noti_new_fw_available:(8836)]final_fw_ver_obj = [null]
Aug 17 18:36:42 WATCHDOG: [NOTI_NEW_FW_AVAIL][noti_new_fw_available:(8952)]No need to send new fw event

Aug 18 18:36:12 WATCHDOG: [NOTI_NEW_FW_AVAIL][noti_new_fw_available:(8818)]fw_version report is not exist.
Aug 18 18:36:12 WATCHDOG: [NOTI_NEW_FW_AVAIL][noti_new_fw_available:(8836)]final_fw_ver_obj = [null]
Aug 18 18:36:12 WATCHDOG: [NOTI_NEW_FW_AVAIL][noti_new_fw_available:(8952)]No need to send new fw event
Aug 18 18:36:34 kernel: SBF: dhd0: INIT [a2:b4:b5:63:c6:4e] ID 65535 BFW 65535 THRSH 2048
Aug 18 18:36:42 WATCHDOG: [NOTI_NEW_FW_AVAIL][noti_new_fw_available:(8818)]fw_version report is not exist.
Aug 18 18:36:42 WATCHDOG: [NOTI_NEW_FW_AVAIL][noti_new_fw_available:(8836)]final_fw_ver_obj = [null]
Aug 18 18:36:42 WATCHDOG: [NOTI_NEW_FW_AVAIL][noti_new_fw_available:(8952)]No need to send new fw event

 

[RMerlin]

Crazy that Asus requires people to install their app on the phone just to get rid of this log message.

That`s not what I wrote.

The notifications are for pushing to the phone. The issue here is the fact that Asuswrt-Merlin has an option to disable firmware checks, something that the stock firmware doesn`t have. The notification push doesn't expect that, hence the constant flow of notifications.

The workaround is to re-enable new firmware checks. That is done on the webui.

 

[dave14305]

The workaround is to re-enable new firmware checks

FWIW, I have the firmware checks disabled and I don’t see these messages on the the AX88U Pro. Not sure what device @Pir8pete uses.

 

[Dedel66]

@dave14305
Same here...