Wireless Access

Reply
Frequent Contributor I
Posts: 64
Registered: ‎01-27-2014

client disassociates after connection

Hi.

I'm running controller 7210 (ArubaOS 6.3.1.10) and I've got issue with one client (Android) that cannot connect to WLAN network. It looks like the client disassociates as soon as it gets connected. Below is debug from "show log user-debug all".

 

Jan 29 13:44:50 :501109:  <NOTI> |AP 24:de:c6:cf:e4:7d@192.168.17.34 stm|  Auth request: 1c:7b:21:6c:19:b3: AP 192.168.17.34-24:de:c6:7e:6d:12-24:de:c6:cf:e4:7d auth_alg 0
Jan 29 13:44:50 :501065:  <DBUG> |AP 24:de:c6:cf:e4:7d@192.168.17.34 stm|  remove_stale_sta 2445: client 1c:7b:21:6c:19:b3 not in stale hash table
Jan 29 13:44:50 :501065:  <DBUG> |AP 24:de:c6:cf:e4:7d@192.168.17.34 stm|  auth_alg_notification: Sent sta (1c:7b:21:6c:19:b3) auth_alg(0) to sw
Jan 29 13:44:50 :501093:  <NOTI> |AP 24:de:c6:cf:e4:7d@192.168.17.34 stm|  Auth success: 1c:7b:21:6c:19:b3: AP 192.168.17.34-24:de:c6:7e:6d:12-24:de:c6:cf:e4:7d
Jan 29 13:44:50 :501095:  <NOTI> |stm|  Assoc request @ 13:44:50.256211: 1c:7b:21:6c:19:b3 (SN 2763): AP 192.168.17.34-24:de:c6:7e:6d:12-24:de:c6:cf:e4:7d
Jan 29 13:44:50 :501095:  <NOTI> |AP 24:de:c6:cf:e4:7d@192.168.17.34 stm|  Assoc request @ 13:44:50.253669: 1c:7b:21:6c:19:b3 (SN 2763): AP 192.168.17.34-24:de:c6:7e:6d:12-24:de:c6:cf:e4:7d
Jan 29 13:44:50 :501100:  <NOTI> |stm|  Assoc success @ 13:44:50.257987: 1c:7b:21:6c:19:b3: AP 192.168.17.34-24:de:c6:7e:6d:12-24:de:c6:cf:e4:7d
Jan 29 13:44:50 :522035:  <INFO> |authmgr|  MAC=1c:7b:21:6c:19:b3 Station UP: BSSID=24:de:c6:7e:6d:12 ESSID=ZoneC VLAN=17 AP-name=24:de:c6:cf:e4:7d
Jan 29 13:44:50 :522077:  <DBUG> |authmgr|  MAC=1c:7b:21:6c:19:b3 ingress 0x0x10222 (tunnel 546), u_encr 32, m_encr 2056, slotport 0x0x2100 , type: local, FW mode: 0, AP IP: 0.0.0.0 mdie 1 ft_complete 0
Jan 29 13:44:50 :501100:  <NOTI> |AP 24:de:c6:cf:e4:7d@192.168.17.34 stm|  Assoc success @ 13:44:50.255465: 1c:7b:21:6c:19:b3: AP 192.168.17.34-24:de:c6:7e:6d:12-24:de:c6:cf:e4:7d
Jan 29 13:44:50 :522264:  <DBUG> |authmgr|  "MAC:1c:7b:21:6c:19:b3: Allocating UUID: 15.
Jan 29 13:44:50 :522258:  <DBUG> |authmgr|  "VDR - Add to history of user user 1c:7b:21:6c:19:b3 vlan 0 derivation_type Reset VLANs for Station up index 0.
Jan 29 13:44:50 :522255:  <DBUG> |authmgr|  "VDR - set vlan in user for 1c:7b:21:6c:19:b3 vlan 203 fwdmode 0 derivation_type Default VLAN.
Jan 29 13:44:50 :522258:  <DBUG> |authmgr|  "VDR - Add to history of user user 1c:7b:21:6c:19:b3 vlan 203 derivation_type Default VLAN index 1.
Jan 29 13:44:50 :522255:  <DBUG> |authmgr|  "VDR - set vlan in user for 1c:7b:21:6c:19:b3 vlan 203 fwdmode 0 derivation_type Current VLAN updated.
Jan 29 13:44:50 :522258:  <DBUG> |authmgr|  "VDR - Add to history of user user 1c:7b:21:6c:19:b3 vlan 203 derivation_type Current VLAN updated index 2.
Jan 29 13:44:50 :522246:  <DBUG> |authmgr|  Idle timeout should be driven by STM for MAC 1c:7b:21:6c:19:b3.
Jan 29 13:44:50 :522254:  <DBUG> |authmgr|  VDR - mac 1c:7b:21:6c:19:b3 rolename guest fwdmode 0 derivation_type Initial Role Contained vp not present.
Jan 29 13:44:50 :522258:  <DBUG> |authmgr|  "VDR - Add to history of user user 1c:7b:21:6c:19:b3 vlan 0 derivation_type Reset Role Based VLANs index 3.
Jan 29 13:44:50 :524124:  <DBUG> |authmgr|  dot1x_supplicant_up(): MAC:1c:7b:21:6c:19:b3, pmkid_present:False, pmkid:N/A
Jan 29 13:44:50 :522255:  <DBUG> |authmgr|  "VDR - set vlan in user for 1c:7b:21:6c:19:b3 vlan 203 fwdmode 0 derivation_type Current VLAN updated.
Jan 29 13:44:50 :522258:  <DBUG> |authmgr|  "VDR - Add to history of user user 1c:7b:21:6c:19:b3 vlan 203 derivation_type Current VLAN updated index 4.
Jan 29 13:44:50 :522260:  <DBUG> |authmgr|  "VDR - Cur VLAN updated 1c:7b:21:6c:19:b3 mob 0 inform 1 remote 0 wired 0 defvlan 203 exportedvlan 0 curvlan 203.
Jan 29 13:44:50 :522050:  <INFO> |authmgr|  MAC=1c:7b:21:6c:19:b3,IP=N/A User data downloaded to datapath, new Role=guest/3, bw Contract=0/0, reason=layer 2 event driven download, idle-timeout=300
Jan 29 13:44:50 :522242:  <DBUG> |authmgr|  MAC=1c:7b:21:6c:19:b3 Station Created Update MMS: BSSID=24:de:c6:7e:6d:12 ESSID=ZoneC VLAN=17 AP-name=24:de:c6:cf:e4:7d
Jan 29 13:44:50 :501102:  <NOTI> |stm|  Disassoc from sta: 1c:7b:21:6c:19:b3: AP 192.168.17.34-24:de:c6:7e:6d:12-24:de:c6:cf:e4:7d Reason Unspecified Failure
Jan 29 13:44:50 :522036:  <INFO> |authmgr|  MAC=1c:7b:21:6c:19:b3 Station DN: BSSID=24:de:c6:7e:6d:12 ESSID=ZoneC VLAN=17 AP-name=24:de:c6:cf:e4:7d
Jan 29 13:44:50 :501102:  <NOTI> |AP 24:de:c6:cf:e4:7d@192.168.17.34 stm|  Disassoc from sta: 1c:7b:21:6c:19:b3: AP 192.168.17.34-24:de:c6:7e:6d:12-24:de:c6:cf:e4:7d Reason Unspecified Failure
Jan 29 13:44:50 :522234:  <DBUG> |authmgr|  Setting idle timer for user 1c:7b:21:6c:19:b3 to 300 seconds (idle timeout: 300 ageout: 0).
Jan 29 13:44:50 :501000:  <DBUG> |AP 24:de:c6:cf:e4:7d@192.168.17.34 stm|  Station 1c:7b:21:6c:19:b3: Clearing state
Jan 29 13:44:50 :501065:  <DBUG> |AP 24:de:c6:cf:e4:7d@192.168.17.34 stm|  store_stale_sta 2342: sta 1c:7b:21:6c:19:b3 saved to stale_sta_hash_table
Jan 29 13:44:50 :522244:  <DBUG> |authmgr|  MAC=1c:7b:21:6c:19:b3 Station Deleted Update MMS
Jan 29 13:44:50 :522004:  <DBUG> |authmgr|  1c:7b:21:6c:19:b3: station datapath entry deleted
Jan 29 13:44:50 :522265:  <DBUG> |authmgr|  "MAC:1c:7b:21:6c:19:b3: Deallocating UUID: 15.
Jan 29 13:44:50 :501000:  <DBUG> |stm|  Station 1c:7b:21:6c:19:b3: Clearing state
Jan 29 13:44:57 :501106:  <NOTI> |AP 24:de:c6:cf:e4:7d@192.168.17.34 stm|  Deauth to sta: 1c:7b:21:6c:19:b3: Ageout AP 192.168.17.34-24:de:c6:7e:6d:12-24:de:c6:cf:e4:7d handle_sapcp
Jan 29 13:45:17 :501105:  <NOTI> |stm|  Deauth from sta: 1c:7b:21:6c:19:b3: AP 192.168.17.34-24:de:c6:7e:6d:12-24:de:c6:cf:e4:7d Reason STA has left and is deauthenticated
Jan 29 13:45:17 :501065:  <DBUG> |AP 24:de:c6:cf:e4:7d@192.168.17.34 stm|  group_resend_ageout_sta 13713: Resend ageout of client 1c:7b:21:6c:19:b3 to sw STM
Jan 29 13:45:17 :501044:  <NOTI> |stm|  Station 1c:7b:21:6c:19:b3: No authentication found trying to de-authenticate to BSSID 24:de:c6:7e:6d:12 on AP 24:de:c6:cf:e4:7d
Jan 29 13:45:17 :501065:  <DBUG> |AP 24:de:c6:cf:e4:7d@192.168.17.34 stm|  remove_stale_sta 2455: sta 1c:7b:21:6c:19:b3 is freed and removed from stale_sta_hash_table
Jan 29 13:45:32 :501106:  <NOTI> |AP 24:de:c6:cf:e4:7d@192.168.17.34 stm|  Deauth to sta: 1c:7b:21:6c:19:b3: Ageout AP 192.168.17.34-24:de:c6:7e:6d:12-24:de:c6:cf:e4:7d handle_sapcp
Jan 29 13:46:12 :501106:  <NOTI> |AP 24:de:c6:cf:e4:7d@192.168.17.34 stm|  Deauth to sta: 1c:7b:21:6c:19:b3: Ageout AP 192.168.17.34-24:de:c6:7e:6d:12-24:de:c6:cf:e4:7d handle_sapcp

 Any ideas what might be preventing client from connection?

