What's new

Release Asuswrt-Merlin 3004.388.6 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!

Hello @RMerlin

Well, there's always instability on the latest version. I was logged in as administrator on the router and was suddenly ejected/disconnected. Here are the errors in the logs (AX88U)
Mar 1 15:12:41 kernel: potentially unexpected fatal signal 11.
Mar 1 15:12:41 kernel: CPU: 3 PID: 1185 Comm: httpds Tainted: P O 4.1.51 #2
Mar 1 15:12:41 kernel: Hardware name: Broadcom-v8A (DT)
Mar 1 15:12:41 kernel: task: ffffffc032b2f500 ti: ffffffc02dd1c000 task.ti: ffffffc02dd1c000
Mar 1 15:12:41 kernel: PC is at 0xf6b81b10
Mar 1 15:12:41 kernel: LR is at 0xf6b85068
Mar 1 15:12:41 kernel: pc : [<00000000f6b81b10>] lr : [<00000000f6b85068>] pstate: 20000010
Mar 1 15:12:41 kernel: sp : 00000000ffb7eac8
Mar 1 15:12:41 kernel: x12: 0000000000000001
Mar 1 15:12:41 kernel: x11: 00000000000a23a3 x10: 00000000000a6a23
Mar 1 15:12:41 kernel: x9 : 00000000002947f8 x8 : 00000000000a4e4e
Mar 1 15:12:41 kernel: x7 : 00000000002e98c8 x6 : 00000000f6b85baa
Mar 1 15:12:41 kernel: x5 : 00000000002e2ca8 x4 : 00000000002f7108
Mar 1 15:12:41 kernel: x3 : 00000000fffffffe x2 : 00000000f6922800
Mar 1 15:12:41 kernel: x1 : 0000000000000000 x0 : 00000000002f7108
Mar 1 15:12:59 watchdog: start httpd
Mar 1 15:12:59 rc_service: watchdog 1194:notify_rc start_httpd
Mar 1 15:12:59 RT-AX88U: start https:****
Mar 1 15:12:59 RT-AX88U: start httpd:80
Mar 1 15:12:59 httpd: Succeed to init SSL certificate...****
Do you know what that means ? I've never experienced this kind of mistake before. If it could be solved, that would be great.
 
Do you know what that means ? I've never experienced this kind of mistake before. If it could be solved, that would be great.
The web server crashed, but it's impossible to tell from that what caused it to crash. What page were you on?
 
The web server crashed, but it's impossible to tell from that what caused it to crash. What page were you on?
Thanks for your quick reply. Just when the web server went down, I was exactly here :

I wanted to change the name and image of my device.

Do you think this problem can be solved in a future version ?

1709306981799.png
 
Last edited:
Thanks for your quick reply. Just when the web server went down, I was exactly here :

I wanted to change the name and image of my device.

Do you think this problem can be solved in a future version ?
Did you maybe try to upload some unsupported image format/size?
Works for me just fine...

Or try to do it from the LAN-DHCP Server page, if it acts the same.
 

Attachments

  • Screenshot 2024-03-01 170737.png
    Screenshot 2024-03-01 170737.png
    101 KB · Views: 22
Do you think this problem can be solved in a future version ?
I don't know. I would first need to be able to reproduce the problem, and so far I can't.
 
Did you maybe try to upload some unsupported image format/size?
Works for me just fine...

Or try to do it from the LAN-DHCP Server page, if it acts the same.
Each time, I chose only the original images supplied in the firmware.

And I've always changed the images in the "network map" tab on the home page, as my screenshot shows..

One thing's for sure, there's a problem. I've never had this problem with Merlin firmware. Which also explains why my customer list crashed the other day.
Double bug since installation of version 3004.388.6_2.

The logs speak for themselves.

I hope this problem will be corrected soon.
 
Each time, I chose only the original images supplied in the firmware.

And I've always changed the images in the "network map" tab on the home page, as my screenshot shows..

One thing's for sure, there's a problem. I've never had this problem with Merlin firmware. Which also explains why my customer list crashed the other day.
Double bug since installation of version 3004.388.6_2.

The logs speak for themselves.

I hope this problem will be corrected soon.
Did you also maybe try to use some French accented letters??
I once accidentally wrote a name in Cyrillic letters - he did not like that! 😄
 
Did you also maybe try to use some French accented letters??
I once accidentally wrote a name in Cyrillic letters - he did not like that! 😄
😆
Absolutely not, never an accent or a strange character.
 
On my home GT-AX6000 the same thing happen with (3004.388.6_2 nand), some wireless clients (android phones on the guest network) couldn't obtain IP address, some other clients were connected (PC laptops on the main network) but with no internet access.

I have double flash , reboot, disabling and re enabling Wi-Fi and guest network and didn't solve the issue.
Then I saw the posts that are saying that diversion is causing dnsmask to crash, so I disable diversion but the problem remains.

I had no other choice so I rolled back to (3004.388.6_0 nand) and everything is working normal again.

The fanny thing is that on my office RT-AX88U that has the same settings and add-ons none of the above is happening, everything seams to work fine for two days now.

Any way I will wait for a fix / solution for the problem 3004.388.6_0 is working fine, my only concerns are the CVE 2023-50868 and CVE 2023-50387 that the update resolves.
 
Then I saw the posts that are saying that diversion is causing dnsmask to crash, so I disable diversion but the problem remains.
The syslog should tell you why dnsmasq fails to start. Save the log on your next upgrade attempt. In the meantime, check for any dnsmasq.conf.add or dnsmasq.postconf files that maybe in conflict with the newer version (e.g. dns-forward-max).
 
On my home GT-AX6000 the same thing happen with (3004.388.6_2 nand), some wireless clients (android phones on the guest network) couldn't obtain IP address, some other clients were connected (PC laptops on the main network) but with no internet access.

I have double flash , reboot, disabling and re enabling Wi-Fi and guest network and didn't solve the issue.
Then I saw the posts that are saying that diversion is causing dnsmask to crash, so I disable diversion but the problem remains.

I had no other choice so I rolled back to (3004.388.6_0 nand) and everything is working normal again.

The fanny thing is that on my office RT-AX88U that has the same settings and add-ons none of the above is happening, everything seams to work fine for two days now.

Any way I will wait for a fix / solution for the problem 3004.388.6_0 is working fine, my only concerns are the CVE 2023-50868 and CVE 2023-50387 that the update resolves.
A lot of instability on this latest version...
So I'm wondering whether it wouldn't be better to go back to version 388.5 or even 388.4 while waiting for a fix.
Previously, version 388.4 ran for over 170 days without a single crash. With version 388.6_2 : 3 hours and even 20 hours later, I started having bugs as indicated earlier in this thread.

You're back to 388.6, but isn't there a dnsmask problem with this version ?
 
Last edited:

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