Smart Home Community > All Threads > Can't change EP10 wireless network even after factory reset
< All Threads

Can't change EP10 wireless network even after factory reset

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.

Can't change EP10 wireless network even after factory reset

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Can't change EP10 wireless network even after factory reset
Can't change EP10 wireless network even after factory reset
2023-08-14 15:38:50
Model: EP10  
Hardware Version: V1
Firmware Version: 1.0.5

I am trying to move four EP10 smart plugs from my old wireless network SSID to a new one.  I am using the Kasa app on my iPhone 13 Pro.  No matter what I do, I cannot get them to stay connected to the wifi for more than a few hours after initial setup UNLESS I use the old SSID and password; changing either the SSID or password, doing a factory reset, then setup again, they will drop off the wireless after a few hours and not reconnect.

 

Here are the things I have tried to confirm the behavior:

 

CHANGE ONLY THE SSID

  1. Factory reset the EP10 by holding the button on the side for > 10 seconds.
  2. Change the SSID of my wireless access point, keeping the old password and other network details.  Other clients are able to connect to the new SSID fine using the old password and new SSID.
  3. Setup the EP10 using the app.
  4. The EP10 will initially be reachable and responds to commands from the app.
  5. After a few hours, the LED will go orange and the plug no longer responds.  It is not pingable from other devices on the wifi.
  6. A soft reset or unplug/plug cycle will reconnect, but it will drop again after a few more hours.

 

CHANGE ONLY THE PASSWORD

1.  Same as above.

2.  Change only the wifi password, keeping the SSID the same as before.  Other devices work fine after reconfiguration, including other Kasa products.

3 and subsequent steps - same result as before.

 

CHANGE BOTH THE SSID AND PASSWORD

Same result as above.

 

In frustration, I set the SSID and password back to the original on my access point and factory reset the EP10.  It will connect and stay connected for days.

 

Other details:

Encryption and authentication is WPA-PSK with 128-bit AES.  I tried WPA3 but the plug would not connect after initial setup at all.  I don't need to use WPA3 but it was a test.

I've reloaded the Kasa app on my iPhone by removing the app and data, then re-downloading the app and logging in and attempted the same steps above.

Signal level is -50dBm on channel 11.

 

I have successfully reset both two KP115's and four HS103's on this same access point and SSID regardless of password with no trouble.  They stay connected without issue after reconfiguration.  This only happens with the model EP10.

 

I've turned on tracing in my access point and see the following sequence of messages over and over while the EP10 attempts to authenticate:

2023/08/05 13:04:49.052058015 {wncd_x_R0-0}{2}: [client-orch-sm] [9933]: (note): MAC: 3460.f997.c89b  Association received. BSSID 2c57.4186.8443, WLAN ibteepee, Slot 0 AP 2c57.4186.8440, APA4B2-3902-50D8, Site tag default-site-tag, Policy tag default-policy-tag, Policy profile VLAN 1, Switching Local
2023/08/05 13:04:49.052393536 {wncd_x_R0-0}{2}: [client-orch-state] [9933]: (note): MAC: 3460.f997.c89b  Client state transition: S_CO_INIT -> S_CO_ASSOCIATING
2023/08/05 13:04:49.053223067 {wncd_x_R0-0}{2}: [dot11] [9933]: (note): MAC: 3460.f997.c89b  Association success. AID 12, Roaming = False, WGB = False, 11r = False, 11w = False Fast roam = False
2023/08/05 13:04:49.053542911 {wncd_x_R0-0}{2}: [client-orch-state] [9933]: (note): MAC: 3460.f997.c89b  Client state transition: S_CO_ASSOCIATING -> S_CO_L2_AUTH_IN_PROGRESS
2023/08/05 13:04:49.053622338 {wncd_x_R0-0}{2}: [client-auth] [9933]: (note): MAC: 3460.f997.c89b  L2 Authentication initiated. method PSK, Policy VLAN 1, AAA override = 0, NAC = 0
2023/08/05 13:04:49.057502702 {wncd_x_R0-0}{2}: [ewlc-infra-evq] [9933]: (note): Authentication Success. Resolved Policy bitmap:11 for client 3460.f997.c89b 
2023/08/05 13:04:49.058047858 {wncd_x_R0-0}{2}: [client-auth] [9933]: (note): MAC: 3460.f997.c89b  ADD MOBILE sent. Client state flags: 0x1  BSSID: MAC: 2c57.4186.8443 capwap IFID: 0x90000005, Add mobiles sent: 1
2023/08/05 13:04:52.063257909 {wncd_x_R0-0}{2}: [client-keymgmt] [9933]: (ERR): MAC: 3460.f997.c89b  Keymgmt: Failed to eapol key m1 retransmit failure. Max retries for M1 over
2023/08/05 13:04:52.063451243 {wncd_x_R0-0}{2}: [client-orch-sm] [9933]: (note): MAC: 3460.f997.c89b  Client delete initiated. Reason: CO_CLIENT_DELETE_REASON_KEY_XCHNG_TIMEOUT, details: , fsm-state transition 00|00|00|00|00|00|00|00|00|00|00|00|00|00|00|00|00|00|00|00|00|00|00|00|00|00|00|01|07|15|1e|27|
2023/08/05 13:04:52.063641816 {wncd_x_R0-0}{2}: [client-orch-sm] [9933]: (note): MAC: 3460.f997.c89b  Delete mobile payload sent for BSSID: 2c57.4186.8443 WTP mac: 2c57.4186.8440 slot id: 0 
2023/08/05 13:04:52.063659420 {wncd_x_R0-0}{2}: [client-orch-state] [9933]: (note): MAC: 3460.f997.c89b  Client state transition: S_CO_L2_AUTH_IN_PROGRESS -> S_CO_DELETE_IN_PROGRESS
2023/08/05 13:04:52.064162649 {wncd_x_R0-0}{2}: [sanet-shim-translate] [9933]: (note): MAC: 3460.f997.c89b  Session manager disconnect event called, session label: 0x390008d3
2023/08/05 13:04:52.066061139 {wncd_x_R0-0}{2}: [client-orch-state] [9933]: (note): MAC: 3460.f997.c89b  Client state transition: S_CO_DELETE_IN_PROGRESS -> S_CO_DELETED
2023/08/05 13:04:58.512526709 {wncd_x_R0-0}{2}: [client-orch-sm] [9933]: (note): MAC: 3460.f997.c89b  Association received. BSSID 2c57.4186.8443, WLAN ibteepee, Slot 0 AP 2c57.4186.8440, APA4B2-3902-50D8, Site tag default-site-tag, Policy tag default-policy-tag, Policy profile VLAN 1, Switching Local
2023/08/05 13:04:58.512882542 {wncd_x_R0-0}{2}: [client-orch-state] [9933]: (note): MAC: 3460.f997.c89b  Client state transition: S_CO_INIT -> S_CO_ASSOCIATING
2023/08/05 13:04:58.513694678 {wncd_x_R0-0}{2}: [dot11] [9933]: (note): MAC: 3460.f997.c89b  Association success. AID 12, Roaming = False, WGB = False, 11r = False, 11w = False Fast roam = False
2023/08/05 13:04:58.514018584 {wncd_x_R0-0}{2}: [client-orch-state] [9933]: (note): MAC: 3460.f997.c89b  Client state transition: S_CO_ASSOCIATING -> S_CO_L2_AUTH_IN_PROGRESS
2023/08/05 13:04:58.514102751 {wncd_x_R0-0}{2}: [client-auth] [9933]: (note): MAC: 3460.f997.c89b  L2 Authentication initiated. method PSK, Policy VLAN 1, AAA override = 0, NAC = 0
2023/08/05 13:04:58.518267907 {wncd_x_R0-0}{2}: [ewlc-infra-evq] [9933]: (note): Authentication Success. Resolved Policy bitmap:11 for client 3460.f997.c89b 
2023/08/05 13:04:58.518821865 {wncd_x_R0-0}{2}: [client-auth] [9933]: (note): MAC: 3460.f997.c89b  ADD MOBILE sent. Client state flags: 0x1  BSSID: MAC: 2c57.4186.8443 capwap IFID: 0x90000005, Add mobiles sent: 1
2023/08/05 13:05:01.523492020 {wncd_x_R0-0}{2}: [client-keymgmt] [9933]: (ERR): MAC: 3460.f997.c89b  Keymgmt: Failed to eapol key m1 retransmit failure. Max retries for M1 over
2023/08/05 13:05:01.523687489 {wncd_x_R0-0}{2}: [client-orch-sm] [9933]: (note): MAC: 3460.f997.c89b  Client delete initiated. Reason: CO_CLIENT_DELETE_REASON_KEY_XCHNG_TIMEOUT, details: , fsm-state transition 00|00|00|00|00|00|00|00|00|00|00|00|00|00|00|00|00|00|00|00|00|00|00|00|00|00|00|01|07|15|1e|27|
2023/08/05 13:05:01.523881083 {wncd_x_R0-0}{2}: [client-orch-sm] [9933]: (note): MAC: 3460.f997.c89b  Delete mobile payload sent for BSSID: 2c57.4186.8443 WTP mac: 2c57.4186.8440 slot id: 0 
2023/08/05 13:05:01.523898843 {wncd_x_R0-0}{2}: [client-orch-state] [9933]: (note): MAC: 3460.f997.c89b  Client state transition: S_CO_L2_AUTH_IN_PROGRESS -> S_CO_DELETE_IN_PROGRESS
2023/08/05 13:05:01.524439937 {wncd_x_R0-0}{2}: [sanet-shim-translate] [9933]: (note): MAC: 3460.f997.c89b  Session manager disconnect event called, session label: 0x440008d9
2023/08/05 13:05:01.527956760 {wncd_x_R0-0}{2}: [client-orch-state] [9933]: (note): MAC: 3460.f997.c89b  Client state transition: S_CO_DELETE_IN_PROGRESS -> S_CO_DELETED

  0      
 
  0      
 
