ragnaroknroll
Regular Contributor
I have an RT-AX86U main router running Asuswrt Merlin v386.7, which in turn connects to an RT-AC86U AiMesh node running Asuswrt v3.0.0.4.386_48260-gd4c241c. I have recently observed a number of strange wlceventd_proc_event messages filling up my system log, referring to a strange <mac_address>, which I cannot identify, and does not seem to belong to any of my devices. Could anyone please let me know if this is some kind of external brute force attack on my wireless network? Thanks!
Code:
Jun 25 17:50:08 wlceventd: wlceventd_proc_event(505): wl0.2: Auth <mac_address>, status: Successful (0)
Jun 25 17:50:08 wlceventd: wlceventd_proc_event(505): wl0.1: Auth <mac_address>, status: Successful (0)
Jun 25 17:50:08 wlceventd: wlceventd_proc_event(469): wl0.2: Deauth_ind <mac_address>, status: 0, reason: Unspecified reason (1)
Jun 25 17:50:08 wlceventd: wlceventd_proc_event(469): wl0.1: Deauth_ind <mac_address>, status: 0, reason: Unspecified reason (1)
Jun 25 17:50:08 wlceventd: wlceventd_proc_event(505): wl0.1: Auth <mac_address>, status: Successful (0)
Jun 25 17:50:09 wlceventd: wlceventd_proc_event(469): wl0.1: Deauth_ind <mac_address>, status: 0, reason: Unspecified reason (1)
Jun 25 17:50:09 wlceventd: wlceventd_proc_event(505): eth6: Auth <mac_address>, status: Successful (0)
Jun 25 17:50:09 wlceventd: wlceventd_proc_event(469): eth6: Deauth_ind <mac_address>, status: 0, reason: Unspecified reason (1)
Jun 25 17:50:09 wlceventd: wlceventd_proc_event(505): eth6: Auth <mac_address>, status: Successful (0)
Jun 25 17:50:09 wlceventd: wlceventd_proc_event(469): eth6: Deauth_ind <mac_address>, status: 0, reason: Unspecified reason (1)
Jun 25 17:50:09 wlceventd: wlceventd_proc_event(505): eth6: Auth <mac_address>, status: Successful (0)
Jun 25 17:50:09 wlceventd: wlceventd_proc_event(469): eth6: Deauth_ind <mac_address>, status: 0, reason: Unspecified reason (1)
Jun 25 17:50:09 wlceventd: wlceventd_proc_event(505): eth6: Auth <mac_address>, status: Successful (0)
Jun 25 17:50:09 wlceventd: wlceventd_proc_event(469): eth6: Deauth_ind <mac_address>, status: 0, reason: Unspecified reason (1)
Jun 25 17:50:09 wlceventd: wlceventd_proc_event(505): wl0.2: Auth <mac_address>, status: Successful (0)
Jun 25 17:50:09 wlceventd: wlceventd_proc_event(469): wl0.2: Deauth_ind <mac_address>, status: 0, reason: Unspecified reason (1)
Jun 25 17:50:09 wlceventd: wlceventd_proc_event(505): wl0.2: Auth <mac_address>, status: Successful (0)
Jun 25 17:50:11 wlceventd: wlceventd_proc_event(469): wl0.2: Deauth_ind <mac_address>, status: 0, reason: Unspecified reason (1)
Jun 25 17:50:11 wlceventd: wlceventd_proc_event(505): eth6: Auth <mac_address>, status: Successful (0)
Jun 25 17:50:11 wlceventd: wlceventd_proc_event(469): eth6: Deauth_ind <mac_address>, status: 0, reason: Unspecified reason (1)
Jun 25 17:50:11 wlceventd: wlceventd_proc_event(505): eth6: Auth <mac_address>, status: Successful (0)
Jun 25 17:50:11 wlceventd: wlceventd_proc_event(469): eth6: Deauth_ind <mac_address>, status: 0, reason: Unspecified reason (1)
Jun 25 17:50:11 wlceventd: wlceventd_proc_event(505): eth6: Auth <mac_address>, status: Successful (0)
Jun 25 17:50:11 wlceventd: wlceventd_proc_event(469): eth6: Deauth_ind <mac_address>, status: 0, reason: Unspecified reason (1)
Jun 25 17:50:11 wlceventd: wlceventd_proc_event(505): eth6: Auth <mac_address>, status: Successful (0)