Valued Contributor II
Posts: 804
Registered: ‎12-01-2014

Re: client disassociates after connection

Hi Friend,

 

Similarly can you share the output of " show auth-tracebuf count 100".

 

it will help us to identify some issues.

 

Please feel free for any further query on this.

Cheers,
Venu Puduchery,
[Is my post helped you ? Give Kudos :) ]
Frequent Contributor I
Posts: 64
Registered: ‎01-27-2014

Re: client disassociates after connection

Hello.

Below is the output.

 

Jan 30 10:13:17  station-up             *  1c:7b:21:6c:19:b3  24:de:c6:7e:6d:10  -  -    wpa2 psk aes
Jan 30 10:13:17  wpa2-key1             <-  1c:7b:21:6c:19:b3  24:de:c6:7e:6d:10  -  117
Jan 30 10:13:17  wpa2-key2             ->  1c:7b:21:6c:19:b3  24:de:c6:7e:6d:10  -  240
Jan 30 10:13:17  wpa2-key3             <-  1c:7b:21:6c:19:b3  24:de:c6:7e:6d:10  -  303
Jan 30 10:13:17  wpa2-key4             ->  1c:7b:21:6c:19:b3  24:de:c6:7e:6d:10  -  95
Jan 30 10:13:17  station-down           *  1c:7b:21:6c:19:b3  24:de:c6:7e:6d:10  -  -
Jan 30 10:13:19  station-up             *  1c:7b:21:6c:19:b3  24:de:c6:7e:6d:18  -  -    wpa2 psk aes
Jan 30 10:13:19  wpa2-key1             <-  1c:7b:21:6c:19:b3  24:de:c6:7e:6d:18  -  117
Jan 30 10:13:19  wpa2-key2             ->  1c:7b:21:6c:19:b3  24:de:c6:7e:6d:18  -  240
Jan 30 10:13:19  wpa2-key3             <-  1c:7b:21:6c:19:b3  24:de:c6:7e:6d:18  -  303
Jan 30 10:13:19  wpa2-key4             ->  1c:7b:21:6c:19:b3  24:de:c6:7e:6d:18  -  95
Jan 30 10:15:13  station-down           *  1c:7b:21:6c:19:b3  24:de:c6:7e:6d:18  -  -
Jan 30 10:16:32  station-up             *  1c:7b:21:6c:19:b3  24:de:c6:7e:6d:1e  -  -    wpa2 psk aes
Jan 30 10:16:32  wpa2-key1             <-  1c:7b:21:6c:19:b3  24:de:c6:7e:6d:1e  -  117
Jan 30 10:16:32  wpa2-key2             ->  1c:7b:21:6c:19:b3  24:de:c6:7e:6d:1e  -  240
Jan 30 10:16:32  wpa2-key3             <-  1c:7b:21:6c:19:b3  24:de:c6:7e:6d:1e  -  303
Jan 30 10:16:32  wpa2-key4             ->  1c:7b:21:6c:19:b3  24:de:c6:7e:6d:1e  -  95

 

