Wireless Access

last person joined: yesterday 

Access network design for branch, remote, outdoor, and campus locations with HPE Aruba Networking access points and mobility controllers.
Expand all | Collapse all

PSK user immediately disconnects

This thread has been viewed 2 times
  • 1.  PSK user immediately disconnects

    Posted Jan 26, 2015 08:59 AM

    I have a customer having discconect issues as soon as they try to connect the client. Signal will show on the client for approx. 5 seconds and disconnect.

     

    The key is correct and I'm getting a PTK challenage failed at the end of the session. Any hints?

     

     

     

    Jan 26 05:44:37 :501109:  <NOTI> |AP _AP10@172.30.60.126 stm|  Auth request: 40:83:de:31:91:ae: AP 172.30.60.126-24:de:c6:4c:9c:b0-_AP10 auth_alg 0

    Jan 26 05:44:37 :501065:  <DBUG> |AP _AP10@172.30.60.126 stm|  remove_stale_sta 2738: client 40:83:de:31:91:ae not in stale hash table

    Jan 26 05:44:37 :501093:  <NOTI> |AP _AP10@172.30.60.126 stm|  Auth success: 40:83:de:31:91:ae: AP 172.30.60.126-24:de:c6:4c:9c:b0-_AP10

    Jan 26 05:44:37 :501095:  <NOTI> |AP _AP10@172.30.60.126 stm|  Assoc request @ 05:44:28.547231: 40:83:de:31:91:ae (SN 1906): AP 172.30.60.126-24:de:c6:4c:9c:b0-_AP10

    Jan 26 05:44:37 :501100:  <NOTI> |AP _AP10@172.30.60.126 stm|  Assoc success @ 05:44:28.548484: 40:83:de:31:91:ae: AP 172.30.60.126-24:de:c6:4c:9c:b0-_AP10

    Jan 26 05:44:37 :501100:  <NOTI> |stm|  Assoc success @ 05:44:37.827913: 40:83:de:31:91:ae: AP 172.30.60.126-24:de:c6:4c:9c:b0-_AP10

    Jan 26 05:44:37 :522295:  <DBUG> |authmgr|  Auth GSM : USER_STA event 0 for user 40:83:de:31:91:ae

    Jan 26 05:44:37 :522035:  <INFO> |authmgr|  MAC=40:83:de:31:91:ae Station UP: BSSID=24:de:c6:4c:9c:b0 ESSID=Warehouse VLAN=151 AP-name=_AP10

    Jan 26 05:44:37 :522077:  <DBUG> |authmgr|  MAC=40:83:de:31:91:ae ingress 0x0x1001d (tunnel 29), u_encr 8, m_encr 2056, slotport 0x0x2100 , type: local, FW mode: 0, AP IP: 0.0.0.0 mdie 0 ft_complete 0

    Jan 26 05:44:37 :522264:  <DBUG> |authmgr|  "MAC:40:83:de:31:91:ae: Allocating UUID: 2.

    Jan 26 05:44:37 :522258:  <DBUG> |authmgr|  "VDR - Add to history of user user 40:83:de:31:91:ae vlan 0 derivation_type Reset VLANs for Station up index 0.

    Jan 26 05:44:37 :522255:  <DBUG> |authmgr|  "VDR - set vlan in user for 40:83:de:31:91:ae vlan 151 fwdmode 0 derivation_type Default VLAN.

    Jan 26 05:44:37 :522258:  <DBUG> |authmgr|  "VDR - Add to history of user user 40:83:de:31:91:ae vlan 151 derivation_type Default VLAN index 1.

    Jan 26 05:44:37 :522255:  <DBUG> |authmgr|  "VDR - set vlan in user for 40:83:de:31:91:ae vlan 151 fwdmode 0 derivation_type Current VLAN updated.

    Jan 26 05:44:37 :522258:  <DBUG> |authmgr|  "VDR - Add to history of user user 40:83:de:31:91:ae vlan 151 derivation_type Current VLAN updated index 2.

    Jan 26 05:44:37 :522246:  <DBUG> |authmgr|  Idle timeout should be driven by STM for MAC 40:83:de:31:91:ae.

    Jan 26 05:44:37 :524141:  <DBUG> |authmgr|  clr_pmkcache_ft():988: MAC:40:83:de:31:91:ae BSS:24:de:c6:4c:9c:b0

    Jan 26 05:44:37 :522287:  <DBUG> |authmgr|  Auth GSM : MAC_USER publish for mac 40:83:de:31:91:ae bssid 24:de:c6:4c:9c:b0 vlan 151 type 1 data-ready 0

    Jan 26 05:44:37 :522254:  <DBUG> |authmgr|  VDR - mac 40:83:de:31:91:ae rolename logon fwdmode 0 derivation_type Initial Role Contained vp not present.

    Jan 26 05:44:37 :522258:  <DBUG> |authmgr|  "VDR - Add to history of user user 40:83:de:31:91:ae vlan 0 derivation_type Reset Role Based VLANs index 3.

    Jan 26 05:44:37 :524124:  <DBUG> |authmgr|  dot1x_supplicant_up(): MAC:40:83:de:31:91:ae, pmkid_present:False, pmkid:N/A

    Jan 26 05:44:37 :522255:  <DBUG> |authmgr|  "VDR - set vlan in user for 40:83:de:31:91:ae vlan 151 fwdmode 0 derivation_type Current VLAN updated.

    Jan 26 05:44:37 :522258:  <DBUG> |authmgr|  "VDR - Add to history of user user 40:83:de:31:91:ae vlan 151 derivation_type Current VLAN updated index 4.

    Jan 26 05:44:37 :522260:  <DBUG> |authmgr|  "VDR - Cur VLAN updated 40:83:de:31:91:ae mob 0 inform 1 remote 0 wired 0 defvlan 151 exportedvlan 0 curvlan 151.

    Jan 26 05:44:37 :522050:  <INFO> |authmgr|  MAC=40:83:de:31:91:ae,IP=N/A User data downloaded to datapath, new Role=logon/2, bw Contract=0/0, reason=layer 2 event driven download, idle-timeout=300

    Jan 26 05:44:37 :522242:  <DBUG> |authmgr|  MAC=40:83:de:31:91:ae Station Created Update MMS: BSSID=24:de:c6:4c:9c:b0 ESSID=Warehouse VLAN=151 AP-name=_AP10

    Jan 26 05:44:37 :522301:  <DBUG> |authmgr|  Auth GSM : USER publish for uuid 2 mac 40:83:de:31:91:ae name  role logon devtype  wired 0 authtype 0 subtype 0  encrypt-type 3 conn-port 8448 fwd-mode 0

    Jan 26 05:44:40 :522289:  <DBUG> |authmgr|  Auth GSM : MAC_USER mu_delete publish for mac 40:83:de:31:91:ae bssid 24:de:c6:4c:9c:b0 vlan 151 type 1 data-ready 0 deauth-reason 49

    Jan 26 05:44:40 :501106:  <NOTI> |stm|  Deauth to sta: 40:83:de:31:91:ae: Ageout AP 172.30.60.126-24:de:c6:4c:9c:b0-_AP10 wifi_deauth_sta

    Jan 26 05:44:40 :522296:  <DBUG> |authmgr|  Auth GSM : USER_STA delete event for user 40:83:de:31:91:ae age 0 deauth_reason 49

    Jan 26 05:44:40 :522036:  <INFO> |authmgr|  MAC=40:83:de:31:91:ae Station DN: BSSID=24:de:c6:4c:9c:b0 ESSID=Warehouse VLAN=151 AP-name=_AP10

    Jan 26 05:44:40 :522234:  <DBUG> |authmgr|  Setting idle timer for user 40:83:de:31:91:ae to 300 seconds (idle timeout: 300 ageout: 0).

    Jan 26 05:44:40 :522244:  <DBUG> |authmgr|  MAC=40:83:de:31:91:ae Station Deleted Update MMS

    Jan 26 05:44:40 :522301:  <DBUG> |authmgr|  Auth GSM : USER publish for uuid 2 mac 40:83:de:31:91:ae name  role logon devtype  wired 0 authtype 0 subtype 0  encrypt-type 3 conn-port 8448 fwd-mode 0

    Jan 26 05:44:40 :522004:  <DBUG> |authmgr|  40:83:de:31:91:ae: station datapath entry deleted

    Jan 26 05:44:40 :522290:  <DBUG> |authmgr|  Auth GSM : MAC_USER delete for mac 40:83:de:31:91:ae

    Jan 26 05:44:40 :522303:  <DBUG> |authmgr|  Auth GSM : USER delete for mac 40:83:de:31:91:ae uuid 2 

    Jan 26 05:44:40 :522265:  <DBUG> |authmgr|  "MAC:40:83:de:31:91:ae: Deallocating UUID: 2.

    Jan 26 05:44:40 :501080:  <NOTI> |stm|  Deauth to sta: 40:83:de:31:91:ae: Ageout AP 172.30.60.126-24:de:c6:4c:9c:b0-_AP10 Ptk Challenge Failed

    Jan 26 05:44:40 :501000:  <DBUG> |stm|  Station 40:83:de:31:91:ae: Clearing state



  • 2.  RE: PSK user immediately disconnects

    EMPLOYEE
    Posted Jan 26, 2015 09:17 AM
    upgrade client driver

    Or wrong preshared key.


  • 3.  RE: PSK user immediately disconnects

    Posted Jan 26, 2015 10:50 AM

    have you configured WIP.

    is the problem with all your device or only with one.



  • 4.  RE: PSK user immediately disconnects

    Posted Jan 26, 2015 11:54 AM

    Question

    Those this happens to ALL the clients which are different devices? or it just happen with one device or a particular model of laptop?

     

    If its just a model, or just one laptop  it could be what Collin says

    If it happens to ALL the devices it could be what rchahboune says

     

    Cheers

    Carlos



  • 5.  RE: PSK user immediately disconnects
    Best Answer

    Posted Jan 26, 2015 11:59 AM
    After viewing more of the logs I noticed clients getting rejected for an incorrect PSK. Come to find out the original key was in use because the config wasn't saved after it changed.
    Layer 3 Communications is growing and needs more room!
    Effective January 12th, 2015 our new Headquarters address will be 1450 Oakbrook Dr., Suite 900, Norcross, GA 30093-6239.
    Rest assured we will maintain our support and managed services throughout the move.
    If you have any concerns or questions please don’t hesitate to contact your Layer 3 representative or our corporate office at (770) 225-5300 or move@layer3com.com.


  • 6.  RE: PSK user immediately disconnects

    Posted Jul 01, 2015 03:55 AM

    Hi,

     

    What does age 0 deauth_reason 49 mean? ____

    What does 49 mean? ____



  • 7.  RE: PSK user immediately disconnects

    Posted Jul 01, 2015 04:43 AM
    As per IEEE 802.11-2012 standard: deauth_reason 49 mean - invalid pairwise master key identifier (PMKI)