Release Asuswrt-Merlin 3006.102.4 is now available

[bennor]

Connmon (and the webgui of the scripts on a subpage with it) is displayed incorrectly on the web interface, when I open it, the left menu bar and the header disappear.

One will need to use the "develop" version of certain scripts if they are using the Asus-Merlin 3006.102.x firmware. See the following post (and thread discussion) which lists working and not working scripts on the Asus-Merlin 3006.102.x firmware:
https://www.snbforums.com/threads/c...ons-with-gt-be98-pro.90657/page-7#post-947006

--WORKING--
...
j1 - connmon: Functional on 3006 (with the develop branch)

Edit to add: Per this post, one can update connmon, spdMerlin and ntpMerlin to their respective develop branches by issuing the following commands via SSH:

connmon:

/jffs/scripts/connmon develop
/jffs/scripts/connmon forceupdate

spdMerlin:

/jffs/scripts/spdmerlin develop
/jffs/scripts/spdmerlin forceupdate

ntpMerlin:

/jffs/scripts/ntpmerlin develop
/jffs/scripts/ntpmerlin forceupdate

 

[robinjoo1]

Because you have a GT-AX11000 Pro. The link referenced in the post you quoted appears to indicate a reverted update for the RT-BE96U and GT-BE98 Pro:

Bummer since beta 3 lots of disconnects see how this release goes

 

[zitev]

One will need to use the "develop" version of certain scripts if they are using the Asus-Merlin 3006.102.x firmware. See the following post (and thread discussion) which lists working and not working scripts on the Asus-Merlin 3006.102.x firmware:
https://www.snbforums.com/threads/c...ons-with-gt-be98-pro.90657/page-7#post-947006

Edit to add: Per this post, one can update connmon, spdMerlin and ntpMerlin to their respective develop branches by issuing the following commands via SSH:

connmon:

/jffs/scripts/connmon develop
/jffs/scripts/connmon forceupdate

spdMerlin:

/jffs/scripts/spdmerlin develop
/jffs/scripts/spdmerlin forceupdate

ntpMerlin:

/jffs/scripts/ntpmerlin develop
/jffs/scripts/ntpmerlin forceupdate

Oh, thanks for the quick help. To be honest, this caught me by surprise, I didn't expect that the new firmware would be incompatible with the scripts installed on the official update repo, maybe it would be worth noting this in the changelog. With this method, would it be worth moving all script sources to the develop repo?

 

[ExtremeFiretop]

Oh, thanks for the quick help. To be honest, this caught me by surprise, I didn't expect that the new firmware would be incompatible with the scripts installed on the official update repo, maybe it would be worth noting this in the changelog.

Script add-ons are outside the scope of the firmware, add-ons are handled by their individual authors, some have since left the scene leaving "important" work in their development branches without promoting it to the main branch. If you want to poke anyone about add-ons it should be @thelonelycoder as I expect some day be may have to make a choice what to do with those add-ons.

With this method, would it be worth moving all script sources to the develop repo?

No. Unless there is a reason to be on the development branches such as the add-ons identified. For most authors still around, that is a development space for a reason.

Edit to add: Per this post, one can update connmon, spdMerlin and ntpMerlin to their respective develop branches by issuing the following commands via SSH:

connmon:

/jffs/scripts/connmon develop
/jffs/scripts/connmon forceupdate

spdMerlin:

/jffs/scripts/spdmerlin develop
/jffs/scripts/spdmerlin forceupdate

ntpMerlin:

/jffs/scripts/ntpmerlin develop
/jffs/scripts/ntpmerlin forceupdate

Adding this to the list for completeness:

Post in thread 'Asuswrt-Merlin 3006.102.4 is now available' https://www.snbforums.com/threads/asuswrt-merlin-3006-102-4-is-now-available.94651/post-954769

 

[bennor]

Oh, thanks for the quick help. To be honest, this caught me by surprise, I didn't expect that the new firmware would be incompatible with the scripts installed on the official update repo, maybe it would be worth noting this in the changelog. With this method, would it be worth moving all script sources to the develop repo?

