Log Spam Issue in 386.1 / 386.1_2?

  • ATTENTION! As of November 1, 2020, you are not able to reply to threads 6 months after the thread is opened if there are more than 500 posts in the thread.
    Threads will not be locked, so posts may still be edited by their authors.
    Just start a new thread on the topic to post if you get an error message when trying to reply to a thread.

Rocketboy235

Occasional Visitor
Hello,

Recently, I was able to update my router (after doing a complete factory reset and erasing NVRAM for good measure) to v386.1_2 on my AC68U as well as my 2 AiMesh nodes (also AC68U) and I realized that sometimes, my remote log server would see all of this spam happen. Never experienced this issue beforehand in my few years of using the routers.

I replaced the actual Mac Address of the AiMesh node below to 00:00:00:00:00:00 FYI
Code:
Apr 10 06:50:25 RT-AC68U-Main-Router syslog wlceventd_proc_event(490): eth2: Deauth_ind 00:00:00:00:00:00, status: 0, reason: Class 2 frame received from nonauthenticated station (6), rssi:0
Apr 10 06:50:25 RT-AC68U-Main-Router syslog wlceventd_proc_event(490): eth2: Deauth_ind 00:00:00:00:00:00, status: 0, reason: Class 2 frame received from nonauthenticated station (6), rssi:0
Apr 10 06:50:25 RT-AC68U-Main-Router syslog wlceventd_proc_event(490): eth2: Deauth_ind 00:00:00:00:00:00, status: 0, reason: Class 2 frame received from nonauthenticated station (6), rssi:0
Apr 10 06:50:25 RT-AC68U-Main-Router syslog wlceventd_proc_event(490): eth2: Deauth_ind 00:00:00:00:00:00, status: 0, reason: Class 2 frame received from nonauthenticated station (6), rssi:0
Apr 10 06:50:25 RT-AC68U-Main-Router syslog wlceventd_proc_event(490): eth2: Deauth_ind 00:00:00:00:00:00, status: 0, reason: Class 2 frame received from nonauthenticated station (6), rssi:0
Apr 10 06:50:25 RT-AC68U-Main-Router syslog wlceventd_proc_event(490): eth2: Deauth_ind 00:00:00:00:00:00, status: 0, reason: Class 2 frame received from nonauthenticated station (6), rssi:0
Apr 10 06:50:25 RT-AC68U-Main-Router syslog wlceventd_proc_event(490): eth2: Deauth_ind 00:00:00:00:00:00, status: 0, reason: Class 2 frame received from nonauthenticated station (6), rssi:0
Apr 10 06:50:25 RT-AC68U-Main-Router syslog wlceventd_proc_event(490): eth2: Deauth_ind 00:00:00:00:00:00, status: 0, reason: Class 2 frame received from nonauthenticated station (6), rssi:0
Apr 10 06:50:25 RT-AC68U-Main-Router syslog wlceventd_proc_event(490): eth2: Deauth_ind 00:00:00:00:00:00, status: 0, reason: Class 2 frame received from nonauthenticated station (6), rssi:0
Apr 10 06:50:25 RT-AC68U-Main-Router syslog wlceventd_proc_event(490): eth2: Deauth_ind 00:00:00:00:00:00, status: 0, reason: Class 2 frame received from nonauthenticated station (6), rssi:0
Apr 10 06:50:25 RT-AC68U-Main-Router syslog wlceventd_proc_event(490): eth2: Deauth_ind 00:00:00:00:00:00, status: 0, reason: Class 2 frame received from nonauthenticated station (6), rssi:0

I would think this kind of message in the logs is harmless but I just saw that it repeated this message 100x all around Apr 10 06:50:25. I'm not exactly sure what is going on here.

Below is my log usage for the main router. The higher the blue bar on each day, the more logs it received that day and it mostly all points to the following logs above.
1618070335842.png



I do see that someone also experienced a similar issue and mentioned it here though they seemed more concern about the logging functionality than the actual log message spam:
 

ColinTaylor

Part of the Furniture
Known issue reported numerous times. It's just debugging information that Asus left in, ignore it.
 

Rocketboy235

Occasional Visitor
I see, thanks. I guess the only problem in my case would be that it spams my remote log server (has a 150 Mb monthly limit which this issue causes to exceed the limit pretty quickly). I suppose there is really nothing I can do about that then if I were to stay on the latest builds?
 

Jack Yaz

Part of the Furniture
install scribe, filter out the crap to other log files and set up a forward destination to your remote log server for the messages you do want to keep
 

lluke

New Around Here
I’ve started to face the same issue on my RT-AC86U since I’ve added to my network an Xbox Series S. I’ve tried several way to get rid of this annoying logs (hard resets, update to beta firmwares, review of almost all the Wi-Fi configurations, ...) and I may have found the solution.

After I‘ve set the configuration “Group Key Rotation Interval” to 0 for both the 2.4GHz and 5GHz connections I’m no longer seeing these annoying messages.

I’m aware of the possible security drawbacks but fortunately I live in a not so crowded area so that I can deal with that. My suggestion for you is to try the same settings and Googling a bit to understand which impacts may this change ha e on your network.
 

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