Release Asuswrt-Merlin 384.19 is now available

[jpthsd]

Since I decided to dust off my AC68U and try it out as an AiMesh node, both the router and node have only used Merlin firmware. I haven't used ASUS' stock firmware for years.

My AC86U was on Merlin 384.17 when I first added the AC68U as a node, so I updated it to that version, then when 384.18 came out, I updated the router and node to that version, and now both are on 384.19. No issues with my mesh setup on any of these Merlin versions in my environment.

Yep,,,solid working here ,,,AC86U Main and AC68U AiMesh node both are 384.18. I am little hesitate to go to 384.19 now as reported many issues thus decided to stay with 384.18 as it's been stable for months now until....

Imagine ,,,couple hundreds dollar Wifi router runs great 4+ years !!! (AC68U 4+ years old ,AC86U 6 months old and covering all house with Wifi 2.4/5Ghz full speed ahead with WAN 500/500)!!

I like stability!

 

[Thomas Szücs]

Do you run Adaptive QOS? For some reason with fq_codel set on my AC86U the RAM usage would go up every day. A lot slower than 100MB per day.

No

 

[Thomas Szücs]

Linux manages memory much different than Windows. Instead of letting unused memory sit around and do nothing, Linux will use it for cache and other things until it is needed by programs. At that time, Linux will give the memory back.

People fuss over Linux memory usage needlessly. If the router is working fine, don't bother resetting just because the memory "looks" like it is running low.

I had a RT-AC3200 before with simular setup. On that the memory usage was constant.

 

[jeden]

Linux manages memory much different than Windows. Instead of letting unused memory sit around and do nothing, Linux will use it for cache and other things until it is needed by programs. At that time, Linux will give the memory back.

Windows behaves more or less in the same way than Linux. Current screenshot from my computer:

The difference is that, unlike Asuswrt, Windows correctly reports the amount of free memory when you look at the task manager. Regarding this: https://www.snbforums.com/threads/memory-usage-at-97.64198/#post-585668

 

[richardeid]

Linux manages memory much different than Windows. Instead of letting unused memory sit around and do nothing, Linux will use it for cache and other things until it is needed by programs. At that time, Linux will give the memory back.

People fuss over Linux memory usage needlessly. If the router is working fine, don't bother resetting just because the memory "looks" like it is running low.

I could be mistaken but I think Windows has been precaching since Vista which would have been like 2005. Maybe XP was doing it before Vista but I don't recall that. I'm surprised some people are still in the "Winblows" days. Like I guess I know there are still people that don't do automatic updates but that still holds at least a little merit because, especially as of late, updates break things sometimes. But to be misinformed for a decade and a half? That's craziness. I mean no disrespect, but it almost seems impossible to not know something so trivial, especially when it's something you seem to know about another OS.

 

[Jeffrey Young]

I could be mistaken but I think Windows has been precaching since Vista which would have been like 2005. Maybe XP was doing it before Vista but I don't recall that. I'm surprised some people are still in the "Winblows" days. Like I guess I know there are still people that don't do automatic updates but that still holds at least a little merit because, especially as of late, updates break things sometimes. But to be misinformed for a decade and a half? That's craziness. I mean no disrespect, but it almost seems impossible to not know something so trivial, especially when it's something you seem to know about another OS.

The difference is that, unlike Asuswrt, Windows correctly reports the amount of free memory when you look at the task manager. Regarding this: https://www.snbforums.com/threads/memory-usage-at-97.64198/#post-585668

Hmmm, perhaps my bad on bad wording. Manage was a poor choice of words. Perhaps reporting would have been a better choice. I am well aware that Windows also caches memory. Was not my intention to nudge a hornet nest, but I appreciate the clarification as I eat some crowe (@richardeid, no offense taken). My main point still remains not to worry to much about the high amount of ram used until it starts to be a problem.

Cheers all

 

[AntonK]

