Controllerless Networks

 View Only
last person joined: 20 hours ago 

Aruba Instant Wi-Fi: Meet the controllerless Wi-Fi solution that's easy to set-up, is loaded with security and smarts, and won't break your budget.
Expand all | Collapse all

Problem with certain clients on draco 8.9.0.3_83448

This thread has been viewed 15 times
  • 1.  Problem with certain clients on draco 8.9.0.3_83448

    Posted Sep 29, 2022 11:14 AM
    Hi,
    after updating my Aruba Instant (3 Aruba 515) to Draco 8.9.0.3_83448 certain clients (mostly window 10) can't connect to the networks.

    I'm getting mgmt-frames like this:

    Sep 29 11:40:11.622  deauth        cc:88:c7:0d:13:c1  08:ed:b9:a1:13:4d  cc:88:c7:0d:13:c1  15      Denied; Ageout (seq num 1)                                                                                                             
    Sep 29 11:40:07.430  assoc-resp    cc:88:c7:0d:13:c1  08:ed:b9:a1:13:4d  cc:88:c7:0d:13:c1  15      Success                                                                                                                                
    Sep 29 11:40:07.430  assoc-req     08:ed:b9:a1:13:4d  cc:88:c7:0d:13:c1  cc:88:c7:0d:13:c1  58      -                                                                                                                                      
    Sep 29 11:40:07.426  auth          cc:88:c7:0d:13:c1  08:ed:b9:a1:13:4d  cc:88:c7:0d:13:c1  15      Success (seq num 0)                                                                                                                    
    Sep 29 11:40:07.426  auth          08:ed:b9:a1:13:4d  cc:88:c7:0d:13:c1  cc:88:c7:0d:13:c1  0       - ​


    The authentication frames look like this:

    Sep 29 09:16:39  station-up             *  08:ed:b9:a1:13:4d  cc:88:c7:0d:13:c0  -  -    wpa2 psk aes
    Sep 29 09:16:39  wpa2-key1             <-  08:ed:b9:a1:13:4d  cc:88:c7:0d:13:c0  -  117  
    Sep 29 09:16:39  wpa2-key2             ->  08:ed:b9:a1:13:4d  cc:88:c7:0d:13:c0  -  117  
    Sep 29 09:16:39  wpa2-key3             <-  08:ed:b9:a1:13:4d  cc:88:c7:0d:13:c0  -  191  
    Sep 29 09:16:40  wpa2-key3             <-  08:ed:b9:a1:13:4d  cc:88:c7:0d:13:c0  -  191  
    Sep 29 09:16:42  wpa2-key3             <-  08:ed:b9:a1:13:4d  cc:88:c7:0d:13:c0  -  191​

    Any ideas what is going wrong here?

    Regards
    Mario Hommel



  • 2.  RE: Problem with certain clients on draco 8.9.0.3_83448

    EMPLOYEE
    Posted Sep 30, 2022 11:43 AM
    Looks like your client is not responding to Key3, for some reason.  What kind of clients are these?

    ------------------------------
    Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba Networks.

    HPE Design and Deploy Guides: https://community.arubanetworks.com/support/migrated-knowledge-base?attachments=&communitykey=dcc83c62-1a3a-4dd8-94dc-92968ea6fff1&pageindex=0&pagesize=12&search=&sort=most_recent&viewtype=card
    ------------------------------



  • 3.  RE: Problem with certain clients on draco 8.9.0.3_83448

    Posted Oct 05, 2022 07:04 AM
    The clients are Windows 10.


  • 4.  RE: Problem with certain clients on draco 8.9.0.3_83448
    Best Answer

    Posted Oct 24, 2022 04:57 AM
    Finally it seems to be a problem with certain windows hardware and drivers which do not deal correctly with WPA3. After stepping back to WPA2 authentication, all clients can connect again to the accesspoints.