What's new
  • 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!

PLEASE HELP - System log getting flooded with wlceventd

RetroPas74

New Around Here
Hi guys I hope you can help me with this issue...

my system log is showing every 3-5 seconds the following lines (this is just a fraction of what I am seeing in the log):

Jul 8 16:47:32 wlceventd: wlceventd_proc_event(685): wl3.1: Auth XX:XX:XX:XX:XX:XX status: Successful (0), rssi:0
Jul 8 16:47:32 wlceventd: wlceventd_proc_event(645): wl3.1: Deauth_ind XX:XX:XX:XX:XX:XX, status: 0, reason: Unspecified reason (1), rssi:0
Jul 8 16:47:35 wlceventd: wlceventd_proc_event(685): wl3.1: Auth XX:XX:XX:XX:XX:XX, status: Successful (0), rssi:0
Jul 8 16:47:35 wlceventd: wlceventd_proc_event(645): wl3.1: Deauth_ind XX:XX:XX:XX:XX:XX, status: 0, reason: Unspecified reason (1), rssi:0
Jul 8 16:47:39 wlceventd: wlceventd_proc_event(685): wl3.1: Auth XX:XX:XX:XX:XX:XX, status: Successful (0), rssi:0
Jul 8 16:47:39 wlceventd: wlceventd_proc_event(645): wl3.1: Deauth_ind XX:XX:XX:XX:XX:XX status: 0, reason: Unspecified reason (1), rssi:0
Jul 8 16:47:42 wlceventd: wlceventd_proc_event(685): wl3.1: Auth XX:XX:XX:XX:XX:XX, status: Successful (0), rssi:0
Jul 8 16:47:42 wlceventd: wlceventd_proc_event(645): wl3.1: Deauth_ind XX:XX:XX:XX:XX:XX, status: 0, reason: Unspecified reason (1), rssi:0
Jul 8 16:47:46 wlceventd: wlceventd_proc_event(685): wl3.1: Auth XX:XX:XX:XX:XX:XX, status: Successful (0), rssi:0
Jul 8 16:47:46 wlceventd: wlceventd_proc_event(645): wl3.1: Deauth_ind XX:XX:XX:XX:XX:XX, status: 0, reason: Unspecified reason (1), rssi:0
Jul 8 16:47:49 wlceventd: wlceventd_proc_event(685): wl3.1: Auth XX:XX:XX:XX:XX:XX, status: Successful (0), rssi:0
Jul 8 16:47:49 wlceventd: wlceventd_proc_event(645): wl3.1: Deauth_ind XX:XX:XX:XX:XX:XX, status: 0, reason: Unspecified reason (1), rssi:0
Jul 8 16:47:53 wlceventd: wlceventd_proc_event(685): wl3.1: Auth XX:XX:XX:XX:XX:XX, status: Successful (0), rssi:0
Jul 8 16:47:53 wlceventd: wlceventd_proc_event(645): wl3.1: Deauth_ind XX:XX:XX:XX:XX:XX, status: 0, reason: Unspecified reason (1), rssi:0
Jul 8 16:47:56 wlceventd: wlceventd_proc_event(685): wl3.1: Auth XX:XX:XX:XX:XX:XX, status: Successful (0), rssi:0
Jul 8 16:47:56 wlceventd: wlceventd_proc_event(645): wl3.1: Deauth_ind XX:XX:XX:XX:XX:XX, status: 0, reason: Unspecified reason (1), rssi:0
Jul 8 16:48:00 wlceventd: wlceventd_proc_event(685): wl3.1: Auth XX:XX:XX:XX:XX:XX, status: Successful (0), rssi:0
Jul 8 16:48:00 wlceventd: wlceventd_proc_event(645): wl3.1: Deauth_ind XX:XX:XX:XX:XX:XX, status: 0, reason: Unspecified reason (1), rssi:0
Jul 8 16:48:04 wlceventd: wlceventd_proc_event(685): wl3.1: Auth XX:XX:XX:XX:XX:XX, status: Successful (0), rssi:0
Jul 8 16:48:04 wlceventd: wlceventd_proc_event(645): wl3.1: Deauth_ind XX:XX:XX:XX:XX:XX, status: 0, reason: Unspecified reason (1), rssi:0
Jul 8 16:48:07 wlceventd: wlceventd_proc_event(685): wl3.1: Auth XX:XX:XX:XX:XX:XX, status: Successful (0), rssi:0
Jul 8 16:48:07 wlceventd: wlceventd_proc_event(645): wl3.1: Deauth_ind XX:XX:XX:XX:XX:XX, status: 0, reason: Unspecified reason (1), rssi:0
Jul 8 16:48:11 wlceventd: wlceventd_proc_event(685): wl3.1: Auth XX:XX:XX:XX:XX:XX, status: Successful (0), rssi:0
Jul 8 16:48:11 wlceventd: wlceventd_proc_event(645): wl3.1: Deauth_ind XX:XX:XX:XX:XX:XX, status: 0, reason: Unspecified reason (1), rssi:0
Jul 8 16:48:14 wlceventd: wlceventd_proc_event(685): wl3.1: Auth XX:XX:XX:XX:XX:XX, status: Successful (0), rssi:0
Jul 8 16:48:14 wlceventd: wlceventd_proc_event(645): wl3.1: Deauth_ind XX:XX:XX:XX:XX:XX, status: 0, reason: Unspecified reason (1), rssi:0
Jul 8 16:48:18 wlceventd: wlceventd_proc_event(685): wl3.1: Auth XX:XX:XX:XX:XX:XX, status: Successful (0), rssi:0

