Release Asuswrt-Merlin 3006.102.5 is now available

[VeloxNEx]

I’m running a BE88U on 102.5 release with a BE86U on stock as my wired Aimesh node. I have no issues as you mention above but I’m not running wireless backhaul.

Would be helpful to know which router and node models you are using.

Sorry, it's in my siggy. GT-BE98 Pros.

Also, doesn't seem to work wired either... See awesome scrolling screenshot I just took.

 

[fourty6and2]

Were there any issues reported with aimesh units? main router is perfect, no issues. The mesh unit is basically shutting itself off. reset it a few times. even made itself it's own router and reloaded the firmware. Everytime I add it as a aimesh router it just shuts off and stays offline. I am trying to use it as wireless backhaul. Haven'tr tried wired backhaul yet. About to do that. But I can't "keep it" that way. The old main release was perfect.

No issues on my setup.

Main: BE96u on 3006.102.5
Mesh: AX86u on 3004.388.9

 

[Comoman]

Sorry, it's in my siggy. GT-BE98 Pros.

Also, doesn't seem to work wired either... See awesome scrolling screenshot I just took.

Apologies - sigs don't seem to appear when using Safari on an iPad.

 

[VeloxNEx]

No problem.

Also an update:

If I do the asus firmware (due to the driver issue https://rog.asus.com/us/networking/rog-rapture-gt-be98-pro/helpdesk_bios/ ) it works just fine wireless MLO etc without issue.

 

[jksmurf]

Updated successfully; everything went as smooth as possible overnight.
As always much appreciated @RMerlin

View attachment 67132

Checking the syslogs this morning shows absolutely nothing out of the ordinary. As clean as a can be.

So no "Disconnected" Internet GUI, nothing, clean as a whistle? You have a different router, setup etc to me though. Hmm...

 

[ExtremeFiretop]

So no "Disconnected" Internet GUI, nothing, clean as a whistle? You have a different router, setup etc to me though. Hmm...

No issues here. No disconnect state or anything. All was a perfectly smooth update as all the previous ones for me.

Even my wireless AiMesh node reconnected flawlessly within 4 minutes according to the syslogs on the node when I checked.

but I wonder what causes the difference between FW updates and if a more reliable “back on line” sequence I can control exists, or whether the post FW update restart could be configured (as part of the update) e.g. to enable the various services with small ‘waits’ between them (if that is what might help, just extrapolating wildly here), to result in the same state as pre-update.

I understand your desire to try and control / monitor the boot up process and services post-update, but that's outside of scope for MerlinAU. Remember we are only an add-on and have no intentions of over stepping our roles.

Our job is to safely shut non-critical services down to free RAM, unload any user scripts, remove any cron jobs, eject any USBs, do SHA checks on the firmware, etc *BEFORE* the automatic flash... In short we are preparing the environment for the flash as best as humanly possible.

The state of the router afterwards is outside of scope, if a release firmware has a bug or a service doesn't start we don't want MerlinAU getting involved / in the way or over stepping. It's a rabbit hole I'm not going down.

Once an update is flashed, we limit checks to basic version checks (to validate the firmware actually flashed) and connectivity checks, before sending the final email that it was a success.

 

[Treadler]

No issues here. No disconnect state or anything. All was a perfectly smooth update as all the previous ones for me.

Even my wireless AiMesh node reconnected flawlessly within 4 minutes according to the syslogs on the node when I checked.



I understand your desire to try and control / monitor the boot up process and services post-update, but that's outside of scope for MerlinAU. Remember we are only an add-on and have no intentions of over stepping our roles.

Our job is to safely shut non-critical services down to free RAM, unload any user scripts, remove any cron jobs, eject any USBs, do SHA checks on the firmware, etc *BEFORE* the automatic flash... In short we are preparing the environment for the flash as best as humanly possible.

The state of the router afterwards is outside of scope, if a release firmware has a bug or a service doesn't start we don't want MerlinAU getting involved / in the way or over stepping. It's a rabbit hole I'm not going down.

Once an updated is flashed, we limit checks to basic version checks (to validate the firmware actually flashed) and connectivity checks, before sending the final email that it was a success.

MerlinAU worked fine for me this AM, with upgrade to latest Merlin.

 

[jksmurf]

No issues here. No disconnect state or anything. All was a perfectly smooth update as all the previous ones for me.

Great!

Even my wireless AiMesh node reconnected flawlessly within 4 minutes according to the syslogs on the node when I checked.

Even Greater...

I understand your desire to try and control / monitor the boot up process and services post-update, but that's outside of scope for MerlinAU. Remember we are only an add-on and have no intentions of over stepping our roles.

Never intended it to be read that way and my apologies if it came across as a request to MerlinAU. It was posted in the FW thread for a reason, I was fishing for others who may have had the same issue and if so, whether Merlin could see anything that might help it come back to life with full function post an update, IF there was any possibility to do so. It is a long shot I know, I am an outlier etc (but maybe not the only one). You understand my remote update reliability concern though, hence the tag to you (but not to MerlinAU).

Our job is to safely shut non-critical services down to free RAM, unload any user scripts, remove any cron jobs, eject any USBs, do SHA checks on the firmware, etc *BEFORE* the automatic flash... In short we are preparing the environment for the flash as best as humanly possible.

The state of the router afterwards is outside of scope, if a release firmware has a bug or a service doesn't start we don't want MerlinAU getting involved / in the way or over stepping. It's a rabbit hole I'm not going down.

Understood!

Once an updated is flashed, we limit checks to basic version checks (to validate the firmware actually flashed) and connectivity checks, before sending the final email that it was a success.

Gotcha. It remains a wonderful addon!

 

[TnF]

Dirty update on my RT-BE92U yesterday from 3006.102.4, all working good

 

[DrTurk]

Dirty upgrade on my RT-AX86U Pro from 3006.102.4, no issues so far.

Thanks for all you do RMerlin.

 

[ducky124]

Were there any issues reported with aimesh units? main router is perfect, no issues. The mesh unit is basically shutting itself off. reset it a few times. even made itself it's own router and reloaded the firmware. Everytime I add it as a aimesh router it just shuts off and stays offline. I am trying to use it as wireless backhaul. Haven'tr tried wired backhaul yet. About to do that. But I can't "keep it" that way. The old main release was perfect.

I’ve got two mesh nodes up and running perfectly. In my experience, it helps to start the setup using Ethernet backhaul—just plug them in with a cable first. Once everything’s connected and working, you can switch to wireless. It seems to make the whole AiMesh setup process a lot smoother.

 

[SpasilliumNexus]

Upgraded from 3006.102.4, through MerlinAU for the first time, to see how it works.
Everything seems to be working just as before the upgrade on an RT-BE88U.

 

[routerq]

Dirty update from last official FW to the 3006.102.5, 20h and things are running fine.
Also installed the Router Date Keeper (that 31 Dec dates in logs were bothering me
The RAM usage seems to have gone down by ~75-100Mb.

1Q) how to show the temp in F in the System Info tab?

Also: my temps under noraml load are, which look high to me.
2.4: 47C, 5.0: 51C, CPU: 68C
Thoughts?

Thanks Merlin.

 

[AlbumMan]

Skipped the beta cycle this time and dirty updated from 3006.102.4 -> 102.5 on the RT-AX86U Pro. Did the usual reboot after 30 minutes and everything connected again including the 20 devices on the VLAN IoT. My RT-AX3000 node did not even need rebooting. 24 hours now and all looks good. Great job @RMerlin

After all this time, I just noticed the "Support SNBForums w/ Amazon" section on the right side of the page and used the link for my last purchase.

 

[bennor]

1Q) how to show the temp in F in the System Info tab?

