[Release] Asuswrt-Merlin 384.10 is now available

[RMerlin]

Thanks, I'll try to get at least one or two of these models compiled later tonight.

 

[fearz]

Since 384.10 I had a very strange problem where the router is acting very slowly, both CPUs are at 100%
I tried everything, fresh install, reverted back to 384.9 - same issue...
top shows different readings...like CPU 1 at 67% and CPU 2 at 66% - however in GUI it shows 100%...
whats being shown in top is diversion mainly and mtdblock3
In system logs..nothing abnormal...

What could be the issue?

Now im still on 384.10

I'm also not sure whats this:

Mar 28 10:08:59 WLCEVENTD: eth1: Assoc 00:04:20:FC:E3:43
Mar 28 10:09:01 WLCEVENTD: eth1: Disassoc 00:04:4B:4B:A2:47
Mar 28 10:09:01 WLCEVENTD: eth2: Assoc 00:09:B0:B5:FC:BD
Mar 28 10:09:01 WLCEVENTD: eth3: Disassoc 00:09:B0:B5:FC:BD
Mar 28 10:09:02 WLCEVENTD: eth1: Assoc 00:04:4B:4B:A2:47
Mar 28 10:09:04 WLCEVENTD: eth2: Assoc 28:CFA:17:85:EC
Mar 28 10:09:04 WLCEVENTD: eth3: Disassoc 28:CFA:17:85:EC
Mar 28 10:09:07 WLCEVENTD: eth3: Assoc D02:B0:87:09:7C
Mar 28 10:09:07 WLCEVENTD: eth1: Disassoc 00:04:4B:4B:A2:47
Mar 28 10:09:07 WLCEVENTD: eth2: Disassoc 28:CFA:17:85:EC
Mar 28 10:09:09 WLCEVENTD: eth1: Assoc 00:04:4B:4B:A2:47
Mar 28 10:09:14 WLCEVENTD: eth1: Disassoc 00:04:4B:4B:A2:47
Mar 28 10:09:16 WLCEVENTD: eth1: Assoc 00:04:4B:4B:A2:47
Mar 28 10:09:21 WLCEVENTD: eth1: Disassoc 00:04:4B:4B:A2:47
Mar 28 10:09:25 WLCEVENTD: eth3: Assoc D02:B0:87:09:7C
Mar 28 10:09:25 WLCEVENTD: eth1: Assoc 00:04:20:FC:E3:43
Mar 28 10:09:43 WLCEVENTD: eth3: Assoc D02:B0:87:09:7C
Mar 28 10:09:49 WLCEVENTD: eth1: Assoc 00:04:20:FC:E3:43
Mar 28 10:10:00 WLCEVENTD: eth3: Assoc D02:B0:87:09:7C
Mar 28 10:10:14 WLCEVENTD: eth1: Assoc 00:04:20:FC:E3:43
Mar 28 10:10:18 WLCEVENTD: eth3: Assoc D02:B0:87:09:7C
Mar 28 10:10:36 WLCEVENTD: eth3: Assoc D02:B0:87:09:7C
Mar 28 10:10:39 WLCEVENTD: eth1: Assoc 00:04:20:FC:E3:43
Mar 28 10:10:54 WLCEVENTD: eth3: Assoc D02:B0:87:09:7C
Mar 28 10:11:03 WLCEVENTD: eth2: Assoc 68:37:E9:C7:F8:76
Mar 28 10:11:03 WLCEVENTD: eth1: Assoc 00:04:20:FC:E3:43
Mar 28 10:11:12 WLCEVENTD: eth3: Assoc D02:B0:87:09:7C
Mar 28 10:11:28 WLCEVENTD: eth1: Assoc 00:04:20:FC:E3:43
Mar 28 10:11:30 WLCEVENTD: eth3: Assoc D02:B0:87:09:7C
Mar 28 10:11:48 WLCEVENTD: eth3: Assoc D02:B0:87:09:7C
Mar 28 10:11:53 WLCEVENTD: eth1: Assoc 00:04:20:FC:E3:43
Mar 28 10:11:53 WLCEVENTD: eth3: Assoc F4:F58:B6:57:0E
Mar 28 10:12:05 WLCEVENTD: eth3: Assoc D02:B0:87:09:7C
Mar 28 10:12:18 WLCEVENTD: eth1: Assoc 00:04:20:FC:E3:43
Mar 28 10:12:23 WLCEVENTD: eth3: Assoc D02:B0:87:09:7C
Mar 28 10:12:39 WLCEVENTD: eth1: Assoc 60:FA:CD:8A:66:9A
Mar 28 10:12:41 WLCEVENTD: eth3: Assoc D02:B0:87:09:7C
Mar 28 10:12:42 WLCEVENTD: eth1: Assoc 00:04:20:FC:E3:43
Mar 28 10:12:45 WLCEVENTD: eth1: Disassoc 60:FA:CD:8A:66:9A
Mar 28 10:12:59 WLCEVENTD: eth3: Assoc D02:B0:87:09:7C
Mar 28 10:13:10 WLCEVENTD: eth1: Assoc 00:04:20:FC:E3:43
Mar 28 10:13:17 WLCEVENTD: eth3: Assoc D02:B0:87:09:7C
Mar 28 10:13:35 WLCEVENTD: eth3: Assoc D02:B0:87:09:7C​

 