Stop worrying about your router's memory usage. I say that because, I know, I'm recovering memory worrier as well. As a number of more knowledgeable people on these forums have explained, Linux manages memory differently than, say, Windows. I turned off the Tools-Other Settings-Advanced Tweaks and Hacks-Cache flushing switch, and I've never been happier. Router hums along like a finely tuned piano...

 

[Vexira]

On my RT-AX88U I have noticed that it eats up around 100MB each day, so after 5 days I have to do a reset.
I run AMTM with Diversion. Any suggestions to what is so hungry?

Have you tired the automatic reboot and set it to every 4 days to see if that helps.

 

[lepa71]

I have RT-AC68U router and I'm trying to set up an Adaptive QOS but when I click on "Apply" nothing happens. Am I missing something? Thanks

 

[slidermike]

I have RT-AC68U router and I'm trying to set up an Adaptive QOS but when I click on "Apply" nothing happens. Am I missing something? Thanks

For adaptive QoS to work, I believe you also need to enable the Trend-Micro function.

ASUS Global

Driven by innovation & committed to quality, ASUS has a wide selection of best in class products. Find & buy a laptop, phone, router, monitor, motherboard & more

www.asus.com

 

[Thomas Szücs]

Have you tired the automatic reboot and set it to every 4 days to see if that helps.

I have only had the router for about 3 weeks and have noticed this behavior which is different than it was on my RT-AC3200. First, I will see what happens if goes to 100%.

 

[Vexira]

I have only had the router for about 3 weeks and have noticed this behavior which is different than it was on my RT-AC3200. First, I will see what happens if goes to 100%.

question did you factory reset when you switched from stock to merlin?
i use an every day reboot on my AX88U just to be sure

 

[Thomas Szücs]

question did you factory reset when you switched from stock to merlin?
i use an every day reboot on my AX88U just to be sure

I actually can't remember. I installed Merlin immediately after opening the box with the new router. The next thing might be to factory reboot and start from scratch.

 

[Jeffrey Young]

I have only had the router for about 3 weeks and have noticed this behavior which is different than it was on my RT-AC3200. First, I will see what happens if goes to 100%.

You can SSH into the router and use the "free" command to see exactly what memory is being used by programs, buffers and caches.

 

[lepa71]

For adaptive QoS to work, I believe you also need to enable the Trend-Micro function.

ASUS Global

Driven by innovation & committed to quality, ASUS has a wide selection of best in class products. Find & buy a laptop, phone, router, monitor, motherboard & more

www.asus.com

There is nothing that says about it here. https://www.asus.com/support/FAQ/1010950

It does let me turn it on but it does not apply it. The "apply" button does not do anything.

 

[lepa71]

For adaptive QoS to work, I believe you also need to enable the Trend-Micro function.

ASUS Global

Driven by innovation & committed to quality, ASUS has a wide selection of best in class products. Find & buy a laptop, phone, router, monitor, motherboard & more

www.asus.com

I enabled AIProtection and still can't activate the QOS. It says " Enabling QoS may take several minutes. " Any other idea.

 

[davelian]

My WIFI disconnected so often can you guy please help me out?

AC68U

