cancel
Showing results for 
Search instead for 
Did you mean: 

GTE-AXE11000 Keeps dropping smart plugs

ironcobra
Level 7
I am having constant issues with my asus router dropping my tp-link smart plugs. It seems looking at the logs that its resetting them every couple of minutes which is causing problems when I try to control them with my echo devices. I have attached a section of my logs over a couple of days showing the constant resets. Any ideas where to start. I did add all 3 of the plugs to the dhcp list giving them static ip addresses and that made no difference.

Jul 20 11:56:35 wlceventd: wlceventd_proc_event(527): eth6: Auth 70:4F:57:9C:79:0E, status: Successful (0), rssi:0
Jul 20 11:56:35 wlceventd: wlceventd_proc_event(556): eth6: Assoc 70:4F:57:9C:79:0E, status: Successful (0), rssi:-65
Jul 20 11:56:40 wlceventd: wlceventd_proc_event(491): eth6: Deauth_ind 40:3F:8C:E8:18:76, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:-71
Jul 20 11:56:40 wlceventd: wlceventd_proc_event(491): eth6: Deauth_ind 40:3F:8C:E8:18:76, status: 0, reason: Unspecified reason (1), rssi:0
Jul 20 11:56:40 wlceventd: wlceventd_proc_event(527): eth6: Auth 40:3F:8C:E8:18:76, status: Successful (0), rssi:0
Jul 20 11:56:40 wlceventd: wlceventd_proc_event(556): eth6: Assoc 40:3F:8C:E8:18:76, status: Successful (0), rssi:-72
Jul 20 11:56:53 wlceventd: wlceventd_proc_event(491): eth6: Deauth_ind 40:3F:8C:E8:1C:02, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:-77
Jul 20 11:56:53 wlceventd: wlceventd_proc_event(491): eth6: Deauth_ind 40:3F:8C:E8:1C:02, status: 0, reason: Unspecified reason (1), rssi:0
Jul 20 11:56:53 wlceventd: wlceventd_proc_event(527): eth6: Auth 40:3F:8C:E8:1C:02, status: Successful (0), rssi:-76
Jul 20 11:56:53 wlceventd: wlceventd_proc_event(556): eth6: Assoc 40:3F:8C:E8:1C:02, status: Successful (0), rssi:-76
Jul 20 11:56:57 wlceventd: wlceventd_proc_event(491): eth6: Deauth_ind 70:4F:57:9C:79:0E, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:-64
Jul 20 11:56:57 wlceventd: wlceventd_proc_event(491): eth6: Deauth_ind 40:3F:8C:E8:1F:AB, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:-66
Jul 20 11:56:57 wlceventd: wlceventd_proc_event(491): eth6: Deauth_ind 40:3F:8C:E8:1F:AB, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:-66
Jul 20 11:56:57 wlceventd: wlceventd_proc_event(491): eth6: Deauth_ind 40:3F:8C:E8:1F:AB, status: 0, reason: Unspecified reason (1), rssi:0
Jul 20 11:56:57 wlceventd: wlceventd_proc_event(527): eth6: Auth 40:3F:8C:E8:1F:AB, status: Successful (0), rssi:0
Jul 20 11:56:57 wlceventd: wlceventd_proc_event(556): eth6: Assoc 40:3F:8C:E8:1F:AB, status: Successful (0), rssi:-66
Jul 20 11:56:57 wlceventd: wlceventd_proc_event(491): eth6: Deauth_ind 70:4F:57:9C:79:0E, status: 0, reason: Unspecified reason (1), rssi:0
Jul 20 11:56:57 wlceventd: wlceventd_proc_event(527): eth6: Auth 70:4F:57:9C:79:0E, status: Successful (0), rssi:-62
Jul 20 11:56:57 wlceventd: wlceventd_proc_event(556): eth6: Assoc 70:4F:57:9C:79:0E, status: Successful (0), rssi:-62
Jul 20 11:57:53 wlceventd: wlceventd_proc_event(491): eth6: Deauth_ind 40:3F:8C:E8:18:76, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:-73
Jul 20 11:57:53 wlceventd: wlceventd_proc_event(491): eth6: Deauth_ind 40:3F:8C:E8:18:76, status: 0, reason: Unspecified reason (1), rssi:0
Jul 20 11:57:53 wlceventd: wlceventd_proc_event(527): eth6: Auth 40:3F:8C:E8:18:76, status: Successful (0), rssi:0
Jul 20 11:57:53 wlceventd: wlceventd_proc_event(556): eth6: Assoc 40:3F:8C:E8:18:76, status: Successful (0), rssi:-74
Jul 20 11:57:57 wlceventd: wlceventd_proc_event(491): eth6: Deauth_ind 40:3F:8C:E8:1C:02, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:-76
Jul 20 11:57:57 wlceventd: wlceventd_proc_event(491): eth6: Deauth_ind 40:3F:8C:E8:1C:02, status: 0, reason: Unspecified reason (1), rssi:0
Jul 20 11:57:57 wlceventd: wlceventd_proc_event(527): eth6: Auth 40:3F:8C:E8:1C:02, status: Successful (0), rssi:0
Jul 20 11:57:57 wlceventd: wlceventd_proc_event(556): eth6: Assoc 40:3F:8C:E8:1C:02, status: Successful (0), rssi:-76
Jul 20 11:58:01 wlceventd: wlceventd_proc_event(491): eth6: Deauth_ind 70:4F:57:9C:79:0E, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:-63
Jul 20 11:58:01 wlceventd: wlceventd_proc_event(491): eth6: Deauth_ind 70:4F:57:9C:79:0E, status: 0, reason: Unspecified reason (1), rssi:0
Jul 20 11:58:01 wlceventd: wlceventd_proc_event(527): eth6: Auth 70:4F:57:9C:79:0E, status: Successful (0), rssi:0
Jul 20 11:58:01 wlceventd: wlceventd_proc_event(556): eth6: Assoc 70:4F:57:9C:79:0E, status: Successful (0), rssi:-63
Jul 20 11:58:40 wlceventd: wlceventd_proc_event(491): eth6: Deauth_ind 40:3F:8C:E8:18:76, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:-74
Jul 20 11:58:40 wlceventd: wlceventd_proc_event(491): eth6: Deauth_ind 40:3F:8C:E8:18:76, status: 0, reason: Unspecified reason (1), rssi:0
Jul 20 11:58:40 wlceventd: wlceventd_proc_event(527): eth6: Auth 40:3F:8C:E8:18:76, status: Successful (0), rssi:-72
Jul 20 11:58:40 wlceventd: wlceventd_proc_event(556): eth6: Assoc 40:3F:8C:E8:18:76, status: Successful (0), rssi:-72
Jul 20 11:58:50 wlceventd: wlceventd_proc_event(491): eth6: Deauth_ind 40:3F:8C:E8:1F:AB, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:-69
Jul 20 11:58:50 wlceventd: wlceventd_proc_event(491): eth6: Deauth_ind 40:3F:8C:E8:1F:AB, status: 0, reason: Unspecified reason (1), rssi:0
Jul 20 11:58:50 wlceventd: wlceventd_proc_event(527): eth6: Auth 40:3F:8C:E8:1F:AB, status: Successful (0), rssi:0
Jul 20 11:58:50 wlceventd: wlceventd_proc_event(556): eth6: Assoc 40:3F:8C:E8:1F:AB, status: Successful (0), rssi:-66
Jul 20 11:58:59 wlceventd: wlceventd_proc_event(491): eth6: Deauth_ind 70:4F:57:9C:79:0E, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:-63
Jul 20 11:58:59 wlceventd: wlceventd_proc_event(491): eth6: Deauth_ind 40:3F:8C:E8:1C:02, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:-75
Jul 20 11:58:59 wlceventd: wlceventd_proc_event(491): eth6: Deauth_ind 70:4F:57:9C:79:0E, status: 0, reason: Unspecified reason (1), rssi:0
Jul 20 11:58:59 wlceventd: wlceventd_proc_event(527): eth6: Auth 70:4F:57:9C:79:0E, status: Successful (0), rssi:0
Jul 20 11:58:59 wlceventd: wlceventd_proc_event(556): eth6: Assoc 70:4F:57:9C:79:0E, status: Successful (0), rssi:-63
Jul 20 11:58:59 wlceventd: wlceventd_proc_event(491): eth6: Deauth_ind 40:3F:8C:E8:1C:02, status: 0, reason: Unspecified reason (1), rssi:0
Jul 20 11:58:59 wlceventd: wlceventd_proc_event(527): eth6: Auth 40:3F:8C:E8:1C:02, status: Successful (0), rssi:0
Jul 20 11:58:59 wlceventd: wlceventd_proc_event(556): eth6: Assoc 40:3F:8C:E8:1C:02, status: Successful (0), rssi:-75
Jul 20 11:59:33 wlceventd: wlceventd_proc_event(491): eth6: Deauth_ind 40:3F:8C:E8:18:76, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:-73
Jul 20 11:59:33 wlceventd: wlceventd_proc_event(491): eth6: Deauth_ind 40:3F:8C:E8:18:76, status: 0, reason: Unspecified reason (1), rssi:0
Jul 20 11:59:33 wlceventd: wlceventd_proc_event(527): eth6: Auth 40:3F:8C:E8:18:76, status: Successful (0), rssi:0
Jul 20 11:59:33 wlceventd: wlceventd_proc_event(556): eth6: Assoc 40:3F:8C:E8:18:76, status: Successful (0), rssi:-72
Jul 20 11:59:37 wlceventd: wlceventd_proc_event(491): eth6: Deauth_ind 40:3F:8C:E8:1C:02, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:-74
Jul 20 11:59:37 wlceventd: wlceventd_proc_event(491): eth6: Deauth_ind 70:4F:57:9C:79:0E, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:-62
Jul 20 11:59:37 wlceventd: wlceventd_proc_event(491): eth6: Deauth_ind 70:4F:57:9C:79:0E, status: 0, reason: Unspecified reason (1), rssi:0
Jul 20 11:59:37 wlceventd: wlceventd_proc_event(527): eth6: Auth 70:4F:57:9C:79:0E, status: Successful (0), rssi:0
Jul 20 11:59:37 wlceventd: wlceventd_proc_event(556): eth6: Assoc 70:4F:57:9C:79:0E, status: Successful (0), rssi:-65
Jul 20 11:59:38 wlceventd: wlceventd_proc_event(491): eth6: Deauth_ind 40:3F:8C:E8:1C:02, status: 0, reason: Disassociated due to inactivity (4), rssi:0
Jul 20 12:00:13 wlceventd: wlceventd_proc_event(527): eth6: Auth 40:3F:8C:E8:1C:02, status: Successful (0), rssi:0
Jul 20 12:00:13 wlceventd: wlceventd_proc_event(556): eth6: Assoc 40:3F:8C:E8:1C:02, status: Successful (0), rssi:-75
Jul 20 12:00:15 wlceventd: wlceventd_proc_event(491): eth6: Deauth_ind 70:4F:57:9C:79:0E, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:-63
Jul 20 12:00:15 wlceventd: wlceventd_proc_event(491): eth6: Deauth_ind 70:4F:57:9C:79:0E, status: 0, reason: Unspecified reason (1), rssi:0
Jul 20 12:00:15 wlceventd: wlceventd_proc_event(527): eth6: Auth 70:4F:57:9C:79:0E, status: Successful (0), rssi:-65
Jul 20 12:00:15 wlceventd: wlceventd_proc_event(556): eth6: Assoc 70:4F:57:9C:79:0E, status: Successful (0), rssi:-65
Jul 20 12:00:20 wlceventd: wlceventd_proc_event(491): eth6: Deauth_ind 40:3F:8C:E8:1F:AB, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:-66
Jul 20 12:00:20 wlceventd: wlceventd_proc_event(491): eth6: Deauth_ind 40:3F:8C:E8:1F:AB, status: 0, reason: Unspecified reason (1), rssi:0
Jul 20 12:00:20 wlceventd: wlceventd_proc_event(527): eth6: Auth 40:3F:8C:E8:1F:AB, status: Successful (0), rssi:0
Jul 20 12:00:20 wlceventd: wlceventd_proc_event(556): eth6: Assoc 40:3F:8C:E8:1F:AB, status: Successful (0), rssi:-66
Jul 20 12:00:25 wlceventd: wlceventd_proc_event(491): eth6: Deauth_ind 40:3F:8C:E8:18:76, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:-74
Jul 20 12:00:25 wlceventd: wlceventd_proc_event(491): eth6: Deauth_ind 40:3F:8C:E8:18:76, status: 0, reason: Unspecified reason (1), rssi:0
Jul 20 12:00:25 wlceventd: wlceventd_proc_event(527): eth6: Auth 40:3F:8C:E8:18:76, status: Successful (0), rssi:0
Jul 20 12:00:25 wlceventd: wlceventd_proc_event(556): eth6: Assoc 40:3F:8C:E8:18:76, status: Successful (0), rssi:-73
Jul 20 12:00:55 wlceventd: wlceventd_proc_event(491): eth6: Deauth_ind 70:4F:57:9C:79:0E, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:-64
Jul 20 12:00:55 wlceventd: wlceventd_proc_event(491): eth6: Deauth_ind 40:3F:8C:E8:1C:02, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:-77
Jul 20 12:00:55 wlceventd: wlceventd_proc_event(491): eth6: Deauth_ind 70:4F:57:9C:79:0E, status: 0, reason: Unspecified reason (1), rssi:0
Jul 20 12:00:55 wlceventd: wlceventd_proc_event(527): eth6: Auth 70:4F:57:9C:79:0E, status: Successful (0), rssi:0
Jul 20 12:00:55 wlceventd: wlceventd_proc_event(491): eth6: Deauth_ind 40:3F:8C:E8:1C:02, status: 0, reason: Unspecified reason (1), rssi:0
Jul 20 12:00:55 wlceventd: wlceventd_proc_event(527): eth6: Auth 40:3F:8C:E8:1C:02, status: Successful (0), rssi:0
Jul 20 12:00:55 wlceventd: wlceventd_proc_event(556): eth6: Assoc 40:3F:8C:E8:1C:02, status: Successful (0), rssi:-73
Jul 20 12:00:55 wlceventd: wlceventd_proc_event(556): eth6: Assoc 70:4F:57:9C:79:0E, status: Successful (0), rssi:-67
5,575 Views
10 REPLIES 10

