Release Asuswrt-Merlin 3004.388.4 is now available

[Rhialto]

Normal? Only Diversion running. I mean I know my previous 1900P was short on memory it was a known fact and I thought this very recent model would be ok about memory.

 

[JGrana]

View attachment 53591

Normal? Only Diversion running. I mean I know my previous 1900P was short on memory it was a known fact and I thought this very recent model would be ok about memory.

Your good. Normal.

Help! Linux ate my RAM!

 

[Milan]

View attachment 53591

Normal? Only Diversion running. I mean I know my previous 1900P was short on memory it was a known fact and I thought this very recent model would be ok about memory.

Please remember router firmware is based on linux so memory is managed completely differently as in windows ...

this state is pretty ok.

 

[Milan]

for real mem consumtion use htop:

in my case really used memory is 601M rest are disk buffers ...

 

[ika]

for real mem consumtion use htop:

View attachment 53593

in my case really used memory is 601M rest are disk buffers ...

May I ask what kind of load did you do to make the router swap? Or did you alter swappiness?

 

[RMerlin]

It’s a missing model check in this function. I’m sure Asus will eventually fix it.

It's already fixed in 3006, they probably forgot to backport the fix to 3004.

 

[Weblee2407]

for real mem consumtion use htop:

View attachment 53593

in my case really used memory is 601M rest are disk buffers ...

Nice utility to have installed. I also saw in some discussions (can remember where) there were graphs...any idea how that is accomplished?

 

[Makaveli]

for real mem consumtion use htop:

View attachment 53593

in my case really used memory is 601M rest are disk buffers ...

good point

I forgot about htop being there without a manual install.

 

[visortgw]

Nice utility to have installed. I also saw in some discussions (can remember where) there were graphs...any idea how that is accomplished?

Try installing scMerlin.

 

[IcerJo]

The firmware has been rock solid for me, but I would randomly have an out of disk error that would kill my internet connection for an undisclosed amount of time. Long story short, turns out there has been an ongoing issue with the ASUSWRT Home Assistant service where it just keeps spamming a new SSH connection. I disabled that addon/service and rebooted my HA Server and my router, the memory now properly hovers around 60% on my XT12.

 

[HarryMuscle]

I've been getting the following error in my log when I try to run the WireGuard server and multiple WireGuard client instances. The first two clients seem to start up fine but the third, fourth, and fifth trigger this error and even though they show as connected no data can be transferred over their connection.