Oct 10 14:49:40 acsd: acs_set_chspec: 0x100d (13) for reason APCS_CSTIMER
Oct 10 15:04:52 acsd: selected channel spec: 0x100c (12)
Oct 10 15:04:52 acsd: Adjusted channel spec: 0x100c (12)
Oct 10 15:04:52 acsd: selected channel spec: 0x100c (12)
Oct 10 15:04:52 acsd: acs_set_chspec: 0x100c (12) for reason APCS_CSTIMER
Oct 10 15:20:04 acsd: selected channel spec: 0x100d (13)
Oct 10 15:20:04 acsd: Adjusted channel spec: 0x100d (13)
Oct 10 15:20:04 acsd: selected channel spec: 0x100d (13)
Oct 10 15:20:04 acsd: acs_set_chspec: 0x100d (13) for reason APCS_CSTIMER
Oct 10 15:35:16 acsd: selected channel spec: 0x100d (13)
Oct 10 15:35:16 acsd: Adjusted channel spec: 0x100d (13)
Oct 10 15:35:16 acsd: selected channel spec: 0x100d (13)
Oct 10 15:35:16 acsd: acs_set_chspec: 0x100d (13) for reason APCS_CSTIMER
Oct 10 15:50:28 acsd: selected channel spec: 0x100d (13)
Oct 10 15:50:28 acsd: Adjusted channel spec: 0x100d (13)
Oct 10 15:50:28 acsd: selected channel spec: 0x100d (13)
Oct 10 15:50:28 acsd: acs_set_chspec: 0x100d (13) for reason APCS_CSTIMER
Oct 10 16:05:40 acsd: selected channel spec: 0x100d (13)
Oct 10 16:05:40 acsd: Adjusted channel spec: 0x100d (13)
Oct 10 16:05:40 acsd: selected channel spec: 0x100d (13)
Oct 10 16:05:40 acsd: acs_set_chspec: 0x100d (13) for reason APCS_CSTIMER
Oct 10 16:20:52 acsd: selected channel spec: 0x100c (12)
Oct 10 16:20:52 acsd: Adjusted channel spec: 0x100c (12)
Oct 10 16:20:52 acsd: selected channel spec: 0x100c (12)
Oct 10 16:20:52 acsd: acs_set_chspec: 0x100c (12) for reason APCS_CSTIMER
Oct 10 16:36:03 acsd: selected channel spec: 0x100d (13)
Oct 10 16:36:03 acsd: Adjusted channel spec: 0x100d (13)
Oct 10 16:36:03 acsd: selected channel spec: 0x100d (13)
Oct 10 16:36:03 acsd: acs_set_chspec: 0x100d (13) for reason APCS_CSTIMER
Oct 10 16:51:16 acsd: selected channel spec: 0x100d (13)
Oct 10 16:51:16 acsd: Adjusted channel spec: 0x100d (13)
Oct 10 16:51:16 acsd: selected channel spec: 0x100d (13)
Oct 10 16:51:16 acsd: acs_set_chspec: 0x100d (13) for reason APCS_CSTIMER
Oct 10 17:06:27 acsd: selected channel spec: 0x100d (13)
Oct 10 17:06:27 acsd: Adjusted channel spec: 0x100d (13)
Oct 10 17:06:27 acsd: selected channel spec: 0x100d (13)
Oct 10 17:06:27 acsd: acs_set_chspec: 0x100d (13) for reason APCS_CSTIMER
Oct 10 17:21:40 acsd: selected channel spec: 0x100d (13)
Oct 10 17:21:40 acsd: Adjusted channel spec: 0x100d (13)
Oct 10 17:21:40 acsd: selected channel spec: 0x100d (13)
Oct 10 17:21:40 acsd: acs_set_chspec: 0x100d (13) for reason APCS_CSTIMER
Oct 10 17:36:51 acsd: selected channel spec: 0x100c (12)
Oct 10 17:36:51 acsd: Adjusted channel spec: 0x100c (12)
Oct 10 17:36:51 acsd: selected channel spec: 0x100c (12)
Oct 10 17:36:51 acsd: acs_set_chspec: 0x100c (12) for reason APCS_CSTIMER
Oct 10 17:52:04 acsd: selected channel spec: 0x100d (13)
Oct 10 17:52:04 acsd: Adjusted channel spec: 0x100d (13)
Oct 10 17:52:04 acsd: selected channel spec: 0x100d (13)
Oct 10 17:52:04 acsd: acs_set_chspec: 0x100d (13) for reason APCS_CSTIMER
Oct 10 18:07:16 acsd: selected channel spec: 0x100d (13)
Oct 10 18:07:16 acsd: Adjusted channel spec: 0x100d (13)
Oct 10 18:07:16 acsd: selected channel spec: 0x100d (13)
Oct 10 18:07:16 acsd: acs_set_chspec: 0x100d (13) for reason APCS_CSTIMER
Oct 10 18:22:28 acsd: selected channel spec: 0x100d (13)
Oct 10 18:22:28 acsd: Adjusted channel spec: 0x100d (13)
Oct 10 18:22:28 acsd: selected channel spec: 0x100d (13)
Oct 10 18:22:28 acsd: acs_set_chspec: 0x100d (13) for reason APCS_CSTIMER
Oct 10 18:37:39 acsd: selected channel spec: 0x100d (13)
Oct 10 18:37:39 acsd: Adjusted channel spec: 0x100d (13)
Oct 10 18:37:39 acsd: selected channel spec: 0x100d (13)
Oct 10 18:37:39 acsd: acs_set_chspec: 0x100d (13) for reason APCS_CSTIMER
Oct 10 18:53:04 acsd: selected channel spec: 0x1005 (5)
Oct 10 18:53:04 acsd: Adjusted channel spec: 0x1005 (5)
Oct 10 18:53:04 acsd: selected channel spec: 0x1005 (5)
Oct 10 18:53:04 acsd: acs_set_chspec: 0x1005 (5) for reason APCS_CSTIMER
Oct 10 19:08:16 acsd: selected channel spec: 0x100c (12)
Oct 10 19:08:16 acsd: Adjusted channel spec: 0x100c (12)
Oct 10 19:08:16 acsd: selected channel spec: 0x100c (12)
Oct 10 19:08:16 acsd: acs_set_chspec: 0x100c (12) for reason APCS_CSTIMER
Oct 10 19:23:28 acsd: selected channel spec: 0x1001 (1)
Oct 10 19:23:28 acsd: Adjusted channel spec: 0x1001 (1)
Oct 10 19:23:28 acsd: selected channel spec: 0x1001 (1)
Oct 10 19:23:28 acsd: acs_set_chspec: 0x1001 (1) for reason APCS_CSTIMER
Oct 10 19:38:40 acsd: selected channel spec: 0x1001 (1)
Oct 10 19:38:40 acsd: Adjusted channel spec: 0x1001 (1)
Oct 10 19:38:40 acsd: selected channel spec: 0x1001 (1)
Oct 10 19:38:40 acsd: acs_set_chspec: 0x1001 (1) for reason APCS_CSTIMER

 