[maxbraketorque]

Since 384.10 I had a very strange problem where the router is acting very slowly, both CPUs are at 100%
I tried everything, fresh install, reverted back to 384.9 - same issue...
top shows different readings...like CPU 1 at 67% and CPU 2 at 66% - however in GUI it shows 100%...
whats being shown in top is diversion mainly and mtdblock3
In system logs..nothing abnormal...

What could be the issue?

Now im still on 384.10

I'm also not sure whats this:

Mar 28 10:08:59 WLCEVENTD: eth1: Assoc 00:04:20:FC:E3:43
Mar 28 10:09:01 WLCEVENTD: eth1: Disassoc 00:04:4B:4B:A2:47
Mar 28 10:09:01 WLCEVENTD: eth2: Assoc 00:09:B0:B5:FC:BD
Mar 28 10:09:01 WLCEVENTD: eth3: Disassoc 00:09:B0:B5:FC:BD
Mar 28 10:09:02 WLCEVENTD: eth1: Assoc 00:04:4B:4B:A2:47
Mar 28 10:09:04 WLCEVENTD: eth2: Assoc 28:CFA:17:85:EC
Mar 28 10:09:04 WLCEVENTD: eth3: Disassoc 28:CFA:17:85:EC
Mar 28 10:09:07 WLCEVENTD: eth3: Assoc D02:B0:87:09:7C
Mar 28 10:09:07 WLCEVENTD: eth1: Disassoc 00:04:4B:4B:A2:47
Mar 28 10:09:07 WLCEVENTD: eth2: Disassoc 28:CFA:17:85:EC
Mar 28 10:09:09 WLCEVENTD: eth1: Assoc 00:04:4B:4B:A2:47
Mar 28 10:09:14 WLCEVENTD: eth1: Disassoc 00:04:4B:4B:A2:47
Mar 28 10:09:16 WLCEVENTD: eth1: Assoc 00:04:4B:4B:A2:47
Mar 28 10:09:21 WLCEVENTD: eth1: Disassoc 00:04:4B:4B:A2:47
Mar 28 10:09:25 WLCEVENTD: eth3: Assoc D02:B0:87:09:7C
Mar 28 10:09:25 WLCEVENTD: eth1: Assoc 00:04:20:FC:E3:43
Mar 28 10:09:43 WLCEVENTD: eth3: Assoc D02:B0:87:09:7C
Mar 28 10:09:49 WLCEVENTD: eth1: Assoc 00:04:20:FC:E3:43
Mar 28 10:10:00 WLCEVENTD: eth3: Assoc D02:B0:87:09:7C
Mar 28 10:10:14 WLCEVENTD: eth1: Assoc 00:04:20:FC:E3:43
Mar 28 10:10:18 WLCEVENTD: eth3: Assoc D02:B0:87:09:7C
Mar 28 10:10:36 WLCEVENTD: eth3: Assoc D02:B0:87:09:7C
Mar 28 10:10:39 WLCEVENTD: eth1: Assoc 00:04:20:FC:E3:43
Mar 28 10:10:54 WLCEVENTD: eth3: Assoc D02:B0:87:09:7C
Mar 28 10:11:03 WLCEVENTD: eth2: Assoc 68:37:E9:C7:F8:76
Mar 28 10:11:03 WLCEVENTD: eth1: Assoc 00:04:20:FC:E3:43
Mar 28 10:11:12 WLCEVENTD: eth3: Assoc D02:B0:87:09:7C
Mar 28 10:11:28 WLCEVENTD: eth1: Assoc 00:04:20:FC:E3:43
Mar 28 10:11:30 WLCEVENTD: eth3: Assoc D02:B0:87:09:7C
Mar 28 10:11:48 WLCEVENTD: eth3: Assoc D02:B0:87:09:7C
Mar 28 10:11:53 WLCEVENTD: eth1: Assoc 00:04:20:FC:E3:43
Mar 28 10:11:53 WLCEVENTD: eth3: Assoc F4:F58:B6:57:0E
Mar 28 10:12:05 WLCEVENTD: eth3: Assoc D02:B0:87:09:7C
Mar 28 10:12:18 WLCEVENTD: eth1: Assoc 00:04:20:FC:E3:43
Mar 28 10:12:23 WLCEVENTD: eth3: Assoc D02:B0:87:09:7C
Mar 28 10:12:39 WLCEVENTD: eth1: Assoc 60:FA:CD:8A:66:9A
Mar 28 10:12:41 WLCEVENTD: eth3: Assoc D02:B0:87:09:7C
Mar 28 10:12:42 WLCEVENTD: eth1: Assoc 00:04:20:FC:E3:43
Mar 28 10:12:45 WLCEVENTD: eth1: Disassoc 60:FA:CD:8A:66:9A
Mar 28 10:12:59 WLCEVENTD: eth3: Assoc D02:B0:87:09:7C
Mar 28 10:13:10 WLCEVENTD: eth1: Assoc 00:04:20:FC:E3:43
Mar 28 10:13:17 WLCEVENTD: eth3: Assoc D02:B0:87:09:7C
Mar 28 10:13:35 WLCEVENTD: eth3: Assoc D02:B0:87:09:7C​