Saltgrass
Level 13
I will try to look through your logs but since mention it, do you have the new Firmware?
Maximus Z790 Hero,
Intel i9-13900k
Intel BE200

Current version is : 3.0.0.4.386_43986-g0176651

Mine has done this since day 1 and I've owned the AXE11000 since launch. Kasa isnt any help, worst part for me was I had the router plugged into one of these kasa power strips and the kasa device would reboot itself every day around 5AM cutting the power to all the outlets and resetting my router everyday. My only solution was to restrict their internet access, in my case I dont need to control the plugs outside the home, havent had connection issues or resetting since.

I dont understand why asus support isnt responsive with fixing these type of bugs... all they tell me is my hardware is defective. Yeah, my foot. Power users could provide genuinely valuable real world feedback for asus support but noooo

TechGuy42 wrote:
Mine has done this since day 1 and I've owned the AXE11000 since launch. Kasa isnt any help, worst part for me was I had the router plugged into one of these kasa power strips and the kasa device would reboot itself every day around 5AM cutting the power to all the outlets and resetting my router everyday. My only solution was to restrict their internet access, in my case I dont need to control the plugs outside the home, havent had connection issues or resetting since.

I dont understand why asus support isnt responsive with fixing these type of bugs... all they tell me is my hardware is defective. Yeah, my foot. Power users could provide genuinely valuable real world feedback for asus support but noooo