Frequent Contributor I
Posts: 64
Registered: ‎01-27-2014

Re: client disassociates after connection

Hello.

Below is the output.

 

Jan 30 10:43:38  station-up             *  1c:7b:21:6c:19:b3  24:de:c6:7c:e1:10  -  -    wpa2 psk aes
Jan 30 10:43:38  wpa2-key1             <-  1c:7b:21:6c:19:b3  24:de:c6:7c:e1:10  -  117
Jan 30 10:43:38  wpa2-key2             ->  1c:7b:21:6c:19:b3  24:de:c6:7c:e1:10  -  119
Jan 30 10:43:38  wpa2-key3             <-  1c:7b:21:6c:19:b3  24:de:c6:7c:e1:10  -  175
Jan 30 10:43:38  wpa2-key4             ->  1c:7b:21:6c:19:b3  24:de:c6:7c:e1:10  -  95
Jan 30 10:47:54  station-down           *  1c:7b:21:6c:19:b3  24:de:c6:7c:e1:10  -  -
Jan 30 10:48:32  station-up             *  1c:7b:21:6c:19:b3  24:de:c6:7c:e1:11  -  -    wpa2 psk aes
Jan 30 10:48:32  wpa2-key1             <-  1c:7b:21:6c:19:b3  24:de:c6:7c:e1:11  -  117
Jan 30 10:48:32  wpa2-key2             ->  1c:7b:21:6c:19:b3  24:de:c6:7c:e1:11  -  119
Jan 30 10:48:32  wpa2-key3             <-  1c:7b:21:6c:19:b3  24:de:c6:7c:e1:11  -  175
Jan 30 10:48:32  wpa2-key4             ->  1c:7b:21:6c:19:b3  24:de:c6:7c:e1:11  -  95
Jan 30 10:54:28  station-down           *  1c:7b:21:6c:19:b3  24:de:c6:7c:e1:11  -  -
Jan 30 10:54:28  station-up             *  1c:7b:21:6c:19:b3  24:de:c6:7c:e1:10  -  -    wpa2 psk aes
Jan 30 10:54:28  wpa2-key1             <-  1c:7b:21:6c:19:b3  24:de:c6:7c:e1:10  -  117
Jan 30 10:54:28  wpa2-key2             ->  1c:7b:21:6c:19:b3  24:de:c6:7c:e1:10  -  119
Jan 30 10:54:28  wpa2-key3             <-  1c:7b:21:6c:19:b3  24:de:c6:7c:e1:10  -  175
Jan 30 10:54:28  wpa2-key4             ->  1c:7b:21:6c:19:b3  24:de:c6:7c:e1:10  -  95
Jan 30 10:59:10  station-up             *  1c:7b:21:6c:19:b3  24:de:c6:7c:e1:10  -  -    wpa2 psk aes
Jan 30 10:59:10  wpa2-key1             <-  1c:7b:21:6c:19:b3  24:de:c6:7c:e1:10  -  117
Jan 30 10:59:11  station-down           *  1c:7b:21:6c:19:b3  24:de:c6:7c:e1:10  -  -
Jan 30 10:59:12  station-up             *  1c:7b:21:6c:19:b3  24:de:c6:7c:e1:10  -  -    wpa2 psk aes
Jan 30 10:59:12  wpa2-key1             <-  1c:7b:21:6c:19:b3  24:de:c6:7c:e1:10  -  117
Jan 30 10:59:12  wpa2-key2             ->  1c:7b:21:6c:19:b3  24:de:c6:7c:e1:10  -  119
Jan 30 10:59:12  wpa2-key3             <-  1c:7b:21:6c:19:b3  24:de:c6:7c:e1:10  -  175
Jan 30 10:59:12  wpa2-key4             ->  1c:7b:21:6c:19:b3  24:de:c6:7c:e1:10  -  95
Jan 30 11:01:07  station-up             *  1c:7b:21:6c:19:b3  24:de:c6:7c:e1:10  -  -    wpa2 psk aes
Jan 30 11:01:07  wpa2-key1             <-  1c:7b:21:6c:19:b3  24:de:c6:7c:e1:10  -  117
Jan 30 11:01:07  wpa2-key2             ->  1c:7b:21:6c:19:b3  24:de:c6:7c:e1:10  -  119
Jan 30 11:01:07  wpa2-key3             <-  1c:7b:21:6c:19:b3  24:de:c6:7c:e1:10  -  175
Jan 30 11:01:07  wpa2-key4             ->  1c:7b:21:6c:19:b3  24:de:c6:7c:e1:10  -  95
Jan 30 11:01:08  station-down           *  1c:7b:21:6c:19:b3  24:de:c6:7c:e1:10  -  -
Jan 30 11:01:08  station-up             *  1c:7b:21:6c:19:b3  24:de:c6:7c:e1:11  -  -    wpa2 psk aes
Jan 30 11:01:08  wpa2-key1             <-  1c:7b:21:6c:19:b3  24:de:c6:7c:e1:11  -  117
Jan 30 11:01:08  wpa2-key2             ->  1c:7b:21:6c:19:b3  24:de:c6:7c:e1:11  -  119
Jan 30 11:01:08  wpa2-key3             <-  1c:7b:21:6c:19:b3  24:de:c6:7c:e1:11  -  175
Jan 30 11:01:08  wpa2-key4             ->  1c:7b:21:6c:19:b3  24:de:c6:7c:e1:11  -  95
Jan 30 11:01:35  station-down           *  1c:7b:21:6c:19:b3  24:de:c6:7c:e1:11  -  -
Jan 30 11:01:35  station-up             *  1c:7b:21:6c:19:b3  24:de:c6:7c:e1:10  -  -    wpa2 psk aes
Jan 30 11:01:35  wpa2-key1             <-  1c:7b:21:6c:19:b3  24:de:c6:7c:e1:10  -  117
Jan 30 11:01:35  wpa2-key2             ->  1c:7b:21:6c:19:b3  24:de:c6:7c:e1:10  -  119
Jan 30 11:01:35  wpa2-key3             <-  1c:7b:21:6c:19:b3  24:de:c6:7c:e1:10  -  175
Jan 30 11:01:35  wpa2-key4             ->  1c:7b:21:6c:19:b3  24:de:c6:7c:e1:10  -  95
Jan 30 11:02:03  station-down           *  1c:7b:21:6c:19:b3  24:de:c6:7c:e1:10  -  -

 