Assoc/disassoc events are normal, but they are not usually reported in the log. ASUS introduced a bug in 45149 that caused these to be reported in the log. This has to be fixed by ASUS. These should have been present with 384.9 as well.

 

[fearz]

Assoc/disassoc events are normal, but they are not usually reported in the log. ASUS introduced a bug in 45149 that caused these to be reported in the log. This has to be fixed by ASUS. These should have been present with 384.9 as well.

Right, this problem is present in both, but is that whats causing the CPU 100%?

 

[skeal]

Right, this problem is present in both, but is that whats causing the CPU 100%?

Hop onto a SSH terminal and check "top" to see what is hogging the processors.

 

[fearz]

Hop onto a SSH terminal and check "top" to see what is hogging the processors.

Like i said, only diversion and its not consuming as shown in the GUI..only abou 60%..however in GUI shows both CPU as 100%

I even disabled it..still shows 100%

 

[skeal]

Like i said, only diversion and its not consuming as shown in the GUI..only abou 60%..however in GUI shows both CPU as 100%

I even disabled it..still shows 100%

Did you reset to defaults following the flash to the newest firmware you have? This sounds like a one of kind of thing.

 

[fearz]

Did you reset to defaults following the flash to the newest firmware you have? This sounds like a one of kind of thing.