- its exactly the same MAC address all the time
- The MAC address A0:92:XX:XX:XX:XX is registered to Tuya Smart Inc
- I don't see this MAC address in my device list

Tried wireless MAC filter to block the MAC address - no success; issue still happening...
for the life of me I cannot figure out which device is causing this...

Router: GT-AXE16000
Firmware: Merlin 3006.102.5 beta1

Thank you in advance for your help!
 
Likely some IoT device, possibly belonging to a neighbour. It appears to be trying to connect to your 6GHz guest Wi-Fi. What 6GHz capable devices do you own?

P.S. You don't need to obscure the MAC address.
 
disabling the 6GHz radio didn't help, still getting the same messages:

Jul 8 19:47:43 wlceventd: wlceventd_proc_event(645): eth10: Deauth_ind A0:92:08:93:B6:10, status: 0, reason: Unspecified reason (1), rssi:0
Jul 8 19:47:43 wlceventd: wlceventd_proc_event(685): wl3.1: Auth A0:92:08:93:B6:10, status: Successful (0), rssi:0
Jul 8 19:47:43 wlceventd: wlceventd_proc_event(685): eth10: Auth A0:92:08:93:B6:10, status: Successful (0), rssi:0
Jul 8 19:47:43 wlceventd: wlceventd_proc_event(645): wl3.1: Deauth_ind A0:92:08:93:B6:10, status: 0, reason: Unspecified reason (1), rssi:0
Jul 8 19:47:46 wlceventd: wlceventd_proc_event(645): eth10: Deauth_ind A0:92:08:93:B6:10, status: 0, reason: Unspecified reason (1), rssi:0
Jul 8 19:47:46 wlceventd: wlceventd_proc_event(685): wl3.1: Auth A0:92:08:93:B6:10, status: Successful (0), rssi:0
Jul 8 19:47:46 wlceventd: wlceventd_proc_event(685): eth10: Auth A0:92:08:93:B6:10, status: Successful (0), rssi:0
Jul 8 19:47:46 wlceventd: wlceventd_proc_event(645): wl3.1: Deauth_ind A0:92:08:93:B6:10, status: 0, reason: Unspecified reason (1), rssi:0
Jul 8 19:47:50 wlceventd: wlceventd_proc_event(645): eth10: Deauth_ind A0:92:08:93:B6:10, status: 0, reason: Unspecified reason (1), rssi:0
Jul 8 19:47:50 wlceventd: wlceventd_proc_event(685): wl3.1: Auth A0:92:08:93:B6:10, status: Successful (0), rssi:0
Jul 8 19:47:50 wlceventd: wlceventd_proc_event(685): eth10: Auth A0:92:08:93:B6:10, status: Successful (0), rssi:0
Jul 8 19:47:50 wlceventd: wlceventd_proc_event(645): wl3.1: Deauth_ind A0:92:08:93:B6:10, status: 0, reason: Unspecified reason (1), rssi:0
Jul 8 19:47:54 wlceventd: wlceventd_proc_event(645): eth10: Deauth_ind A0:92:08:93:B6:10, status: 0, reason: Unspecified reason (1), rssi:0
Jul 8 19:47:54 wlceventd: wlceventd_proc_event(685): wl3.1: Auth A0:92:08:93:B6:10, status: Successful (0), rssi:0
Jul 8 19:47:54 wlceventd: wlceventd_proc_event(685): eth10: Auth A0:92:08:93:B6:10, status: Successful (0), rssi:0
Jul 8 19:47:54 wlceventd: wlceventd_proc_event(645): wl3.1: Deauth_ind A0:92:08:93:B6:10, status: 0, reason: Unspecified reason (1), rssi:0
Jul 8 19:47:57 wlceventd: wlceventd_proc_event(645): eth10: Deauth_ind A0:92:08:93:B6:10, status: 0, reason: Unspecified reason (1), rssi:0
Jul 8 19:47:57 wlceventd: wlceventd_proc_event(685): wl3.1: Auth A0:92:08:93:B6:10, status: Successful (0), rssi:0
Jul 8 19:47:57 wlceventd: wlceventd_proc_event(685): eth10: Auth A0:92:08:93:B6:10, status: Successful (0), rssi:0
Jul 8 19:47:57 wlceventd: wlceventd_proc_event(645): wl3.1: Deauth_ind A0:92:08:93:B6:10, status: 0, reason: Unspecified reason (1), rssi:0
Jul 8 19:48:01 wlceventd: wlceventd_proc_event(645): eth10: Deauth_ind A0:92:08:93:B6:10, status: 0, reason: Unspecified reason (1), rssi:0
Jul 8 19:48:01 wlceventd: wlceventd_proc_event(685): wl3.1: Auth A0:92:08:93:B6:10, status: Successful (0), rssi:0
Jul 8 19:48:01 wlceventd: wlceventd_proc_event(685): eth10: Auth A0:92:08:93:B6:10, status: Successful (0), rssi:0
Jul 8 19:48:01 wlceventd: wlceventd_proc_event(645): wl3.1: Deauth_ind A0:92:08:93:B6:10, status: 0, reason: Unspecified reason (1), rssi:0
 
My mistake. According to this post the interfaces on your model do not follow the normal naming convention. So wl3.1 appears to be the 2.4GHz guest network which makes more sense.

But now I see you're getting messages on eth10. This post indicates that eth10 is the non-guest 2.4GHz radio. That is similar to the problem reported in this post: https://www.snbforums.com/threads/a...-0-0-6-102_36382-2025-03-12.94092/post-950933

Do you have any other network devices, like AiMesh nodes, access points, repeaters, etc?
 
Last edited:
My mistake. According to this post the interfaces on your model do not follow the normal naming convention. So wl3.1 appears to be the 2.4GHz guest network which makes more sense.

But now I see you're getting messages on eth10. This post indicates that eth10 is the non-guest 2.4GHz radio. That is similar to the problem reported in this post: https://www.snbforums.com/threads/a...-0-0-6-102_36382-2025-03-12.94092/post-950933

Do you have any other network devices, like AiMesh nodes, access points, repeaters, etc?
No AI mesh nodes, access points or repeaters... just the GT-AXE16000

in the meantime I will check out the post..
 
Just an idea if you want to experiment, try disabling "802.11ax / WiFi 6 mode" on the 2.4GHz bands. See if the messages change.
 
Its is already disabled...
 

Attachments

  • Screenshot 2025-07-08 at 20.53.52.png
    Screenshot 2025-07-08 at 20.53.52.png
    102.8 KB · Views: 5
  • Screenshot 2025-07-08 at 20.54.23.png
    Screenshot 2025-07-08 at 20.54.23.png
    94.6 KB · Views: 6

Similar threads

Support SNBForums w/ Amazon

If you'd like to support SNBForums, just use this link and buy anything on Amazon. Thanks!

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!

Staff online

Back
Top