#1
Options
6 Reply
Re:Can't change EP10 wireless network even after factory reset
2023-08-16 01:08:02

  @IronBow 

 

What's the model of your router and access point? Please provide a simple drawing of your network topology.

 

What was your previous SSID and password like? How long was the password? Did they include numbers, characters, or symbols? If symbols were used, which ones specifically?

 

To better help with this case, we have reported the issue to the support engineers, they will likely reach out to you via email to continue to troubleshoot your issue. Please check your email box and confirm.

▶ Landscape Mode - Tapo App for Pad ▶ Share Your Pet Story. Win Free Tapo Care! ▶ Smart Action 2.0 Explore and meet the next level home automation.
  0  
  0  
#2
Options
Re:Can't change EP10 wireless network even after factory reset
2023-08-16 02:27:22

  @Wayne-TP 

 

I am using a pfSense router and two Cisco 9130AXi-Bs running IOS-XE 17.11.1. The router connects to the 9130s by an HP 48 port switch.  One of the access points is much closer than the other and so it associates with that one on channel 11.

 

My old SSID was three letters with an 8 character password.   My new SSID is 8 characters.  I have tried passwords ranging from 8 characters (by only changing 1 character from the old password) to 20 characters.  I use only letters and numbers in my wifi passwords.

 

The MACs of my EP10s:

3460.f997.cb0c

3460.f997.b3b0

3460.f997.c89b

3460.f997.cb06

 

I'm configuring monitoring now for these to see exactly how long they will stay connected before dropping off.

  0  
  0  
#3
Options
Re:Can't change EP10 wireless network even after factory reset
2023-08-17 06:38:38

  @IronBow 

 

Thank you for the update. The information will be forwarded to the support engineer. 

▶ Landscape Mode - Tapo App for Pad ▶ Share Your Pet Story. Win Free Tapo Care! ▶ Smart Action 2.0 Explore and meet the next level home automation.
  0  
  0  
#4
Options
Re:Can't change EP10 wireless network even after factory reset
2023-08-18 14:13:14

  @Wayne-TP 

 

I have installed the new firmware on three of the four devices and reset them all.  I still have monitoring configured to watch them and logging turned on for those devices on the access points.  Thank you!

  0  
  0  
#5
Options
Re:Can't change EP10 wireless network even after factory reset
2023-08-21 03:01:31

@Wayne-TP 

 

I have been running the beta firmware for about 48 hours now.  The EP10 devices have all stayed connected to the network.  My monitoring does notice that they disassociate at the end of the session timeout and take about 20 seconds to reconnect.  The log from my access point is below.  I'm not sure if this is a normal behavior.  I'm going to increase my session timeout to at least an hour - that will help.  Having them stay connected is a major improvement!

 

2023/08/18 19:56:10.059610113 {wncd_x_R0-0}{1}: [client-auth] [9094]: (info): MAC: 3460.f997.b3b0  Client auth-interface state transition: S_AUTHIF_PSK_AUTH_DONE -> S_SANET_DELETED
2023/08/18 19:56:10.059749227 {wncd_x_R0-0}{1}: [client-orch-sm] [9094]: (info): MAC: 3460.f997.b3b0  Deleting the client, reason: 24, CO_CLIENT_DELETE_REASON_SESSION_TIMEOUT, Client state S_CO_RUN
2023/08/18 19:56:10.059875163 {wncd_x_R0-0}{1}: [client-orch-sm] [9094]: (note): MAC: 3460.f997.b3b0  Client delete initiated. Reason: CO_CLIENT_DELETE_REASON_SESSION_TIMEOUT, details: , fsm-state transition 00|00|00|00|00|00|00|00|00|00|00|00|00|00|00|00|01|07|15|1a|1b|2c|37|46|48|4a|4c|51|60|62|83|ab|
2023/08/18 19:56:10.060119589 {wncd_x_R0-0}{1}: [client-orch-sm] [9094]: (note): MAC: 3460.f997.b3b0  Delete mobile payload sent for BSSID: 2c57.4186.8440 WTP mac: 2c57.4186.8440 slot id: 0 
2023/08/18 19:56:10.060153026 {wncd_x_R0-0}{1}: [client-orch-state] [9094]: (note): MAC: 3460.f997.b3b0  Client state transition: S_CO_RUN -> S_CO_DELETE_IN_PROGRESS
2023/08/18 19:56:10.060290838 {wncd_x_R0-0}{1}: [ewlc-qos-voice] [9094]: (info): MAC: 3460.f997.b3b0 Successfully freed the bw for sip client
2023/08/18 19:56:10.060482660 {wncd_x_R0-0}{1}: [multicast-main] [9094]: (info): MAC: 3460.f997.b3b0  No Flex/Fabric main record exists for client
2023/08/18 19:56:10.060492400 {wncd_x_R0-0}{1}: [rog-proxy-capwap] [9094]: (debug): Managed client state notification: client left run state: 3460.f997.b3b0
2023/08/18 19:56:10.060559014 {wncd_x_R0-0}{1}: [mdns] [9094]: (debug): MDNS_DB: mdns client record not found: 3460.f997.b3b0
2023/08/18 19:56:10.061148281 {wncd_x_R0-0}{1}: [client-orch-sm] [9094]: (ERR): MAC: 3460.f997.b3b0  vlan_mode_api: Sanet policy returned failure
2023/08/18 19:56:10.061277499 {wncd_x_R0-0}{1}: [client-iplearn] [9094]: (info): MAC: 3460.f997.b3b0  IP-learn state transition: S_IPLEARN_COMPLETE -> S_IPLEARN_DELETE_IN_PROGRESS
2023/08/18 19:56:10.061506769 {wncd_x_R0-0}{1}: [dpath_svc] [9094]: (note): MAC: 3460.f997.b3b0 Client datapath entry deleted for ifid 0x9000001f
2023/08/18 19:56:10.061546612 {wncd_x_R0-0}{1}: [mm-transition] [9094]: (info): MAC: 3460.f997.b3b0 MMIF FSM transition: S_MA_LOCAL -> S_MA_DELETE_PROCESSED_TR on E_MA_CO_DELETE_RCVD
2023/08/18 19:56:10.061694893 {wncd_x_R0-0}{1}: [mm-client] [9094]: (info): MAC: 3460.f997.b3b0 Invalid transmitter ip in build client context
2023/08/18 19:56:10.061962443 {wncd_x_R0-0}{1}: [client-auth] [9094]: (info): MAC: 3460.f997.b3b0  Client auth-interface state transition: S_SANET_DELETED -> S_AUTHIF_DELETED
2023/08/18 19:56:10.062010516 {wncd_x_R0-0}{1}: [dot11] [9094]: (info): MAC: 3460.f997.b3b0  Total length of Deauth/Disassoc: 2
2023/08/18 19:56:10.062234629 {wncd_x_R0-0}{1}: [dot11] [9094]: (info): MAC: 3460.f997.b3b0  Sent disassoc to client, disassoc reason: 252, CLIENT_DEAUTH_REASON_ADMIN_RESET delete reason: 24, CO_CLIENT_DELETE_REASON_SESSION_TIMEOUT.
2023/08/18 19:56:10.062242390 {wncd_x_R0-0}{1}: [dot11] [9094]: (info): MAC: 3460.f997.b3b0  Total length of Deauth/Disassoc: 2
2023/08/18 19:56:10.062376087 {wncd_x_R0-0}{1}: [dot11] [9094]: (info): MAC: 3460.f997.b3b0  Sent deauth to client, deauth reason: 252, CLIENT_DEAUTH_REASON_ADMIN_RESET delete reason: 24, CO_CLIENT_DELETE_REASON_SESSION_TIMEOUT.
2023/08/18 19:56:10.062669158 {wncd_x_R0-0}{1}: [dot11] [9094]: (info): MAC: 3460.f997.b3b0  DOT11 state transition: S_DOT11_ASSOCIATED -> S_DOT11_DELETED
2023/08/18 19:56:10.063629361 {wncd_x_R0-0}{1}: [mm-client] [9094]: (debug): MAC: 3460.f997.b3b0 Received handoff_end, sub type: 0 of XID (0) from (WNCD[0])
2023/08/18 19:56:10.064158524 {wncd_x_R0-0}{1}: [client-orch-state] [9094]: (note): MAC: 3460.f997.b3b0  Client state transition: S_CO_DELETE_IN_PROGRESS -> S_CO_DELETED
2023/08/18 19:56:11.060981358 {rogued_R0-0}{1}: [rogue-core] [9472]: (debug): managed client 3460.f997.b3b0 state: not run. Not a rogue.
2023/08/18 19:56:30.905605726 {wncd_x_R0-0}{1}: [client-orch-sm] [9094]: (note): MAC: 3460.f997.b3b0  Association received. BSSID 2c57.4186.8440, WLAN svt, Slot 0 AP 2c57.4186.8440, secondfloor, Site tag default-site-tag, Policy tag default-policy-tag, Policy profile VLAN 32, Switching Local
2023/08/18 19:56:30.905724475 {wncd_x_R0-0}{1}: [client-orch-sm] [9094]: (debug): MAC: 3460.f997.b3b0  Received Dot11 association request. Processing started,SSID: svt, Policy profile: VLAN 32, AP Name: secondfloor, Ap Mac Address: 2c57.4186.8440BSSID MAC0000.0000.0000wlan ID: 1RSSI: -52, SNR: 45
2023/08/18 19:56:30.905975255 {wncd_x_R0-0}{1}: [client-orch-state] [9094]: (note): MAC: 3460.f997.b3b0  Client state transition: S_CO_INIT -> S_CO_ASSOCIATING
2023/08/18 19:56:30.906462805 {wncd_x_R0-0}{1}: [dot11-validate] [9094]: (info): MAC: 3460.f997.b3b0  Dot11 ie validate ext/supp rates. Validation Passed for Supported rates  radio_type 1
2023/08/18 19:56:30.906472440 {wncd_x_R0-0}{1}: [dot11-validate] [9094]: (info): MAC: 3460.f997.b3b0  WiFi direct: Dot11 validate P2P IE. P2P IE not present.
2023/08/18 19:56:30.906688116 {wncd_x_R0-0}{1}: [dot11] [9094]: (debug): MAC: 3460.f997.b3b0  dot11 send association response. Framing association response with resp_status_code: 0
2023/08/18 19:56:30.906690355 {wncd_x_R0-0}{1}: [dot11] [9094]: (info): MAC: 3460.f997.b3b0  Dot11 capability privacy bit set TRUE
2023/08/18 19:56:30.906699522 {wncd_x_R0-0}{1}: [dot11] [9094]: (debug): MAC: 3460.f997.b3b0  Dot11 Capability info byte1 11, byte2: 14
2023/08/18 19:56:30.906772907 {wncd_x_R0-0}{1}: [dot11-frame] [9094]: (info): MAC: 3460.f997.b3b0  WiFi direct: skip build Assoc Resp with P2P IE: Wifi direct policy disabled
2023/08/18 19:56:30.907046343 {wncd_x_R0-0}{1}: [dot11] [9094]: (info): MAC: 3460.f997.b3b0  dot11 send association response. Sending assoc response of length: 108 with resp_status_code: 0, DOT11_STATUS: DOT11_STATUS_SUCCESS
2023/08/18 19:56:30.907059937 {wncd_x_R0-0}{1}: [dot11] [9094]: (note): MAC: 3460.f997.b3b0  Association success. AID 6, Roaming = False, WGB = False, 11r = False, 11w = False Fast roam = False
2023/08/18 19:56:30.907099832 {wncd_x_R0-0}{1}: [dot11] [9094]: (info): MAC: 3460.f997.b3b0  DOT11 state transition: S_DOT11_INIT -> S_DOT11_ASSOCIATED
2023/08/18 19:56:30.907247227 {wncd_x_R0-0}{1}: [client-orch-sm] [9094]: (debug): MAC: 3460.f997.b3b0  Station Dot11 association is successful. 
2023/08/18 19:56:30.907352174 {wncd_x_R0-0}{1}: [client-orch-sm] [9094]: (debug): MAC: 3460.f997.b3b0  Starting L2 authentication. Bssid in state machine:2c57.4186.8440  Bssid in request is:2c57.4186.8440
2023/08/18 19:56:30.907399414 {wncd_x_R0-0}{1}: [client-orch-state] [9094]: (note): MAC: 3460.f997.b3b0  Client state transition: S_CO_ASSOCIATING -> S_CO_L2_AUTH_IN_PROGRESS
2023/08/18 19:56:30.907510246 {wncd_x_R0-0}{1}: [client-auth] [9094]: (note): MAC: 3460.f997.b3b0  L2 Authentication initiated. method PSK, Policy VLAN 32, AAA override = 0, NAC = 0
2023/08/18 19:56:30.907691756 {wncd_x_R0-0}{1}: [auth-mgr] [9094]: (info): [3460.f997.b3b0:capwap_9000000a] Session Start event called from SANET-SHIM, vlan: 0
2023/08/18 19:56:30.907732276 {wncd_x_R0-0}{1}: [auth-mgr] [9094]: (info): [3460.f997.b3b0:capwap_9000000a] Wireless session sequence, create context with method No method
2023/08/18 19:56:30.907770922 {wncd_x_R0-0}{1}: [auth-mgr-feat_wireless] [9094]: (info): [3460.f997.b3b0:capwap_9000000a]  - authc_list: Not present under wlan configuration
2023/08/18 19:56:30.907775401 {wncd_x_R0-0}{1}: [auth-mgr-feat_wireless] [9094]: (info): [3460.f997.b3b0:capwap_9000000a]  - authz_list: Not present under wlan configuration
2023/08/18 19:56:30.907825297 {wncd_x_R0-0}{1}: [client-auth] [9094]: (info): MAC: 3460.f997.b3b0  Client auth-interface state transition: S_AUTHIF_INIT -> S_AUTHIF_AWAIT_PSK_AUTH_START_RESP
2023/08/18 19:56:30.908051910 {wncd_x_R0-0}{1}: [auth-mgr] [9094]: (info): [3460.f997.b3b0:unknown] auth mgr attr add/change notification is received for attr iif-id(952)
2023/08/18 19:56:30.908122795 {wncd_x_R0-0}{1}: [auth-mgr] [9094]: (info): [3460.f997.b3b0:capwap_9000000a] auth mgr attr add/change notification is received for attr swbidb(1263)
2023/08/18 19:56:30.908199565 {wncd_x_R0-0}{1}: [auth-mgr] [9094]: (info): [3460.f997.b3b0:capwap_9000000a] auth mgr attr add/change notification is received for attr aaa-unique-id(220)
2023/08/18 19:56:30.908252846 {wncd_x_R0-0}{1}: [auth-mgr] [9094]: (info): [3460.f997.b3b0:capwap_9000000a] auth mgr attr add/change notification is received for attr iif-id(952)
2023/08/18 19:56:30.908283315 {wncd_x_R0-0}{1}: [auth-mgr] [9094]: (info): [3460.f997.b3b0:capwap_9000000a] Retrieved Client IIF ID 0x580005bf
2023/08/18 19:56:30.908346908 {wncd_x_R0-0}{1}: [auth-mgr] [9094]: (info): [3460.f997.b3b0:capwap_9000000a] auth mgr attr add/change notification is received for attr audit-session-id(819)
2023/08/18 19:56:30.908368992 {wncd_x_R0-0}{1}: [auth-mgr] [9094]: (info): [3460.f997.b3b0:capwap_9000000a] Allocated audit session id 0000000000025D9524D71469
2023/08/18 19:56:30.908963936 {wncd_x_R0-0}{1}: [auth-mgr] [9094]: (info): [3460.f997.b3b0:capwap_9000000a] Device type found in cache TP-LINK-Device
2023/08/18 19:56:30.908981019 {wncd_x_R0-0}{1}: [auth-mgr] [9094]: (info): [3460.f997.b3b0:capwap_9000000a] Device type for the session is detected as TP-LINK-Device and old device-type not classified earlier & Device name for the session is detected as EP10 and old device-name not classified earlier & Old protocol map 0 and new is 41
2023/08/18 19:56:30.909163831 {wncd_x_R0-0}{1}: [svm] [9094]: (info): SVM_INFO: Applying Svc Templ wlan_svc_VLAN 32 (ML:NONE)
2023/08/18 19:56:30.909774556 {wncd_x_R0-0}{1}: [auth-mgr-feat_wireless] [9094]: (info): [0000.0000.0000:unknown] retrieving vlanid from name failed
2023/08/18 19:56:30.909810181 {wncd_x_R0-0}{1}: [auth-mgr] [9094]: (info): [3460.f997.b3b0:capwap_9000000a] auth mgr attr add/change notification is received for attr vlan-id(965)
2023/08/18 19:56:30.909871327 {wncd_x_R0-0}{1}: [epm] [9094]: (info): [3460.f997.b3b0:capwap_9000000a] Vlan tag name is 32, pref is 1048575 vlan num is 32
2023/08/18 19:56:30.909978982 {wncd_x_R0-0}{1}: [epm] [9094]: (info): [3460.f997.b3b0:capwap_9000000a] Feature (EPM Vlan PLUG-IN) has been started (status Success)
2023/08/18 19:56:30.910015440 {wncd_x_R0-0}{1}: [auth-mgr] [9094]: (info): [3460.f997.b3b0:capwap_9000000a] SM Reauth Plugin: Received valid timeout = 3600, effective timeout = 3600
2023/08/18 19:56:30.910074138 {wncd_x_R0-0}{1}: [epm] [9094]: (info): [3460.f997.b3b0:capwap_9000000a] Feature (SM Reauth PLUG-IN) has been started (status Success)
2023/08/18 19:56:30.910194398 {wncd_x_R0-0}{1}: [svm] [9094]: (info): SVM_INFO: Response of epm is SYNC with return code Success
2023/08/18 19:56:30.910329137 {wncd_x_R0-0}{1}: [auth-mgr] [9094]: (info): [3460.f997.b3b0:capwap_9000000a] Raising ext evt Template Activated (9) on this session, client (unknown) (0)
2023/08/18 19:56:30.910589656 {wncd_x_R0-0}{1}: [llbridge-main] [9094]: (debug): MAC: 3460.f997.b3b0  Link-local bridging not enabled for this client, not checking VLAN validity
2023/08/18 19:56:30.910724082 {wncd_x_R0-0}{1}: [auth-mgr] [9094]: (info): [3460.f997.b3b0:capwap_9000000a] auth mgr attr add/change notification is received for attr auth-domain(954)
2023/08/18 19:56:30.910835957 {wncd_x_R0-0}{1}: [auth-mgr] [9094]: (info): [3460.f997.b3b0:capwap_9000000a] Raised event AUTHZ_SUCCESS (11)
2023/08/18 19:56:30.910849394 {wncd_x_R0-0}{1}: [auth-mgr] [9094]: (info): [3460.f997.b3b0:capwap_9000000a] Context changing state from 'Idle' to 'Authz Success'
2023/08/18 19:56:30.910861738 {wncd_x_R0-0}{1}: [auth-mgr] [9094]: (info): [3460.f997.b3b0:capwap_9000000a] Authorized open auth session for 3460.f997.b3b0
2023/08/18 19:56:30.932504947 {wncd_x_R0-0}{1}: [auth-mgr] [9094]: (info): [3460.f997.b3b0:capwap_9000000a] SM will not send event Template Activated to PRE for 0x85000D9A
2023/08/18 19:56:30.932561145 {wncd_x_R0-0}{1}: [client-auth] [9094]: (info): MAC: 3460.f997.b3b0  Client auth-interface state transition: S_AUTHIF_AWAIT_PSK_AUTH_START_RESP -> S_AUTHIF_PSK_AUTH_PENDING
2023/08/18 19:56:30.932583488 {wncd_x_R0-0}{1}: [ewlc-infra-evq] [9094]: (note): Authentication Success. Resolved Policy bitmap:11 for client 3460.f997.b3b0 
2023/08/18 19:56:30.932820883 {wncd_x_R0-0}{1}: [ewlc-qos-client] [9094]: (info): MAC: 3460.f997.b3b0 Client QoS add mobile cb
2023/08/18 19:56:30.933144110 {wncd_x_R0-0}{1}: [ewlc-qos-client] [9094]: (info): MAC: 3460.f997.b3b0 No QoS PM Name or QoS Level received from SANet for pm_dir:0. Check client is fastlane, otherwise set pm name to none
2023/08/18 19:56:30.933168225 {wncd_x_R0-0}{1}: [ewlc-qos-client] [9094]: (info): MAC: 3460.f997.b3b0 No QoS PM Name or QoS Level received from SANet for pm_dir:1. Check client is fastlane, otherwise set pm name to none
2023/08/18 19:56:30.933270307 {wncd_x_R0-0}{1}: [client-auth] [9094]: (note): MAC: 3460.f997.b3b0  ADD MOBILE sent. Client state flags: 0x1  BSSID: MAC: 2c57.4186.8440 capwap IFID: 0x9000000a, Add mobiles sent: 1
2023/08/18 19:56:30.933304838 {wncd_x_R0-0}{1}: [client-auth] [9094]: (info): MAC: 3460.f997.b3b0  Client auth-interface state transition: S_AUTHIF_PSK_AUTH_PENDING -> S_AUTHIF_ADD_MOBILE_ACK_WAIT_KM
2023/08/18 19:56:30.933516243 {wncd_x_R0-0}{1}: [auth-mgr] [9094]: (info): [3460.f997.b3b0:capwap_9000000a] Device type for the session is detected as TP-LINK-Device and old TP-LINK-Device & Device name for the session is detected as TP-LINK CORPORATION LIMITED and old EP10 & Old protocol map 41 and new is 1
2023/08/18 19:56:30.933551243 {wncd_x_R0-0}{1}: [auth-mgr] [9094]: (info): [3460.f997.b3b0:capwap_9000000a] auth mgr attr add/change notification is received for attr dc-profile-name(1130)
2023/08/18 19:56:30.951408641 {wncd_x_R0-0}{1}: [client-auth] [9094]: (info): MAC: 3460.f997.b3b0  Client auth-interface state transition: S_AUTHIF_ADD_MOBILE_ACK_WAIT_KM -> S_AUTHIF_PSK_AUTH_KEY_XCHNG_PENDING
2023/08/18 19:56:30.951665514 {wncd_x_R0-0}{1}: [client-keymgmt] [9094]: (info): MAC: 3460.f997.b3b0  EAP key M1 Sent successfully
2023/08/18 19:56:30.951679212 {wncd_x_R0-0}{1}: [client-keymgmt] [9094]: (info): MAC: 3460.f997.b3b0  Client key-mgmt state transition: S_INITPMK -> S_PTK_START
2023/08/18 19:56:30.957834385 {wncd_x_R0-0}{1}: [client-keymgmt] [9094]: (info): MAC: 3460.f997.b3b0   M2 Status: EAP key M2 validation success
2023/08/18 19:56:30.958120842 {wncd_x_R0-0}{1}: [client-keymgmt] [9094]: (info): MAC: 3460.f997.b3b0  EAP key M3 Sent successfully
2023/08/18 19:56:30.958126623 {wncd_x_R0-0}{1}: [client-keymgmt] [9094]: (info): MAC: 3460.f997.b3b0  Client key-mgmt state transition: S_PTK_START -> S_PTKINITNEGOTIATING
2023/08/18 19:56:30.961968945 {wncd_x_R0-0}{1}: [client-keymgmt] [9094]: (info): MAC: 3460.f997.b3b0  M4 Status: EAP key M4 validation is successful
2023/08/18 19:56:30.961979674 {wncd_x_R0-0}{1}: [client-keymgmt] [9094]: (note): MAC: 3460.f997.b3b0  EAP Key management successful. AKM:PSK Cipher:CCMP WPA Version: WPA2
2023/08/18 19:56:30.961998007 {wncd_x_R0-0}{1}: [client-keymgmt] [9094]: (info): MAC: 3460.f997.b3b0  Client key-mgmt state transition: S_PTKINITNEGOTIATING -> S_PTKINITDONE
2023/08/18 19:56:30.962564150 {wncd_x_R0-0}{1}: [client-auth] [9094]: (note): MAC: 3460.f997.b3b0  L2 PSK Authentication Success. EAP type: NA, Resolved VLAN: 32, Audit Session id: 0000000000025D9524D71469
2023/08/18 19:56:30.962602431 {wncd_x_R0-0}{1}: [client-auth] [9094]: (info): MAC: 3460.f997.b3b0  Client auth-interface state transition: S_AUTHIF_PSK_AUTH_KEY_XCHNG_PENDING -> S_AUTHIF_PSK_AUTH_DONE
2023/08/18 19:56:30.962779409 {wncd_x_R0-0}{1}: [client-orch-sm] [9094]: (debug): MAC: 3460.f997.b3b0  L2 Authentication of station is successful., L3 Authentication : 0
2023/08/18 19:56:30.962971908 {wncd_x_R0-0}{1}: [client-orch-sm] [9094]: (note): MAC: 3460.f997.b3b0  Mobility discovery triggered. Client mode: Flex - Local Switching
2023/08/18 19:56:30.962980241 {wncd_x_R0-0}{1}: [client-orch-state] [9094]: (note): MAC: 3460.f997.b3b0  Client state transition: S_CO_L2_AUTH_IN_PROGRESS -> S_CO_MOBILITY_DISCOVERY_IN_PROGRESS
2023/08/18 19:56:30.963052845 {wncd_x_R0-0}{1}: [mm-transition] [9094]: (info): MAC: 3460.f997.b3b0 MMIF FSM transition: S_MA_INIT -> S_MA_MOBILITY_DISCOVERY_PROCESSED_TR on E_MA_MOBILITY_DISCOVERY
2023/08/18 19:56:30.963183469 {wncd_x_R0-0}{1}: [mm-client] [9094]: (info): MAC: 3460.f997.b3b0 Invalid transmitter ip in build client context
2023/08/18 19:56:30.963452009 {wncd_x_R0-0}{1}: [mm-client] [9094]: (debug): MAC: 3460.f997.b3b0 Received mobile_announce, sub type: 0 of XID (0) from (WNCD[0])
2023/08/18 19:56:30.963625133 {wncd_x_R0-0}{1}: [mm-client] [9094]: (debug): MAC: 3460.f997.b3b0 Add MCC by tdl mac: client_ifid 0x9000001f is assigned to client
2023/08/18 19:56:30.963764924 {wncd_x_R0-0}{1}: [mm-client] [9094]: (debug): MAC: 0000.0000.0000 Sending mobile_announce_nak of XID (0) to (WNCD[0])
2023/08/18 19:56:30.963847111 {wncd_x_R0-0}{1}: [mm-client] [9094]: (debug): MAC: 3460.f997.b3b0 Received mobile_announce_nak, sub type: 1 of XID (0) from (WNCD[0])
2023/08/18 19:56:30.963955079 {wncd_x_R0-0}{1}: [mm-transition] [9094]: (info): MAC: 3460.f997.b3b0 MMIF FSM transition: S_MA_INIT_WAIT_ANNOUNCE_RSP -> S_MA_NAK_PROCESSED_TR on E_MA_NAK_RCVD
2023/08/18 19:56:30.963971850 {wncd_x_R0-0}{1}: [mm-client] [9094]: (info): MAC: 3460.f997.b3b0 Roam type changed - None -> None
2023/08/18 19:56:30.964003881 {wncd_x_R0-0}{1}: [mm-client] [9094]: (info): MAC: 3460.f997.b3b0 Mobility role changed -  Unassoc -> Local
2023/08/18 19:56:30.964155703 {wncd_x_R0-0}{1}: [mm-client] [9094]: (note): MAC: 3460.f997.b3b0 Mobility Successful. Roam Type None, Sub Roam Type MM_SUB_ROAM_TYPE_NONE, Client IFID: 0x9000001f, Client Role: Local PoA: 0x9000000a PoP: 0x0
2023/08/18 19:56:30.964215286 {wncd_x_R0-0}{1}: [client-orch-sm] [9094]: (debug): MAC: 3460.f997.b3b0  Processing mobility response from MMIF. Client ifid: 0x9000001f, roam type: None, client role: Local
2023/08/18 19:56:30.964668096 {wncd_x_R0-0}{1}: [dot1x] [9094]: (info): [0000.0000.0000:capwap_9000000a] Couldn't find the supplicant in the list
2023/08/18 19:56:30.964741794 {wncd_x_R0-0}{1}: [ewlc-qos-client] [9094]: (info): MAC: 3460.f997.b3b0 Client QoS add mobile cb
2023/08/18 19:56:30.964826481 {wncd_x_R0-0}{1}: [ewlc-qos-client] [9094]: (info): MAC: 3460.f997.b3b0 No QoS PM Name or QoS Level received from SANet for pm_dir:0. Check client is fastlane, otherwise set pm name to none
2023/08/18 19:56:30.964857783 {wncd_x_R0-0}{1}: [ewlc-qos-client] [9094]: (info): MAC: 3460.f997.b3b0 No QoS PM Name or QoS Level received from SANet for pm_dir:1. Check client is fastlane, otherwise set pm name to none
2023/08/18 19:56:30.964922418 {wncd_x_R0-0}{1}: [ewlc-qos-client] [9094]: (info): MAC: 3460.f997.b3b0 Build AAA QoS Params for addMobile: aaa_avgdtus:0, aaa_avgrtdtus:0, aaa_bstdtus:0, aaa_bstrtdtus:0, aaa_avgdtds:0, aaa_avgrtdtds:0, aaa_bstdtds:0, aaa_bstrtdtds:0, aaa_sig:1431655765
2023/08/18 19:56:30.964932209 {wncd_x_R0-0}{1}: [ewlc-qos-client] [9094]: (info): MAC: 3460.f997.b3b0 Qos rate-limit parameters encoded successfully in addMobile payload from qos addMobile callback
2023/08/18 19:56:30.965024344 {wncd_x_R0-0}{1}: [client-auth] [9094]: (note): MAC: 3460.f997.b3b0  ADD MOBILE sent. Client state flags: 0x2  BSSID: MAC: 2c57.4186.8440 capwap IFID: 0x9000000a, Add mobiles sent: 1
2023/08/18 19:56:30.965152052 {wncd_x_R0-0}{1}: [client-orch-state] [9094]: (note): MAC: 3460.f997.b3b0  Client state transition: S_CO_MOBILITY_DISCOVERY_IN_PROGRESS -> S_CO_DPATH_PLUMB_IN_PROGRESS
2023/08/18 19:56:30.965679653 {wncd_x_R0-0}{1}: [dot11] [9094]: (note): MAC: 3460.f997.b3b0  Client datapath entry params - ssid:svt,slot_id:0 bssid ifid: 0x0, radio_ifid: 0x90000009, wlan_ifid: 0xf0400001
2023/08/18 19:56:30.965778871 {wncd_x_R0-0}{1}: [llbridge-main] [9094]: (debug): MAC: 3460.f997.b3b0  Link-local bridging not enabled for this client, not checking VLAN validity
2023/08/18 19:56:30.965809027 {wncd_x_R0-0}{1}: [llbridge-main] [9094]: (debug): MAC: 3460.f997.b3b0  Link Local Bridging not enabled for client
2023/08/18 19:56:30.965813819 {wncd_x_R0-0}{1}: [ewlc-qos-client] [9094]: (info): MAC: 3460.f997.b3b0 Client QoS dpath create params
2023/08/18 19:56:30.965861162 {wncd_x_R0-0}{1}: [avc-afc] [9094]: (debug): AVC enabled for client 3460.f997.b3b0 
2023/08/18 19:56:30.965956110 {wncd_x_R0-0}{1}: [dpath_svc] [9094]: (note): MAC: 3460.f997.b3b0 Client datapath entry created for ifid 0x9000001f
2023/08/18 19:56:30.966129390 {wncd_x_R0-0}{1}: [client-orch-state] [9094]: (note): MAC: 3460.f997.b3b0  Client state transition: S_CO_DPATH_PLUMB_IN_PROGRESS -> S_CO_IP_LEARN_IN_PROGRESS
2023/08/18 19:56:30.966373347 {wncd_x_R0-0}{1}: [client-iplearn] [9094]: (info): MAC: 3460.f997.b3b0  IP-learn state transition: S_IPLEARN_INIT -> S_IPLEARN_IN_PROGRESS
2023/08/18 19:56:30.969959472 {wncd_x_R0-0}{1}: [client-auth] [9094]: (info): MAC: 3460.f997.b3b0  Client auth-interface state transition: S_AUTHIF_PSK_AUTH_DONE -> S_AUTHIF_PSK_AUTH_DONE
2023/08/18 19:56:31.417363107 {wncd_x_R0-0}{1}: [sisf-packet] [9094]: (info): RX: DHCPv4 from interface capwap_9000000a on vlan 32 Src MAC: 3460.f997.b3b0 Dst MAC: ffff.ffff.ffff src_ip: 0.0.0.0, dst_ip: 255.255.255.255, BOOTPREQUEST, SISF_DHCPDISCOVER, giaddr: 0.0.0.0, yiaddr: 0.0.0.0, CMAC: 3460.f997.b3b0 
2023/08/18 19:56:31.417533315 {wncd_x_R0-0}{1}: [auth-mgr] [9094]: (info): [3460.f997.b3b0:capwap_9000000a] auth mgr attr add/change notification is received for attr dhcp-option(1126)
2023/08/18 19:56:31.417604408 {wncd_x_R0-0}{1}: [auth-mgr-feat_acct] [9094]: (info): [3460.f997.b3b0:capwap_9000000a] SM Notified attribute Add/Update dhcp-option 
2023/08/18 19:56:31.438942671 {wncd_x_R0-0}{1}: [auth-mgr] [9094]: (info): [3460.f997.b3b0:capwap_9000000a] Device type for the session is detected as TP-LINK-Device and old TP-LINK-Device & Device name for the session is detected as TP-LINK CORPORATION LIMITED and old EP10 & Old protocol map 41 and new is 9
2023/08/18 19:56:31.438975171 {wncd_x_R0-0}{1}: [auth-mgr] [9094]: (info): [3460.f997.b3b0:capwap_9000000a] auth mgr attr add/change notification is received for attr dc-profile-name(1130)
2023/08/18 19:56:31.440205581 {wncd_x_R0-0}{1}: [sisf-packet] [9094]: (info): RX: DHCPv4 from interface capwap_9000000a on vlan 32 Src MAC: 3460.f997.b3b0 Dst MAC: ffff.ffff.ffff src_ip: 0.0.0.0, dst_ip: 255.255.255.255, BOOTPREQUEST, SISF_DHCPDISCOVER, giaddr: 0.0.0.0, yiaddr: 0.0.0.0, CMAC: 3460.f997.b3b0 
2023/08/18 19:56:31.440581152 {wncd_x_R0-0}{1}: [sisf-packet] [9094]: (info): RX: DHCPv4 from interface capwap_9000000a on vlan 32 Src MAC: 0050.56a1.403b Dst MAC: 3460.f997.b3b0 src_ip: 192.168.32.1, dst_ip: 192.168.32.35, BOOTPREPLY, SISF_DHCPOFFER, giaddr: 0.0.0.0, yiaddr: 192.168.32.35, CMAC: 3460.f997.b3b0 
2023/08/18 19:56:31.440895837 {wncd_x_R0-0}{1}: [sisf-packet] [9094]: (info): RX: DHCPv4 from interface capwap_9000000a on vlan 32 Src MAC: 0050.56a1.403b Dst MAC: 3460.f997.b3b0 src_ip: 192.168.32.1, dst_ip: 192.168.32.35, BOOTPREPLY, SISF_DHCPOFFER, giaddr: 0.0.0.0, yiaddr: 192.168.32.35, CMAC: 3460.f997.b3b0 
2023/08/18 19:56:31.441427813 {wncd_x_R0-0}{1}: [sisf-packet] [9094]: (info): RX: DHCPv4 from interface capwap_9000000a on vlan 32 Src MAC: 3460.f997.b3b0 Dst MAC: ffff.ffff.ffff src_ip: 0.0.0.0, dst_ip: 255.255.255.255, BOOTPREQUEST, SISF_DHCPREQUEST, giaddr: 0.0.0.0, yiaddr: 0.0.0.0, CMAC: 3460.f997.b3b0 
2023/08/18 19:56:31.441561667 {wncd_x_R0-0}{1}: [auth-mgr] [9094]: (info): [3460.f997.b3b0:capwap_9000000a] auth mgr attr add/change notification is received for attr dhcp-option(1126)
2023/08/18 19:56:31.441628698 {wncd_x_R0-0}{1}: [auth-mgr-feat_acct] [9094]: (info): [3460.f997.b3b0:capwap_9000000a] SM Notified attribute Add/Update dhcp-option 
2023/08/18 19:56:31.463662894 {wncd_x_R0-0}{1}: [auth-mgr] [9094]: (info): [3460.f997.b3b0:capwap_9000000a] Device type for the session is detected as TP-LINK-Device and old TP-LINK-Device & Device name for the session is detected as EP10 and old EP10 & Old protocol map 41 and new is 9
2023/08/18 19:56:31.463696019 {wncd_x_R0-0}{1}: [auth-mgr] [9094]: (info): [3460.f997.b3b0:capwap_9000000a] auth mgr attr add/change notification is received for attr dc-profile-name(1130)
2023/08/18 19:56:31.464640649 {wncd_x_R0-0}{1}: [client-iplearn] [9094]: (note): MAC: 3460.f997.b3b0  Client IP learn successful. Method: IP Snooping IP: 192.168.32.35
2023/08/18 19:56:31.464703878 {wncd_x_R0-0}{1}: [auth-mgr] [9094]: (info): [3460.f997.b3b0:capwap_9000000a] auth mgr attr add/change notification is received for attr addr(8)
2023/08/18 19:56:31.464869033 {wncd_x_R0-0}{1}: [auth-mgr-feat_acct] [9094]: (info): [3460.f997.b3b0:capwap_9000000a] SM Notified attribute Add/Update addr 192.168.32.35
2023/08/18 19:56:31.465547415 {wncd_x_R0-0}{1}: [client-iplearn] [9094]: (info): MAC: 3460.f997.b3b0  IP-learn state transition: S_IPLEARN_IN_PROGRESS -> S_IPLEARN_COMPLETE
2023/08/18 19:56:31.465703664 {wncd_x_R0-0}{1}: [client-orch-sm] [9094]: (debug): MAC: 3460.f997.b3b0  Received ip learn response. method: IPLEARN_METHOD_IP_SNOOPING
2023/08/18 19:56:31.466003402 {wncd_x_R0-0}{1}: [aaa-attr-inf] [9094]: (info): [ Applied attribute :bsn-vlan-interface-name   0 "32" ]
2023/08/18 19:56:31.466009287 {wncd_x_R0-0}{1}: [aaa-attr-inf] [9094]: (info): [ Applied attribute :             timeout   0 3600 (0xe10) ]
2023/08/18 19:56:31.466138453 {wncd_x_R0-0}{1}: [ewlc-qos-client] [9094]: (info): MAC: 3460.f997.b3b0 Client QoS run state handler
2023/08/18 19:56:31.466206786 {wncd_x_R0-0}{1}: [rog-proxy-capwap] [9094]: (debug): Managed client RUN state notification: 3460.f997.b3b0
2023/08/18 19:56:31.466240900 {wncd_x_R0-0}{1}: [mdns] [9094]: (debug): MDNS_ROAM: mDNS current bssid and old wto mac
2023/08/18 19:56:31.466245171 {wncd_x_R0-0}{1}: [mdns] [9094]: (debug): MDNS_ROAM: mDNS old bssid and old wto mac
2023/08/18 19:56:31.466255588 {wncd_x_R0-0}{1}: [mdns] [9094]: (debug): MDNS_UPN: notification flag 0x0, is set to FALSE
2023/08/18 19:56:31.466274650 {wncd_x_R0-0}{1}: [mdns] [9094]: (debug): MDNS_DB: mdns client record not found: 3460.f997.b3b0
2023/08/18 19:56:31.466374545 {wncd_x_R0-0}{1}: [client-orch-state] [9094]: (note): MAC: 3460.f997.b3b0  Client state transition: S_CO_IP_LEARN_IN_PROGRESS -> S_CO_RUN
2023/08/18 19:56:31.466599128 {wncd_x_R0-0}{1}: [llbridge-main] [9094]: (debug): MAC: 3460.f997.b3b0  Link-local bridging not enabled for this client, not checking VLAN validity
2023/08/18 19:56:31.466649908 {wncd_x_R0-0}{1}: [llbridge-main] [9094]: (debug): MAC: 3460.f997.b3b0  Link Local Bridging not enabled for client
2023/08/18 19:56:31.466654908 {wncd_x_R0-0}{1}: [ewlc-qos-client] [9094]: (info): MAC: 3460.f997.b3b0 Client QoS dpath run params
2023/08/18 19:56:31.466688242 {wncd_x_R0-0}{1}: [avc-afc] [9094]: (debug): AVC enabled for client 3460.f997.b3b0 
2023/08/18 19:56:31.467354644 {wncd_x_R0-0}{1}: [sisf-packet] [9094]: (info): RX: DHCPv4 from interface capwap_9000000a on vlan 32 Src MAC: 0050.56a1.403b Dst MAC: 3460.f997.b3b0 src_ip: 192.168.32.1, dst_ip: 192.168.32.35, BOOTPREPLY, SISF_DHCPACK, giaddr: 0.0.0.0, yiaddr: 192.168.32.35, CMAC: 3460.f997.b3b0 
2023/08/18 19:56:31.467528133 {wncd_x_R0-0}{1}: [client-iplearn] [9094]: (info): MAC: 3460.f997.b3b0  iplearn receive client learn method update. Prev method (IP Snooping) Cur method (DHCP)
2023/08/18 19:56:31.467530320 {wncd_x_R0-0}{1}: [client-iplearn] [9094]: (info): MAC: 3460.f997.b3b0  Client IP learn method update successful. Method: DHCP IP: 192.168.32.35
2023/08/18 19:56:31.467850995 {wncd_x_R0-0}{1}: [client-iplearn] [9094]: (info): MAC: 3460.f997.b3b0  IP-learn state transition: S_IPLEARN_COMPLETE -> S_IPLEARN_COMPLETE
2023/08/18 19:56:31.468468023 {wncd_x_R0-0}{1}: [sisf-packet] [9094]: (info): RX: DHCPv4 from interface capwap_9000000a on vlan 32 Src MAC: 0050.56a1.403b Dst MAC: 3460.f997.b3b0 src_ip: 192.168.32.1, dst_ip: 192.168.32.35, BOOTPREPLY, SISF_DHCPACK, giaddr: 0.0.0.0, yiaddr: 192.168.32.35, CMAC: 3460.f997.b3b0 
2023/08/18 19:56:32.157523608 {wncd_x_R0-0}{1}: [sisf-packet] [9094]: (info): RX: ARP from interface capwap_9000000a on vlan 32 Source MAC: 3460.f997.b3b0 Dest MAC: ffff.ffff.ffff ARP REQUEST, ARP sender MAC: 3460.f997.b3b0 ARP target MAC: 0000.0000.0000 ARP sender IP: 192.168.32.35, ARP target IP: 192.168.32.35, 
2023/08/18 19:56:32.466555483 {rogued_R0-0}{1}: [rogue-core] [9472]: (debug): managed client 3460.f997.b3b0 state: run. Not a rogue.
2023/08/18 19:56:32.648387879 {wncd_x_R0-0}{1}: [sisf-packet] [9094]: (info): RX: ARP from interface capwap_9000000a on vlan 32 Source MAC: 3460.f997.b3b0 Dest MAC: ffff.ffff.ffff ARP REQUEST, ARP sender MAC: 3460.f997.b3b0 ARP target MAC: 0000.0000.0000 ARP sender IP: 192.168.32.35, ARP target IP: 192.168.32.35, 
2023/08/18 19:56:33.648493661 {wncd_x_R0-0}{1}: [sisf-packet] [9094]: (info): RX: ARP from interface capwap_9000000a on vlan 32 Source MAC: 3460.f997.b3b0 Dest MAC: ffff.ffff.ffff ARP REQUEST, ARP sender MAC: 3460.f997.b3b0 ARP target MAC: 0000.0000.0000 ARP sender IP: 192.168.32.35, ARP target IP: 192.168.32.35, 
2023/08/18 19:56:34.648356372 {wncd_x_R0-0}{1}: [sisf-packet] [9094]: (info): RX: ARP from interface capwap_9000000a on vlan 32 Source MAC: 3460.f997.b3b0 Dest MAC: ffff.ffff.ffff ARP REQUEST, ARP sender MAC: 3460.f997.b3b0 ARP target MAC: 0000.0000.0000 ARP sender IP: 192.168.32.35, ARP target IP: 192.168.32.35, 

  0  
  0  
#6
Options
Re:Can't change EP10 wireless network even after factory reset
2023-08-23 12:04:26

  @IronBow 

 

 

Based on the behavior of the plug reconnecting to WiFi, this phenomenon appears to be normal. The smart plug is not a high-traffic device, so if data transmission does not reach the set threshold within the specified timeframe, the session timeout will be calculated as usual. Once the timeout period expires, the device will need to reestablish the connection.

▶ Landscape Mode - Tapo App for Pad ▶ Share Your Pet Story. Win Free Tapo Care! ▶ Smart Action 2.0 Explore and meet the next level home automation.
  0  
  0  
#7
Options

Information

Helpful: 0

Views: 1133

Replies: 6

Related Articles
EP10 smartplug stopped working, can't find network
689 0
Need wireless switch to control EP10
214 0
Kasa EP10
1585 2
Kasa EP10
104 0
EP10's not discoverable in Home Assistant
650 0
connecting an EP10 mini smart plug at a second home on an android phone
568 0
About Us
Press
Copyright © TP-Link Systems Inc. All rights reserved.