[Deleted member 22229]

Looks like the router keeps switching channels. Set your channel yourself and don't use auto.

 

[jsbeddow]

My WIFI disconnected so often can you guy please help me out?

AC68U

Oct 10 14:49:40 acsd: acs_set_chspec: 0x100d (13) for reason APCS_CSTIMER
Oct 10 15:04:52 acsd: selected channel spec: 0x100c (12)
Oct 10 15:04:52 acsd: Adjusted channel spec: 0x100c (12)
Oct 10 15:04:52 acsd: selected channel spec: 0x100c (12)
Oct 10 15:04:52 acsd: acs_set_chspec: 0x100c (12) for reason APCS_CSTIMER
Oct 10 15:20:04 acsd: selected channel spec: 0x100d (13)
Oct 10 15:20:04 acsd: Adjusted channel spec: 0x100d (13)
Oct 10 15:20:04 acsd: selected channel spec: 0x100d (13)
Oct 10 15:20:04 acsd: acs_set_chspec: 0x100d (13) for reason APCS_CSTIMER
Oct 10 15:35:16 acsd: selected channel spec: 0x100d (13)
Oct 10 15:35:16 acsd: Adjusted channel spec: 0x100d (13)
Oct 10 15:35:16 acsd: selected channel spec: 0x100d (13)
Oct 10 15:35:16 acsd: acs_set_chspec: 0x100d (13) for reason APCS_CSTIMER
Oct 10 15:50:28 acsd: selected channel spec: 0x100d (13)
Oct 10 15:50:28 acsd: Adjusted channel spec: 0x100d (13)
Oct 10 15:50:28 acsd: selected channel spec: 0x100d (13)
Oct 10 15:50:28 acsd: acs_set_chspec: 0x100d (13) for reason APCS_CSTIMER
Oct 10 16:05:40 acsd: selected channel spec: 0x100d (13)
Oct 10 16:05:40 acsd: Adjusted channel spec: 0x100d (13)
Oct 10 16:05:40 acsd: selected channel spec: 0x100d (13)
Oct 10 16:05:40 acsd: acs_set_chspec: 0x100d (13) for reason APCS_CSTIMER
Oct 10 16:20:52 acsd: selected channel spec: 0x100c (12)
Oct 10 16:20:52 acsd: Adjusted channel spec: 0x100c (12)
Oct 10 16:20:52 acsd: selected channel spec: 0x100c (12)
Oct 10 16:20:52 acsd: acs_set_chspec: 0x100c (12) for reason APCS_CSTIMER
Oct 10 16:36:03 acsd: selected channel spec: 0x100d (13)
Oct 10 16:36:03 acsd: Adjusted channel spec: 0x100d (13)
Oct 10 16:36:03 acsd: selected channel spec: 0x100d (13)
Oct 10 16:36:03 acsd: acs_set_chspec: 0x100d (13) for reason APCS_CSTIMER
Oct 10 16:51:16 acsd: selected channel spec: 0x100d (13)
Oct 10 16:51:16 acsd: Adjusted channel spec: 0x100d (13)
Oct 10 16:51:16 acsd: selected channel spec: 0x100d (13)
Oct 10 16:51:16 acsd: acs_set_chspec: 0x100d (13) for reason APCS_CSTIMER
Oct 10 17:06:27 acsd: selected channel spec: 0x100d (13)
Oct 10 17:06:27 acsd: Adjusted channel spec: 0x100d (13)
Oct 10 17:06:27 acsd: selected channel spec: 0x100d (13)
Oct 10 17:06:27 acsd: acs_set_chspec: 0x100d (13) for reason APCS_CSTIMER
Oct 10 17:21:40 acsd: selected channel spec: 0x100d (13)
Oct 10 17:21:40 acsd: Adjusted channel spec: 0x100d (13)
Oct 10 17:21:40 acsd: selected channel spec: 0x100d (13)
Oct 10 17:21:40 acsd: acs_set_chspec: 0x100d (13) for reason APCS_CSTIMER
Oct 10 17:36:51 acsd: selected channel spec: 0x100c (12)
Oct 10 17:36:51 acsd: Adjusted channel spec: 0x100c (12)
Oct 10 17:36:51 acsd: selected channel spec: 0x100c (12)
Oct 10 17:36:51 acsd: acs_set_chspec: 0x100c (12) for reason APCS_CSTIMER
Oct 10 17:52:04 acsd: selected channel spec: 0x100d (13)
Oct 10 17:52:04 acsd: Adjusted channel spec: 0x100d (13)
Oct 10 17:52:04 acsd: selected channel spec: 0x100d (13)
Oct 10 17:52:04 acsd: acs_set_chspec: 0x100d (13) for reason APCS_CSTIMER
Oct 10 18:07:16 acsd: selected channel spec: 0x100d (13)
Oct 10 18:07:16 acsd: Adjusted channel spec: 0x100d (13)
Oct 10 18:07:16 acsd: selected channel spec: 0x100d (13)
Oct 10 18:07:16 acsd: acs_set_chspec: 0x100d (13) for reason APCS_CSTIMER
Oct 10 18:22:28 acsd: selected channel spec: 0x100d (13)
Oct 10 18:22:28 acsd: Adjusted channel spec: 0x100d (13)
Oct 10 18:22:28 acsd: selected channel spec: 0x100d (13)
Oct 10 18:22:28 acsd: acs_set_chspec: 0x100d (13) for reason APCS_CSTIMER
Oct 10 18:37:39 acsd: selected channel spec: 0x100d (13)
Oct 10 18:37:39 acsd: Adjusted channel spec: 0x100d (13)
Oct 10 18:37:39 acsd: selected channel spec: 0x100d (13)
Oct 10 18:37:39 acsd: acs_set_chspec: 0x100d (13) for reason APCS_CSTIMER
Oct 10 18:53:04 acsd: selected channel spec: 0x1005 (5)
Oct 10 18:53:04 acsd: Adjusted channel spec: 0x1005 (5)
Oct 10 18:53:04 acsd: selected channel spec: 0x1005 (5)
Oct 10 18:53:04 acsd: acs_set_chspec: 0x1005 (5) for reason APCS_CSTIMER
Oct 10 19:08:16 acsd: selected channel spec: 0x100c (12)
Oct 10 19:08:16 acsd: Adjusted channel spec: 0x100c (12)
Oct 10 19:08:16 acsd: selected channel spec: 0x100c (12)
Oct 10 19:08:16 acsd: acs_set_chspec: 0x100c (12) for reason APCS_CSTIMER
Oct 10 19:23:28 acsd: selected channel spec: 0x1001 (1)
Oct 10 19:23:28 acsd: Adjusted channel spec: 0x1001 (1)
Oct 10 19:23:28 acsd: selected channel spec: 0x1001 (1)
Oct 10 19:23:28 acsd: acs_set_chspec: 0x1001 (1) for reason APCS_CSTIMER
Oct 10 19:38:40 acsd: selected channel spec: 0x1001 (1)
Oct 10 19:38:40 acsd: Adjusted channel spec: 0x1001 (1)
Oct 10 19:38:40 acsd: selected channel spec: 0x1001 (1)
Oct 10 19:38:40 acsd: acs_set_chspec: 0x1001 (1) for reason APCS_CSTIMER

