What's new

Beta Asuswrt-Merlin 3004.388.4 beta is now available

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

Status
Not open for further replies.
Besides a continuous every 30-seconds log spamming about mastiff, everything's smooth.
I know it's closed source and out of your control, but what is mastiff?

Code:
Aug  5 03:24:45 GT-AX6000 rc_service: watchdog 2848:notify_rc stop_aae
Aug  5 03:24:45 GT-AX6000 rc_service: watchdog 2848:notify_rc start_mastiff
Aug  5 03:24:45 GT-AX6000 rc_service: waitting "stop_aae" via watchdog ...
Aug  5 03:24:45 GT-AX6000 custom_script: Running /jffs/scripts/service-event (args: stop aae)
Aug  5 03:24:45 GT-AX6000 custom_script: Running /jffs/scripts/service-event-end (args: stop aae)
Aug  5 03:24:46 GT-AX6000 custom_script: Running /jffs/scripts/service-event (args: start mastiff)
Aug  5 03:24:46 GT-AX6000 custom_script: Running /jffs/scripts/service-event-end (args: start mastiff)
Aug  5 03:24:46 GT-AX6000 Mastiff: init
Me too, trying to search what this is all about.

The difficult part is all my logs are sent to a log Server. The log server is generating me emails saying that this is a critical error. So rather annoying.
 
Probably not related to this beta, but I've had a bit of a fight to keep my Brother HL-2350DW wireless printer connected to my 2.4Ghz network. It will eventually just keep disconnecting/reconnecting and you can't print to it. I think I've figured it out though - disabled 'deep sleep' mode on the printer and set a static IP, seems to be working so far.
Definitely was not related to this beta, disabling Deep Sleep mode on my printer has well and truly fixed the issue. :)

Going out of town until next Thursday, I'm sure beta 3 (or maybe the full release?) will be available by then.

Thanks again for all your hard work @RMerlin!!!!
 
Suggestion:

Can item that use a graph, like temperature, can we store the last 60 results?

That would immediately show some values when looking at the graph, instead of waiting for it to populate.

I understand then, this would be a routing running in the background then.
 
Did 388.2.2 have a memory leak?

The reason why I ask is now I’ve upgraded to 388.4.beta, and the memory utilization is staying at 69%.

Before it kept creeping up to the point it was 98%, and then the DHCP server would stop working

On at rt-ac88u pro

So 17 hours now in, and so far everything’s pretty stable.
 

Attachments

  • IMG_2076.jpeg
    IMG_2076.jpeg
    80 KB · Views: 66
Hi all,

Been a lurker for a while and loving the Asus WRT merlin work, been using it for a while on my GT-AX6000

But for me Im getting packet loss when using 3004.388. 4 Beta 2. I did a factory reset after installing and also tried dirty flash from offical 3.0.0.6.102_21514 to 3004.388. 4 Beta 2 still happening.

My connection is
Fibre > PPoE 900 mbps DL 900mbps UL
MTU set to 1492 everything else set to default

when gaming its laggy as hell on the 3004.388. 4 Beta 2 here is a pingtest to 1.1.1.1 100 times
enlarged.png



for comparision here is the offical 3.0.0.6.102_21514 ran exactly 10 mins later

enlarged 2.png


Any suggestions I much prefer to run Merlins build but unable to at the moment


Kind Regards

Sal
 
Last edited:
In latest beta, from time to time I get a lot of router reboots. Looking at the logs, this is the latest record before each reboot.

Aug 13 16:08:19 crond[2325]: time disparity of 2773922 minutes detected

Anybody has idea what that means?
 
In latest beta, from time to time I get a lot of router reboots. Looking at the logs, this is the latest record before each reboot.
Aug 13 16:08:19 crond[2325]: time disparity of 2773922 minutes detected
This is the reboot FINISHED message, saying that the time server (NTP) got the actual time - you need to post the log BEFORE reboot to find the reason.
The reboot starts with:
May 5 07:05:03 kernel: CPU: AArch64 Processor [420f1000] revision 0
May 5 07:05:03 kernel: init_timers: timer_function_timeout virt addr 0xffffffc000729788
So we need to know what happens before that.
You can easily copy the log entries from the web interface by Ctrl-A and Ctrl-C and paste into notepad to find the meaningful log lines before the reboot.
 
Hi all,

Been a lurker for a while and loving the Asus WRT merlin work, been using it for a while on my GT-AX6000

But for me Im getting packet loss when using 3004.388. 4 Beta 2. I did a factory reset after installing and also tried dirty flash from offical 3.0.0.6.102_21514 to 3004.388. 4 Beta 2 still happening.

My connection is
Fibre > PPoE 900 mbps DL 900mbps UL
MTU set to 1492 everything else set to default

when gaming its laggy as hell on the 3004.388. 4 Beta 2 here is a pingtest to 1.1.1.1 100 times

View attachment 52322

for comparision here is the offical 3.0.0.6.102_21514 ran exactly 10 mins later

View attachment 52323

Any suggestions I much prefer to run Merlins build but unable to at the moment


Kind Regards

Sal
These screenshots are too small to read.
 
on official 3.0.0.4.388_23285 on my gt-ax6000, I can dirty flash to this rmerlin beta (the non-rog version)?

..also do you guys stay on betas when you have achieved stability and good results, or you just ride the beta train through and final releases? curious.

3.0.0.6 official final was a bit buggy so I rolled it back and did a factory fresh start but always been curious about RMerlin

going 17 days strong on 3.0.0.4 official so far

thx
 
mesh.png


since 3004.x.x firmware the aimesh is a little to week, earlier firmware 388.x has a better connection/signal.
anyone noticed this too ?
i know that this is out of the range from rmerlin as it is closed source, but maybe asus has an eye on this.
 
Currently, I guess it is known thing- ASUS app cannot connect remotely, unless VPN is connected.
Shows Security Link status.
Not sure why is it.
Under VPN it works like a charm
 

Attachments

  • Screenshot_20230814_092508_ASUS Router.jpg
    Screenshot_20230814_092508_ASUS Router.jpg
    45.4 KB · Views: 53
on official 3.0.0.4.388_23285 on my gt-ax6000, I can dirty flash to this rmerlin beta (the non-rog version)?

..also do you guys stay on betas when you have achieved stability and good results, or you just ride the beta train through and final releases? curious.

3.0.0.6 official final was a bit buggy so I rolled it back and did a factory fresh start but always been curious about RMerlin

going 17 days strong on 3.0.0.4 official so far

thx
Since you would be switching from the ASUS firmware to RMerlin for the first time I would suggest that you do it with the latest stable final version (388.2_2) instead in case of unexpected issues that might be purely related to the latest beta version for this router.

We (the adventurous/fearless ones) usually ride the alpha/beta train through and final releases.

Make sure to make plenty of screenshots (personalized settings) on your stock firmware before making the jump...
 
A few easy questions for you:

Based on what Merlin said and I quote, "Asuswrt-Merlin 3004.388.4 beta is now available. Note that starting with this release, the version numbering scheme was changed to better illustrate that this is based on the 3.0.0.4 code (versus 3.0.0.6 that would be 3006.102.x).", is the Merlin build going to remain with the 3.0.0.4 firmware or will it be moving to the 3.0.0.6 version at some stage and if the answer is yes, would I be right in thinking that to swap to the 3.0.0.6 build would require a complete reset after flashing with the new firmware, just as moving from the official 3.0.0.6 firmware (which I am currently using) is highly-recommended at the moment? Also, if Merlin does move to 3.0.0.6 firmware, would that make swapping between the official 3.0.0.6 firmware and Merlin 3.0.0.6 firmware less likely to need a full reset?
 
Switching to/back from any major firmware versions a full reset is most likely required for stable and reliable router/network operation.

As is switching between stock Asus and RMerlin builds (even if they're on the same nominal 3.0.0.X builds).

Nothing changes this fact.

Will some be able to switch without a full reset? Of course.

How lucky do you feel?

How important is a stable/reliable network to you?

It is far more straightforward to do a full and proper reset than to try bungling through an unstable router trying to diagnose and fix what is wrong. When that avenue fails, a full reset is required/recommended here in the end anyways.

Save yourself a few days or weeks of that and just get the router/network to a good/known place immediately and if any troubleshooting is required, it won't be a wild goose chase of unknown interactions between internal variables of different firmware and the defaults they are expecting to see/work with (not to mention the almost unlimited additional variables of how one may have their router/network set up for their environment too).

I don't understand why some think a full reset is such a chore. 15 minutes buys you sanity.

And if you have a network that requires hours of setting up to work as you want? Maybe your expectations, workflows and choice of hardware need to be questioned and brought in line with the capabilities of the Asus hardware we have (today).
 
Status
Not open for further replies.

Similar threads

Latest threads

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top