Oct 16 22:12:03 kernel: ^[[0;33;41m[ERROR pktrunner] runnerUcast_inetaddr_event,181: Could not rdpa_system_ipv4_host_address_table_add ret=-3^[[0m

This issue is repeatable even after a factory reset and minimal reconfigure. I'm doing this on a RT-AX86U Pro running 388.4 firmware

Thanks,
Harry

EDIT: This is definitely somehow related to also running a WireGuard server cause as soon as I disable the server and reboot, all 5 clients are able to start up.

How to reproduce:

Configure the WireGuard Server first with 10 clients and then configure all 5 WireGuard Clients, some of the clients will fail to start with the above message. Disable the WG server and reboot the router, all of the clients start, but try to start the WG server again and you'll get the above error message and the server won't start correctly (ie: no data can be transferred).

 

[RMerlin]

pktrunner is closed source and outside of my control.

 

[HarryMuscle]

pktrunner is closed source and outside of my control.

The strange thing is that even if I disable pktrunner via SSH it still throws those errors when using the WG Server and multiple WG Clients.

 

[opensourcehw]

Ugh, I tried doing some mild searches.. but anyhoo I'm on 386.7 on my AX86U... any reservations or things I should take heed of before upgrading to 3004.388.4_0 ??

Am I good to go? Is it safe to do a straight dirty flash from 386.7 to 3004.388.4_0 on the AX86U ??

I could not find anything that would advise against it necessarily, I'll probably go ahead and try it... lest someone may suggest that I should perhaps upgrade sequentially before making the jump?

TIA

 

[Robert Tickle]

Ugh, I tried doing some mild searches.. but anyhoo I'm on 386.7 on my AX86U... any reservations or things I should take heed of before upgrading to 3004.388.4_0 ??

I'm a good to go? Is it safe to do a straight dirty flash from 386.7 to 3004.388.4_0 on the AX86U ??

I could not find anything that would advise against it necessarily, I'll probably go ahead and try it... lest someone may suggest that I should perhaps upgrade sequentially before making the jump?

TIA

I had issues when I did a dirty flash from 386.7_2 to 3004.388.4_0 on my AX86U. Ended up doing a factory reset and reconfiguring from scratch. Now my network is the most stable its been in the three years I've had this configuration.

 

[ketma]

Hi, i wonder if anyone can help diagnose an issue I keep encountering.

I have 2x XT12 flashed from the stock firmware to 3004.388.4_0

All is typically well but randomly after a couple of days of uptime (in this occurrence almost 4 days) I get a reboot of the primary router, for instance it crashed/rebooted whilst updating a game on steam. When it restarted connection to the node is strong and it's back in business. If the router doesn't reboot everything is solid, no weird behaviour at all.

These are the router logs from the initial crash/reboot:

<snip>
Oct 18 20:53:15 roamast: eth4: disconnect weak signal strength station [xx:xx:xx:xx:75:2e]
Oct 18 20:53:15 roamast: eth4: remove client [xx:xx:xx:xx:75:2e] from monitor list
Oct 18 20:59:06 roamast: [EXAP]Deauth old sta in 1 0: xx:xx:xx:xx:AA:37
Oct 18 20:59:06 roamast: eth5: disconnect weak signal strength station [xx:xx:xx:xx:aa:37]
Oct 18 20:59:06 wlceventd: wlceventd_proc_event(645): eth5: Deauth_ind xx:xx:xx:xx:AA:37, status: 0, reason: Previous authentication no longer valid (2), rssi:-75
Oct 18 20:59:06 roamast: eth5: remove client [xx:xx:xx:xx:aa:37] from monitor list
Oct 18 20:59:07 wlceventd: wlceventd_proc_event(645): eth5: Deauth_ind xx:xx:xx:xx:AA:37, status: 0, reason: Previous authentication no longer valid (2), rssi:-75
<rebooted at this point>
May 5 06:05:18 kernel: klogd started: BusyBox v1.25.1 (2023-08-21 15:34:18 EDT)
May 5 06:05:18 kernel: Linux version 4.19.183 (merlin@ubuntu-dev) (gcc version 9.2.0 (Buildroot 2019.11.1)) #1 SMP PREEMPT Mon Aug 21 15:34:47 EDT 2023
May 5 06:05:18 kernel: random: get_random_bytes called from start_kernel+0x9c/0x454 with crng_init=0
May 5 06:05:18 kernel: Kernel command line: coherent_pool=4M cpuidle_sysfs_switch pci=pcie_bus_safe console=ttyAMA0,115200 earlycon rootwait mtdparts=brcmnand.0:2097152(loader),264241152@2097152(image),524288@266338304(crashlog) root=/dev/ubiblock0_6 ubi.mtd=image ubi.block=0,6 rootfstype=squashfs cma=0M
May 5 06:05:18 kernel: mtusize 1500
May 5 06:05:18 kernel: CCI hardware cache coherency enabled
May 5 06:05:18 kernel: bootloader version U-Boot 2019.07 (Aug 21 2023 - 16:27:51 -0400), Build: 5.04L.0
<snip...and then back on-line>
May 5 06:05:54 rc_service: ip-up 2771:notify_rc stop_ntpd
May 5 06:05:54 rc_service: ip-up 2771:notify_rc start_ntpd
May 5 06:05:54 ntpd: Started ntpd
May 5 06:05:55 acsd: acs_start(737): cs scan failed ret code: -16
May 5 06:05:55 acsd: acs_init_run(1197): acs_start failed for ifname: eth6
Oct 18 21:57:06 ntpd: Initial clock set
Oct 18 21:57:06 WAN_Connection: WAN was restored.
Oct 18 21:57:08 GPY211: ### GPY211 WAR AUTO : eth3 ###

Apologies if this information doesn't help or I've included the wrong information, I replaced the MAC addresses with xx, but would appreciate any advice from the experts here.

I'm not using 160MHz or QoS. The 2.4/5GHz bands are separate, wireless backhaul enabled, all settings default to what I recall.

Thanks.

 

[Morris]

Hi, i wonder if anyone can help diagnose an issue I keep encountering.

I have 2x XT12 flashed from the stock firmware to 3004.388.4_0

All is typically well but randomly after a couple of days of uptime (in this occurrence almost 4 days) I get a reboot of the primary router, for instance it crashed/rebooted whilst updating a game on steam. When it restarted connection to the node is strong and it's back in business. If the router doesn't reboot everything is solid, no weird behaviour at all.

These are the router logs from the initial crash/reboot:

<snip>
Oct 18 20:53:15 roamast: eth4: disconnect weak signal strength station [xx:xx:xx:xx:75:2e]
Oct 18 20:53:15 roamast: eth4: remove client [xx:xx:xx:xx:75:2e] from monitor list
Oct 18 20:59:06 roamast: [EXAP]Deauth old sta in 1 0: xx:xx:xx:xx:AA:37
Oct 18 20:59:06 roamast: eth5: disconnect weak signal strength station [xx:xx:xx:xx:aa:37]
Oct 18 20:59:06 wlceventd: wlceventd_proc_event(645): eth5: Deauth_ind xx:xx:xx:xx:AA:37, status: 0, reason: Previous authentication no longer valid (2), rssi:-75
Oct 18 20:59:06 roamast: eth5: remove client [xx:xx:xx:xx:aa:37] from monitor list
Oct 18 20:59:07 wlceventd: wlceventd_proc_event(645): eth5: Deauth_ind xx:xx:xx:xx:AA:37, status: 0, reason: Previous authentication no longer valid (2), rssi:-75
<rebooted at this point>
May 5 06:05:18 kernel: klogd started: BusyBox v1.25.1 (2023-08-21 15:34:18 EDT)
May 5 06:05:18 kernel: Linux version 4.19.183 (merlin@ubuntu-dev) (gcc version 9.2.0 (Buildroot 2019.11.1)) #1 SMP PREEMPT Mon Aug 21 15:34:47 EDT 2023
May 5 06:05:18 kernel: random: get_random_bytes called from start_kernel+0x9c/0x454 with crng_init=0
May 5 06:05:18 kernel: Kernel command line: coherent_pool=4M cpuidle_sysfs_switch pci=pcie_bus_safe console=ttyAMA0,115200 earlycon rootwait mtdparts=brcmnand.0:2097152(loader),264241152@2097152(image),524288@266338304(crashlog) root=/dev/ubiblock0_6 ubi.mtd=image ubi.block=0,6 rootfstype=squashfs cma=0M
May 5 06:05:18 kernel: mtusize 1500
May 5 06:05:18 kernel: CCI hardware cache coherency enabled
May 5 06:05:18 kernel: bootloader version U-Boot 2019.07 (Aug 21 2023 - 16:27:51 -0400), Build: 5.04L.0
<snip...and then back on-line>
May 5 06:05:54 rc_service: ip-up 2771:notify_rc stop_ntpd
May 5 06:05:54 rc_service: ip-up 2771:notify_rc start_ntpd
May 5 06:05:54 ntpd: Started ntpd
May 5 06:05:55 acsd: acs_start(737): cs scan failed ret code: -16
May 5 06:05:55 acsd: acs_init_run(1197): acs_start failed for ifname: eth6
Oct 18 21:57:06 ntpd: Initial clock set
Oct 18 21:57:06 WAN_Connection: WAN was restored.
Oct 18 21:57:08 GPY211: ### GPY211 WAR AUTO : eth3 ###

Apologies if this information doesn't help or I've included the wrong information, I replaced the MAC addresses with xx, but would appreciate any advice from the experts here.

I'm not using 160MHz or QoS. The 2.4/5GHz bands are separate, wireless backhaul enabled, all settings default to what I recall.

Thanks.

I suggest you start your own thread for this. We will need to know what router and firmware version.

 

[BGood]

At the risk of asking a dumb question, I have an Asus ROG Rapture AX11000 but I'm not a gamer. Evidently I have been using the Merlin versions not having "rog" in their names without even realizing. This time, I flashed using the "rog" version and it looks *very* different, though I think it's cosmetic. I'm assuming that if I flash again and use GT-AX11000_3004_388.4_0_ubi that it will look more like what I'm accustomed to. Is this correct? Am I losing anything by not using the "rog" version?

 

[ketma]

I suggest you start your own thread for this. We will need to know what router and firmware version.

Hi, it is stated clearly in my post:

I have 2x XT12 flashed from the stock firmware to 3004.388.4_0

Thanks.

 

[Morris]

Hi, it is stated clearly in my post:

I have 2x XT12 flashed from the stock firmware to 3004.388.4_0

Thanks.

I forgot that the XT12 runs Merlin. As you are experiencing a router crash, you could swap router and node to see if the router has a hardware issue.