The addon issues with 3006 have been mentioned or discussed quite a bit across a number of earlier topic discussions, including earlier in the current 3006.102.4 release discussion (see yesterday's post), and in Beta 3006 firmware discussions (see this link and this link for example). Developers were warned (see this link) last year that they may need to update their scripts to deal with several changes in the Asus-Merlin 3006 track firmware. And there is mention early on in the 3006 change log (28-Jun-2024) that addon developers may need to make certain changes to their scripts.

Each addon developer, if they're still actively developing their scripts, are the one's who will have to roll in their develop branch changes to their final release version addon script(s). Otherwise for now users will have to manually update to the develop branch for those affected scripts for which a develop branch has been created to deal with the script's incompatibility with 3006.

 

[Mutzli]

Strange behavior on my AiMesh BT10 devices with the final firmware. They suddenly drop all the clients and a few seconds later they are back again. I reverted back to Beta3 with the newer WiFi drivers and everything works again without any issues.

I tried once more to upgrade to the final release and still experience the problem of dropped clients with the older WiFi driver in the final release. The only message I see in the system log is this one which is timed around the disconnect:

May 12 07:41:26 kernel: WLC_SCB_DEAUTHORIZE error (-30)
May 12 07:41:27 kernel: WLC_SCB_DEAUTHENTICATE_FOR_REASON err -30

Going back to the "newer" driver and the disconnects disappear. @RMerlin Since Beta3 resolves the disconnects, are there any known downsides to staying on it long-term? Would it introduce security vulnerabilities or impact performance in other areas?

 

[zitev]

The addon issues with 3006 have been mentioned or discussed quite a bit across a number of earlier topic discussions, including earlier in the current 3006.102.4 release discussion (see yesterday's post), and in Beta 3006 firmware discussions (see this link and this link for example). Developers were warned (see this link) last year that they may need to update their scripts to deal with several changes in the Asus-Merlin 3006 track firmware. And there is mention early on in the 3006 change log (28-Jun-2024) that addon developers may need to make certain changes to their scripts.

Each addon developer, if they're still actively developing their scripts, are the one's who will have to roll in their develop branch changes to their final release version addon script(s). Otherwise for now users will have to manually update to the develop branch for those affected scripts for which a develop branch has been created to deal with the script's incompatibility with 3006.

Unfortunately, I couldn't follow all the forum posts related to this, so a warning in the changelog wouldn't hurt, so that an inexperienced and novice user like me doesn't run into a challenging problem. Now that I've moved the two script sources to the develop repo, the amtm update shows their status in red, so I obviously won't be able to update them. The question is, how can I revert to the original source later?

 

[ExtremeFiretop]

Now that I've moved the two script sources to the develop repo, the amtm update shows their status in red, so I obviously won't be able to update them.

You can manually update them at anytime with:

/jffs/scripts/spdmerlin forceupdate
/jffs/scripts/connmon forceupdate
/jffs/scripts/ntpmerlin forceupdate

The question is, how can I revert to the original source later?

Like this:

/jffs/scripts/spdmerlin stable
/jffs/scripts/connmon stable
/jffs/scripts/ntpmerlin stable

 

[MDM]

Unfortunately, I couldn't follow all the forum posts related to this, so a warning in the changelog wouldn't hurt, so that an inexperienced and novice user like me doesn't run into a challenging problem. Now that I've moved the two script sources to the develop repo, the amtm update shows their status in red, so I obviously won't be able to update them. The question is, how can I revert to the original source later?

Just my 2 cent's, but script and add-ons aren't for inexperienced and novice users...

 

[zitev]

You can manually update them at anytime with:

/jffs/scripts/spdmerlin forceupdate
/jffs/scripts/connmon forceupdate
/jffs/scripts/ntpmerlin forceupdate

Like this:

/jffs/scripts/spdmerlin stable
/jffs/scripts/connmon stable
/jffs/scripts/ntpmerlin stable

I understand everything (I think), thanks again for the help!

 

[zitev]

Just my 2 cent's, but script and add-ons aren't for inexperienced and novice users...

So you were born knowing everything right away?

 

[GHog]

Update to my flashing update available post update. After deciding to sleep on it, all's well this morning. Must have been DOGE

 

[RMerlin]

so a warning in the changelog wouldn't hurt

There was a warning in the initial 3006 release changelog, and the devs were warned weeks ahead of time about it. It's been almost a year now since that initial 3006 release, I'm not going to keep repeating the same warning over and over again in every release. It's their developer's responsibility to either update their addons, warn their users, or have someone in the community warn other users if an addon dev is MIA/retired. I'm not going to personally keep track of 20+ addons myself, sorry.

 

[MDM]

So you were born knowing everything right away?

You didn't get me nor my point, but so be it...

 

[demux]

Thanks RMerlin. I updated my RT-BE88U to the latest version. The update ran smoothly with no issues for the past 24 hours!

Does anyone have insights into why Asus is pushing the can down the road regarding the outdated kernel version: 4.19.294?

 

[RMerlin]

Does anyone have insights into why Asus is pushing the can down the road regarding the outdated kernel version: 4.19.294?

The kernel is picked by Broadcom with their SDK, not by Asus. Kernels never get updated, because then everything else will break. Trend Micro would need to provide new kernel modules, Tuxera would need to provide new NTFS drivers, and so on.

 

[demux]

Okay, thanks. However, to my knowledge, Kernel 4.19 is out of support since December 2024. I understand this will be a hassle for manufacturers with the drivers, but at some point, it will be very difficult to backport security updates to this "dinosaur" kernel.

 

[Rajjco]

Upgraded RT-BE92U from Beta3 and the router just rebooted by itself after running for 2 days. No errors or note worthy logs.
Might have to fork over 700$ for a BE98 Pro.

 

[heysoundude]

Does anyone have insights into why Asus is pushing the can down the road regarding the outdated kernel version: 4.19.294?

If you're after more current kernels, there is other networking hardware available that uses them:
For instance, Mikrotik's RouterOS v7 uses k5.6.3

 

[Howard_inGA]

Just updated within the last hour...so far, all is smooth on the dirty upgrade from B3.