yeah this is unfortunate, the logs are clearly showing whats going on and kasa and asus dont respond to anything. Can you tell me how you restricted there access?

ironcobra wrote:
yeah this is unfortunate, the logs are clearly showing whats going on and kasa and asus dont respond to anything. Can you tell me how you restricted there access?


Open your network map in the router settings, find the kasa devices giving you trouble, there should be a ON/OFF toggle to block internet access

ironcobra wrote:
yeah this is unfortunate, the logs are clearly showing whats going on and kasa and asus dont respond to anything.


It appears your devices are on the 2.4 GHz network, can they use either 5 GHz or ethernet? Any Microwave ovens or wireless Phones around?

The reason for Deauthorizing is always the same, sending station is leaving or has left. This appears to happen around 1 minute apart, +/- 20 seconds.

When they are Deauthorized, they are Authorized again within 1 second.

Since the entire log you attached shows only the eth6 network, do you have any devices on eth7 or eth8 that might behave differently and show in the log?
Maximus Z790 Hero,
Intel i9-13900k
Intel BE200

Saltgrass wrote:
It appears your devices are on the 2.4 GHz network, can they use either 5 GHz or ethernet? Any Microwave ovens or wireless Phones around?

The reason for Deauthorizing is always the same, sending station is leaving or has left. This appears to happen around 1 minute apart, +/- 20 seconds.

When they are Deauthorized, they are Authorized again within 1 second.

Since the entire log you attached shows only the eth6 network, do you have any devices on eth7 or eth8 that might behave differently and show in the log?


No these are the only devices on the log and devices giving me issues.

TechGuy42 wrote:
Open your network map in the router settings, find the kasa devices giving you trouble, there should be a ON/OFF toggle to block internet access


Theres no toggle on that screen only the list

ironcobra wrote:
Theres no toggle on that screen only the list


On the Network Map screen, click the icon above the word "Clients: ##" this will list them on the right side, search or page over to your device and click the device to get the screen with a "Block Internet Access" toggle

89430
89431

Do you have smart connect enabled?

Once I turned this off, I had a couple IOT devices that were having connection problems (as well as an older ipad that simply could not join the wifi at all) all fixed.