Frequent Contributor I
Posts: 64
Registered: ‎01-27-2014

Re: client disassociates after connection

Hello. Below is the output.

 

Jan 30 10:43:38  station-up             *  1c:7b:21:6c:19:b3  24:de:c6:7c:e1:10  -  -    wpa2 psk aes
Jan 30 10:43:38  wpa2-key1             <-  1c:7b:21:6c:19:b3  24:de:c6:7c:e1:10  -  117
Jan 30 10:43:38  wpa2-key2             ->  1c:7b:21:6c:19:b3  24:de:c6:7c:e1:10  -  119
Jan 30 10:43:38  wpa2-key3             <-  1c:7b:21:6c:19:b3  24:de:c6:7c:e1:10  -  175
Jan 30 10:43:38  wpa2-key4             ->  1c:7b:21:6c:19:b3  24:de:c6:7c:e1:10  -  95
Jan 30 10:47:54  station-down           *  1c:7b:21:6c:19:b3  24:de:c6:7c:e1:10  -  -
Jan 30 10:48:32  station-up             *  1c:7b:21:6c:19:b3  24:de:c6:7c:e1:11  -  -    wpa2 psk aes
Jan 30 10:48:32  wpa2-key1             <-  1c:7b:21:6c:19:b3  24:de:c6:7c:e1:11  -  117
Jan 30 10:48:32  wpa2-key2             ->  1c:7b:21:6c:19:b3  24:de:c6:7c:e1:11  -  119
Jan 30 10:48:32  wpa2-key3             <-  1c:7b:21:6c:19:b3  24:de:c6:7c:e1:11  -  175
Jan 30 10:48:32  wpa2-key4             ->  1c:7b:21:6c:19:b3  24:de:c6:7c:e1:11  -  95
Jan 30 10:54:28  station-down           *  1c:7b:21:6c:19:b3  24:de:c6:7c:e1:11  -  -
Jan 30 10:54:28  station-up             *  1c:7b:21:6c:19:b3  24:de:c6:7c:e1:10  -  -    wpa2 psk aes
Jan 30 10:54:28  wpa2-key1             <-  1c:7b:21:6c:19:b3  24:de:c6:7c:e1:10  -  117
Jan 30 10:54:28  wpa2-key2             ->  1c:7b:21:6c:19:b3  24:de:c6:7c:e1:10  -  119
Jan 30 10:54:28  wpa2-key3             <-  1c:7b:21:6c:19:b3  24:de:c6:7c:e1:10  -  175
Jan 30 10:54:28  wpa2-key4             ->  1c:7b:21:6c:19:b3  24:de:c6:7c:e1:10  -  95
Jan 30 10:59:10  station-up             *  1c:7b:21:6c:19:b3  24:de:c6:7c:e1:10  -  -    wpa2 psk aes
Jan 30 10:59:10  wpa2-key1             <-  1c:7b:21:6c:19:b3  24:de:c6:7c:e1:10  -  117
Jan 30 10:59:11  station-down           *  1c:7b:21:6c:19:b3  24:de:c6:7c:e1:10  -  -
Jan 30 10:59:12  station-up             *  1c:7b:21:6c:19:b3  24:de:c6:7c:e1:10  -  -    wpa2 psk aes
Jan 30 10:59:12  wpa2-key1             <-  1c:7b:21:6c:19:b3  24:de:c6:7c:e1:10  -  117
Jan 30 10:59:12  wpa2-key2             ->  1c:7b:21:6c:19:b3  24:de:c6:7c:e1:10  -  119
Jan 30 10:59:12  wpa2-key3             <-  1c:7b:21:6c:19:b3  24:de:c6:7c:e1:10  -  175
Jan 30 10:59:12  wpa2-key4             ->  1c:7b:21:6c:19:b3  24:de:c6:7c:e1:10  -  95
Jan 30 11:01:07  station-up             *  1c:7b:21:6c:19:b3  24:de:c6:7c:e1:10  -  -    wpa2 psk aes
Jan 30 11:01:07  wpa2-key1             <-  1c:7b:21:6c:19:b3  24:de:c6:7c:e1:10  -  117
Jan 30 11:01:07  wpa2-key2             ->  1c:7b:21:6c:19:b3  24:de:c6:7c:e1:10  -  119
Jan 30 11:01:07  wpa2-key3             <-  1c:7b:21:6c:19:b3  24:de:c6:7c:e1:10  -  175
Jan 30 11:01:07  wpa2-key4             ->  1c:7b:21:6c:19:b3  24:de:c6:7c:e1:10  -  95
Jan 30 11:01:08  station-down           *  1c:7b:21:6c:19:b3  24:de:c6:7c:e1:10  -  -
Jan 30 11:01:08  station-up             *  1c:7b:21:6c:19:b3  24:de:c6:7c:e1:11  -  -    wpa2 psk aes
Jan 30 11:01:08  wpa2-key1             <-  1c:7b:21:6c:19:b3  24:de:c6:7c:e1:11  -  117
Jan 30 11:01:08  wpa2-key2             ->  1c:7b:21:6c:19:b3  24:de:c6:7c:e1:11  -  119
Jan 30 11:01:08  wpa2-key3             <-  1c:7b:21:6c:19:b3  24:de:c6:7c:e1:11  -  175
Jan 30 11:01:08  wpa2-key4             ->  1c:7b:21:6c:19:b3  24:de:c6:7c:e1:11  -  95
Jan 30 11:01:35  station-down           *  1c:7b:21:6c:19:b3  24:de:c6:7c:e1:11  -  -
Jan 30 11:01:35  station-up             *  1c:7b:21:6c:19:b3  24:de:c6:7c:e1:10  -  -    wpa2 psk aes
Jan 30 11:01:35  wpa2-key1             <-  1c:7b:21:6c:19:b3  24:de:c6:7c:e1:10  -  117
Jan 30 11:01:35  wpa2-key2             ->  1c:7b:21:6c:19:b3  24:de:c6:7c:e1:10  -  119
Jan 30 11:01:35  wpa2-key3             <-  1c:7b:21:6c:19:b3  24:de:c6:7c:e1:10  -  175
Jan 30 11:01:35  wpa2-key4             ->  1c:7b:21:6c:19:b3  24:de:c6:7c:e1:10  -  95
Jan 30 11:02:03  station-down           *  1c:7b:21:6c:19:b3  24:de:c6:7c:e1:10  -  -

 