By the way, it is considered poor form to post the same question in multiple locations in the hope of getting better or faster help. FYI.

 

[xdj]

Update:

Deauth_ind D8:*:*:*:*:6F, status: 0, reason: Class 3 frame received from nonassociated station (7)

Error is causing issues…ie 1000 entries in syslog in 30 minutes for one device! Causing interruption in tv viewing. I know it’s not a wifi issue as my NAS has an ethernet connection and gets the same errors.

I never had this issue or error with my old 86U running 384.19, only my new 86U. I’ve read it’s an Asus problem but again, it never was an issue in my old 86U.

Devices are being dropped from the WiFi connection constantly or can not connect to the WiFi.

AiMesh nodes dropping from the network (Offline status)

My wife’s iPhone MAC address changed when it reconnected to the new router's network. This one I don’t get. At one time the MAC ended in C0:AE and now ends in 07:27! I have noticed that there’s 2 MAC’s on the phone. One is in “General” > “About” WiFi address and the other is listed the wifi connection SSID when you press the information button that’s beside it. This may be normal for Apple products but I’ve never seen it but I’m not an Apple user.

I have a printer that doesn’t show up in the router, but I can view its status in a web browser and print to it. My wife’s work iPhone doesn’t show up in the router, yet it’s connected according to the phone’s status.

Internet Traffic gauge displaying 100% up and down when there is no traffic. As well as WAN/LAN Bandwidth Monitor dials not moving when there’s traffic and the traffic analyzer being blank when there’s traffic! A reboot fixed it but still, it hasn’t been a one-off thing!

One positive thing…I haven’t noticed any random reboots with 384.19 on my new 86U!

Just to remind everyone, I’m just running the minimal for a configuration while I’ve been troubleshooting issues and it’s a brand-new router with a clean install of 384.19.

So, to sum it up, I haven’t been able to solve any issues…the issues just increase ☹!

That’s it for now…I think I’m going back to 384.18 or .17. I’m just so tired of erroneous issues!

Cheers