Yes

 

[giracueca]

Hi, does anyone know if there is a problem with Chinese mobile phones and American routers Asus in WIFI connections? I use a OnePlus 6 and my Ac86u (US) sometimes hangs, does not surf, it takes to get back even with the last update. I read that other cell phones such as google pixel 2 had problems causing the router to reboot. If I use an AC66 with firmware tomato, latest version, everything works fine. Even with an older wireless internet driver, and this problem just happen to my OP6.

 

[skeal]

If you are setting up your scripts new. Install amtm and then skynet, then continue with the rest of what you need.

 

[fearz]

If you are setting up your scripts new. Install amtm and then skynet, then continue with the rest of what you need.

I only install diversion

 

[Pizzy09]

Hello, on my RT-AC87U after the 384.10 update sometimes the 5GHz WiFi suddenly goes down. It lasts about 1 minute and then it comes back. No errors on syslog.
Obviously made hard reset after the update and set manually all the configurations. Any suggestions?
No issues with previous versions.

 

[bobo27]

You should just have to throw them into the folder and restart the server and clients on the router. Has always worked for me. I always back up the whole folder /jffs.

Thanks. I just tried this by making a backup of the JFFS first, unpack on Mac, then edit the CA file from server1 in Atom. Make a new tar file with GUItar. Upload this to the router. Then reboot. Unfortunately this doesn’t work either.
I noticed the new GUI only support 1024 and 2048 bits rsa keys, but my CA uses 4096 bit. Which worked on the AC-66U.. does the new openvpn not support this maybe?


Sent from my iPhone using Tapatalk

 

[RMerlin]

About six months ago, I started doing all of my development in Atom editor on Windows 10

I must be hardcore, I do 95% of my development in nano...

 

[RMerlin]

Hi all! I'm having an issue with my 5ghz after the update. Everything seemed fine after the update, but after a few minutes, the app is sluggish and the 5ghz seems to loose some of its configuration. Has anybody seen this issue?

"Channel 0" usually indicates that the wifi radio is down/crashed/dead. Try power cycling your router.

The RT-AC86U driver is unchanged in 384.10.


I encountered that two days ago. The second 5 GHz radio of my development RT-AC5300 died

 

[cierzo]

What router models are the Moviestar users having? I'd like to create a test build or two to confirm that fixing Quagga takes care of the problem.

RT-AC87 here.

 

[RMerlin]

I uploaded a few test builds with the Quagga fix, please give them a try.

https://asuswrt.lostrealm.ca/test-builds

Also make sure to remove the suggested workaround script if you had created one.

 

[cmkelley]

I must be hardcore, I do 95% of my development in nano...

I do all of my development in vim.

 

[Ro berto]

Hi, does anyone know if there is a problem with Chinese mobile phones and American routers Asus in WIFI connections? I use a OnePlus 6 and my Ac86u (US) sometimes hangs, does not surf, it takes to get back even with the last update. I read that other cell phones such as google pixel 2 had problems causing the router to reboot. If I use an AC66 with firmware tomato, latest version, everything works fine. Even with an older wireless internet driver, and this problem just happen to my OP6.

Hi
I'm also using the same router and the same phone and I'm having no problems (both of them with the latest update). My router is from Amazon Germany, but it's made in China with HW rev 1.5 (I guess yours is made in China too).

The problem is the camera quality of the OP6, but that's a different topic

 

[cierzo]

I uploaded a few test builds with the Quagga fix, please give them a try.

https://asuswrt.lostrealm.ca/test-builds

Also make sure to remove the suggested workaround script if you had created one.

AC87
Routes have returned and everything is working for the moment (TV channels, menus and VOD)
I'll will test throughly later but it looks good.

Thank you very much.