Frequent Contributor I
Posts: 64
Registered: ‎01-27-2014

Re: client disassociates after connection

Hello.

Below is the output.

 

Jan 30 10:43:38  station-up             *  1c:7b:21:6c:19:b3  24:de:c6:7c:e1:10  -  -    wpa2 psk aes
Jan 30 10:43:38  wpa2-key1             <-  1c:7b:21:6c:19:b3  24:de:c6:7c:e1:10  -  117
Jan 30 10:43:38  wpa2-key2             ->  1c:7b:21:6c:19:b3  24:de:c6:7c:e1:10  -  119
Jan 30 10:43:38  wpa2-key3             <-  1c:7b:21:6c:19:b3  24:de:c6:7c:e1:10  -  175
Jan 30 10:43:38  wpa2-key4             ->  1c:7b:21:6c:19:b3  24:de:c6:7c:e1:10  -  95
Jan 30 10:47:54  station-down           *  1c:7b:21:6c:19:b3  24:de:c6:7c:e1:10  -  -
Jan 30 10:48:32  station-up             *  1c:7b:21:6c:19:b3  24:de:c6:7c:e1:11  -  -    wpa2 psk aes
Jan 30 10:48:32  wpa2-key1             <-  1c:7b:21:6c:19:b3  24:de:c6:7c:e1:11  -  117
Jan 30 10:48:32  wpa2-key2             ->  1c:7b:21:6c:19:b3  24:de:c6:7c:e1:11  -  119
Jan 30 10:48:32  wpa2-key3             <-  1c:7b:21:6c:19:b3  24:de:c6:7c:e1:11  -  175
Jan 30 10:48:32  wpa2-key4             ->  1c:7b:21:6c:19:b3  24:de:c6:7c:e1:11  -  95
Jan 30 10:54:28  station-down           *  1c:7b:21:6c:19:b3  24:de:c6:7c:e1:11  -  -
Jan 30 10:54:28  station-up             *  1c:7b:21:6c:19:b3  24:de:c6:7c:e1:10  -  -    wpa2 psk aes
Jan 30 10:54:28  wpa2-key1             <-  1c:7b:21:6c:19:b3  24:de:c6:7c:e1:10  -  117
Jan 30 10:54:28  wpa2-key2             ->  1c:7b:21:6c:19:b3  24:de:c6:7c:e1:10  -  119
Jan 30 10:54:28  wpa2-key3             <-  1c:7b:21:6c:19:b3  24:de:c6:7c:e1:10  -  175
Jan 30 10:54:28  wpa2-key4             ->  1c:7b:21:6c:19:b3  24:de:c6:7c:e1:10  -  95
Jan 30 10:59:10  station-up             *  1c:7b:21:6c:19:b3  24:de:c6:7c:e1:10  -  -    wpa2 psk aes
Jan 30 10:59:10  wpa2-key1             <-  1c:7b:21:6c:19:b3  24:de:c6:7c:e1:10  -  117
Jan 30 10:59:11  station-down           *  1c:7b:21:6c:19:b3  24:de:c6:7c:e1:10  -  -
Jan 30 10:59:12  station-up             *  1c:7b:21:6c:19:b3  24:de:c6:7c:e1:10  -  -    wpa2 psk aes
Jan 30 10:59:12  wpa2-key1             <-  1c:7b:21:6c:19:b3  24:de:c6:7c:e1:10  -  117
Jan 30 10:59:12  wpa2-key2             ->  1c:7b:21:6c:19:b3  24:de:c6:7c:e1:10  -  119
Jan 30 10:59:12  wpa2-key3             <-  1c:7b:21:6c:19:b3  24:de:c6:7c:e1:10  -  175
Jan 30 10:59:12  wpa2-key4             ->  1c:7b:21:6c:19:b3  24:de:c6:7c:e1:10  -  95
Jan 30 11:01:07  station-up             *  1c:7b:21:6c:19:b3  24:de:c6:7c:e1:10  -  -    wpa2 psk aes
Jan 30 11:01:07  wpa2-key1             <-  1c:7b:21:6c:19:b3  24:de:c6:7c:e1:10  -  117
Jan 30 11:01:07  wpa2-key2             ->  1c:7b:21:6c:19:b3  24:de:c6:7c:e1:10  -  119
Jan 30 11:01:07  wpa2-key3             <-  1c:7b:21:6c:19:b3  24:de:c6:7c:e1:10  -  175
Jan 30 11:01:07  wpa2-key4             ->  1c:7b:21:6c:19:b3  24:de:c6:7c:e1:10  -  95
Jan 30 11:01:08  station-down           *  1c:7b:21:6c:19:b3  24:de:c6:7c:e1:10  -  -
Jan 30 11:01:08  station-up             *  1c:7b:21:6c:19:b3  24:de:c6:7c:e1:11  -  -    wpa2 psk aes
Jan 30 11:01:08  wpa2-key1             <-  1c:7b:21:6c:19:b3  24:de:c6:7c:e1:11  -  117
Jan 30 11:01:08  wpa2-key2             ->  1c:7b:21:6c:19:b3  24:de:c6:7c:e1:11  -  119
Jan 30 11:01:08  wpa2-key3             <-  1c:7b:21:6c:19:b3  24:de:c6:7c:e1:11  -  175
Jan 30 11:01:08  wpa2-key4             ->  1c:7b:21:6c:19:b3  24:de:c6:7c:e1:11  -  95
Jan 30 11:01:35  station-down           *  1c:7b:21:6c:19:b3  24:de:c6:7c:e1:11  -  -
Jan 30 11:01:35  station-up             *  1c:7b:21:6c:19:b3  24:de:c6:7c:e1:10  -  -    wpa2 psk aes
Jan 30 11:01:35  wpa2-key1             <-  1c:7b:21:6c:19:b3  24:de:c6:7c:e1:10  -  117
Jan 30 11:01:35  wpa2-key2             ->  1c:7b:21:6c:19:b3  24:de:c6:7c:e1:10  -  119
Jan 30 11:01:35  wpa2-key3             <-  1c:7b:21:6c:19:b3  24:de:c6:7c:e1:10  -  175
Jan 30 11:01:35  wpa2-key4             ->  1c:7b:21:6c:19:b3  24:de:c6:7c:e1:10  -  95
Jan 30 11:02:03  station-down           *  1c:7b:21:6c:19:b3  24:de:c6:7c:e1:10  -  -

 

Guru Elite
Posts: 21,037
Registered: ‎03-29-2007

Re: client disassociates after connection

It is best that you open a case.  Without the logs.tar, version of android we only have a single side of the issue, and that does not say much.  The auth-tracebuf is only a single part of the puzzle.



Colin Joseph
Aruba Customer Engineering

Looking for an Answer? Search the Community Knowledge Base Here: Community Knowledge Base

Search Airheads
Showing results for 
Search instead for 
Did you mean: