Release Asuswrt-Merlin 3004.388.10 is now available

[dbell]

A new stock firmware was posted yesterday:

 

[ColinTaylor]

A new stock firmware was posted yesterday:
View attachment 68490

And how is that relevant to this thread?

 

[dbell]

And how is that relevant to this thread?

Well we're talking about instability in Merlin FW 10_0, and he just determined it is in closed source, but Asus clearly recognized an issue given the first two comments in the release notes and it's only 6 wks after their last release which have been coming out in at least several months increments recently. That is all evidence that what we are experiencing is not limited to mobile app, or HA integrations, but rather is a FW problem itself.

So folks have a choice to stick with 9_2, or try the new stock firmware instead and see if it resolves the issues, or limp along with 10_0 until another Merlin update can roll in a suitable GPL.

Is that relevant enough for you ?

 

[ColinTaylor]

Is that relevant enough for you ?

Then you could have just said "try the stock firmware" rather than posting the changelog for one specific model without explanation.

 

[dbell]

Then you could have just said "try the stock firmware" rather than posting the changelog for one specific model without explanation.

Ah ok got it - you just didn't like the way I communicated that Asus published a very recent firmware update that specifically targets stability problems.

"Try the stock firmware" has even less context and relevance, but I'll bear your advice in mind for the future.

 

[Clark Griswald]

Could you please clarify your concern here, as to divergence from the topic?

With all due respect, if this particular FW causes an issue with any system that integrates, communicates or interconnects with it, whether that be internal or external to the Routers “OS” for want of better terminology, then surely by definition it is on topic? That it happens to be HA in this instance is irrelevant.

Granted, commenting on the pros and cons of HA or its integrations is a divergence; but in my case above I was suggesting an interim solution for those who wanted to use the new FW and avoid the issues associated with HA that came with it, not to extol the virtues of HA itself. I do not think this unreasonable, in this particular instance, but I am open to hearing your concern.

Please state issues that directly effect RMerlin's FW and HA with any additional help (logs, screen shots, etc) in addressing the issue. Since HA is not part of Asus nor RMerlin FW I suggested you possibly open your issue in asuswrt-merlin addons Many of these technical threads get lengthy and finding solutions is difficult. Thus your questions and solutions could be easily found and addressed, instead of currently buried on page #10.
Or just run HA on a RPi and let the router do what it was designed.

 

[jksmurf]

Please state issues that directly effect RMerlin's FW and HA with any additional help (logs, screen shots, etc) in addressing the issue

I do not personally have these issues but feel free to check this thread for folks describing their issues with HA as a direct result of this FW, along with Merlin’s conclusion that the problem rests with Asus closed source part of the FW and is not something he can address. If you refer HA posters to that conclusion rather than requesting they totally desist from posting about HA issues related to this firmware, that would be a positive addition, in my view.

Clearly there are e.g. here folks that have issues with the WebGUI (e.g.) on this firmware when used with a HA integration; issues that they did not experience with the previous FW revision.

I do not think it outwith the bounds of reason for them to raise that here.

Or just run HA on a RPi and let the router do what it was designed

Your recommendation that they simply run HA on a RPi suggests somewhat of a misunderstanding of the issue, as regardless of the device HA is run on, if the HA Integration refers to the router in the network, the one with this FW on it, the issue will still arise.

Ultimately I appreciate your concerns regarding posts diverging from the FW posted and I also find this detracts from nailing down collective, repeatable issues with the FW, but in this instance, sir, I think the HA issues are and remain, relevant.

 

[aex.perez]

Confused

Had lots of headaches with 3004.388.10, reverting back to beta1 to stabilize with just about every service failing and restarting. Then having to get on the develop track of the scribe add it to get logging and have my custom filters working again. Even had the Node not passing traffic with BACKUPMON failing to find the NAS, couldn't even ping the Router via SSH on the Nodes, though they could still be managed via the Router through the GUI, a reboot of each fixed that. Still with all that I was was not able to use the App, let alone the App and the GUI simultaneously and didn't risk even trying.

Then last night, after a few days of stability, I took a the risk. Downloaded the App on the iPhone and set it up and it was able to connect, login and actually report on active connections on the Router and on each Node

So, file under no risk no reward, took the next step. Tried this morning, being in the GUI and using the App at the same time. Before it wouldn't work and it would cause a cascade of failures with Router processes, firewall, logging, ACS, channel changes amongst others.

But this morning, both were working like they did under 3004.388.9.2 with the Router and Nodes remaining stable, though the log entries are different now.

Oct 21 08:43:43 Router HTTPD: [LOGIN][http][Web] success (192.168.1.99)
Oct 21 08:45:45 Router HTTPD: [LOGIN][https][APP] success (192.168.1.172)

Continues to work Not sure how or why but I'll take the WIN!

Well it mostly all works now.

Have a scheduled job that does not appear to run, or more acurately actually does not do what its supposed to do when it's scheduled to do it. But works fine from the command line (and did under 9.2), and does run at it's scheduled time
The schedule:
0 4 * * * /bin/sh /jffs/scripts/clearcache.sh #ClearCache#

The script:
#!/bin/bash
echo 3 > /proc/sys/vm/drop_caches && logger 'Ram-cache and Swap Cleared'

As far as the other random issues that that come about from using the APP or with HTTP/HTTPS or start after a few days of running fine. The AX88 Router has been working fine, no errors in the log. Thought since I also run Merlin on the nodes (quite successfully for quite some time) that issue has moved from the Router and onto both AX86 nodes, causing them to crash, though they do restart. As they complan "kernel: CPU: 0 PID: 13273 Comm: httpds Tainted: P O 4.1.52 #2".

At the height of issues with my AX88 with the release of 3004.388.10, with all sorts of scripts and services failing, causing me to roll back to Alpha1 for stability and abandon the APP. Well, just sharing mostly as "the APP so not supported" with Merlin FW, and though I'm only using it for visibility and maybe for a clue into what was/is going on. Though @RMerlin did post on the HTTP service and logging being closed source to clear it up, just adding this for any additional clarity this may provide, if any.

Logs from the nodes and the crash attached.