That appears, per a old RMerlin post, to be hard coded.

That setting is stored in a cookie if I remember correctly (it's been years since I've looked at that page). Make sure you aren't blocking cookies.

Also note that this only applies to that page - it does not apply to the Sysinfo page, where I have it hardcoded to Celcius.

PS: And a later reply by RMerlin indicating it's hard coded.

The Sysinfo page is hardcoded to Celcius.

 

[copperhead]

Any idea why I'm getting this text under System Status after the firmware update? Yes, i've always had a proper username and password set for router login.

 

[Ripshod]

Any idea why I'm getting this text under System Status after the firmware update? Yes, i've always had a proper username and password set for router login.


View attachment 67159

Do you have WAN access enabled? Does your password conform to the new requirements?

 

[Blacklistedcard]

Loaded onto BE98Pro. No issues or errors. Running well.

 

[dave14305]

Any idea why I'm getting this text under System Status after the firmware update? Yes, i've always had a proper username and password set for router login.

Seems like a browser cache issue since those texts actually belong to the QIS Quick Internet Setup page.

 

[copperhead]

Do you have WAN access enabled? Does your password conform to the new requirements?

Seems like a browser cache issue since those texts actually belong to the QIS Quick Internet Setup page.

Yes, WAN access is enabled, password has been modified to the new requirements, and both Firefox & Chrome cache (everything) have been cleared (all time) -- also used private mode in both. The problem still remains. I'll check the underlying code to see how it's being triggered.