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.
Back to discussions
Expand all | Collapse all

legasy device not able to connect WPA2-AES

This thread has been viewed 0 times

  • 1.  legasy device not able to connect WPA2-AES

    Posted Feb 18, 2015 11:24 AM

    hi all,

    One more question.

    I have one SSID with WPA2auth and AES encryption enabledand auth server as AD [dont have CPPM].

    Today i was trying to authenticate one legasy device [nokia 5800] with that SSID, but its saying EAP-peap authentication failed.

    Is there anything to support legasy device with wpa2 -aes And also how can i troubleshoot why the client showing EAP-PEAP auth failed..

     



  • 2.  RE: legasy device not able to connect WPA2-AES

    EMPLOYEE
    Posted Feb 18, 2015 11:26 AM
    Turn on user-debugging for the client and then run "show auth-tracebuf mac
    <CLIENT-MAC>"</CLIENT-MAC>


  • 3.  RE: legasy device not able to connect WPA2-AES

    Posted Feb 18, 2015 11:52 AM

    Since this device only supports b/g try the following:

    - Make sure that all your lower basic rates are enabled

    - Create a test SSID with the same aaa profile and disable "band steering" on the VAP 



  • 4.  RE: legasy device not able to connect WPA2-AES

    Posted Feb 18, 2015 12:00 PM

    Band steering is disabled, and all the lower rates is also enabled

     

    [Edit]  here is the O/P

    Feb 18 06:07:21  station-up             *  00:25:48:c0:1f:89  00:24:6c:b2:2d:c0  -  -  wpa2 aes
    Feb 18 06:07:21  eap-id-req            <-  00:25:48:c0:1f:89  00:24:6c:b2:2d:c0  1  5
    Feb 18 06:07:21  eap-start             ->  00:25:48:c0:1f:89  00:24:6c:b2:2d:c0  -  -
    Feb 18 06:07:21  eap-id-req            <-  00:25:48:c0:1f:89  00:24:6c:b2:2d:c0  1  5
    Feb 18 06:07:21  station-down           *  00:25:48:c0:1f:89  00:24:6c:b2:2d:c0  -  -
    Feb 18 06:07:32  station-up             *  00:25:48:c0:1f:89  00:24:6c:b2:2d:c0  -  -  wpa2 aes
    Feb 18 06:07:32  eap-id-req            <-  00:25:48:c0:1f:89  00:24:6c:b2:2d:c0  1  5
    Feb 18 06:07:32  eap-start             ->  00:25:48:c0:1f:89  00:24:6c:b2:2d:c0  -  -
    Feb 18 06:07:32  eap-id-req            <-  00:25:48:c0:1f:89  00:24:6c:b2:2d:c0  1  5
    Feb 18 06:07:32  station-down           *  00:25:48:c0:1f:89  00:24:6c:b2:2d:c0  -  -
    Feb 18 06:08:01  station-up             *  00:25:48:c0:1f:89  00:24:6c:b2:2d:c0  -  -  wpa2 aes
    Feb 18 06:08:01  eap-id-req            <-  00:25:48:c0:1f:89  00:24:6c:b2:2d:c0  1  5
    Feb 18 06:08:01  eap-start             ->  00:25:48:c0:1f:89  00:24:6c:b2:2d:c0  -  -
    Feb 18 06:08:01  eap-id-req            <-  00:25:48:c0:1f:89  00:24:6c:b2:2d:c0  1  5
    Feb 18 06:08:01  station-down           *  00:25:48:c0:1f:89  00:24:6c:b2:2d:c0  -  -



  • 5.  RE: legasy device not able to connect WPA2-AES

    Posted Feb 18, 2015 11:57 AM
    how to turn on user debug....
    plz tell me


  • 6.  RE: legasy device not able to connect WPA2-AES

    EMPLOYEE
    Posted Feb 18, 2015 11:59 AM

    Logging level debugging user-debug <client-mac>



  • 7.  RE: legasy device not able to connect WPA2-AES

    Posted Feb 18, 2015 12:05 PM
    thanks Tim,

    here is the O/P

    Feb 18 06:07:21 station-up * 00:25:48:c0:1f:89
    00:24:6c:b2:2d:c0 - - wpa2 aes
    Feb 18 06:07:21 eap-id-req <- 00:25:48:c0:1f:89
    00:24:6c:b2:2d:c0 1 5
    Feb 18 06:07:21 eap-start -> 00:25:48:c0:1f:89
    00:24:6c:b2:2d:c0 - -
    Feb 18 06:07:21 eap-id-req <- 00:25:48:c0:1f:89
    00:24:6c:b2:2d:c0 1 5
    Feb 18 06:07:21 station-down * 00:25:48:c0:1f:89
    00:24:6c:b2:2d:c0 - -
    Feb 18 06:07:32 station-up * 00:25:48:c0:1f:89
    00:24:6c:b2:2d:c0 - - wpa2 aes
    Feb 18 06:07:32 eap-id-req <- 00:25:48:c0:1f:89
    00:24:6c:b2:2d:c0 1 5
    Feb 18 06:07:32 eap-start -> 00:25:48:c0:1f:89
    00:24:6c:b2:2d:c0 - -
    Feb 18 06:07:32 eap-id-req <- 00:25:48:c0:1f:89
    00:24:6c:b2:2d:c0 1 5
    Feb 18 06:07:32 station-down * 00:25:48:c0:1f:89
    00:24:6c:b2:2d:c0 - -
    Feb 18 06:08:01 station-up * 00:25:48:c0:1f:89
    00:24:6c:b2:2d:c0 - - wpa2 aes
    Feb 18 06:08:01 eap-id-req <- 00:25:48:c0:1f:89
    00:24:6c:b2:2d:c0 1 5
    Feb 18 06:08:01 eap-start -> 00:25:48:c0:1f:89
    00:24:6c:b2:2d:c0 - -
    Feb 18 06:08:01 eap-id-req <- 00:25:48:c0:1f:89
    00:24:6c:b2:2d:c0 1 5
    Feb 18 06:08:01 station-down * 00:25:48:c0:1f:89
    00:24:6c:b2:2d:c0 - -


  • 8.  RE: legasy device not able to connect WPA2-AES

    Posted Feb 18, 2015 12:20 PM

    Can that device connect to an open SSID ?



  • 9.  RE: legasy device not able to connect WPA2-AES

    Posted Feb 18, 2015 12:22 PM

    Yeah it able to connect Open network, Captive portal, PSK.

     

    her eis the O/P of tracebuf

    Feb 18 06:07:21  station-up             *  00:25:48:c0:1f:89  00:24:6c:b2:2d:c0  -  -  wpa2 aes
    Feb 18 06:07:21  eap-id-req            <-  00:25:48:c0:1f:89  00:24:6c:b2:2d:c0  1  5
    Feb 18 06:07:21  eap-start             ->  00:25:48:c0:1f:89  00:24:6c:b2:2d:c0  -  -
    Feb 18 06:07:21  eap-id-req            <-  00:25:48:c0:1f:89  00:24:6c:b2:2d:c0  1  5
    Feb 18 06:07:21  station-down           *  00:25:48:c0:1f:89  00:24:6c:b2:2d:c0  -  -
    Feb 18 06:07:32  station-up             *  00:25:48:c0:1f:89  00:24:6c:b2:2d:c0  -  -  wpa2 aes
    Feb 18 06:07:32  eap-id-req            <-  00:25:48:c0:1f:89  00:24:6c:b2:2d:c0  1  5
    Feb 18 06:07:32  eap-start             ->  00:25:48:c0:1f:89  00:24:6c:b2:2d:c0  -  -
    Feb 18 06:07:32  eap-id-req            <-  00:25:48:c0:1f:89  00:24:6c:b2:2d:c0  1  5
    Feb 18 06:07:32  station-down           *  00:25:48:c0:1f:89  00:24:6c:b2:2d:c0  -  -
    Feb 18 06:08:01  station-up             *  00:25:48:c0:1f:89  00:24:6c:b2:2d:c0  -  -  wpa2 aes
    Feb 18 06:08:01  eap-id-req            <-  00:25:48:c0:1f:89  00:24:6c:b2:2d:c0  1  5
    Feb 18 06:08:01  eap-start             ->  00:25:48:c0:1f:89  00:24:6c:b2:2d:c0  -  -
    Feb 18 06:08:01  eap-id-req            <-  00:25:48:c0:1f:89  00:24:6c:b2:2d:c0  1  5
    Feb 18 06:08:01  station-down           *  00:25:48:c0:1f:89  00:24:6c:b2:2d:c0  -  -



  • 10.  RE: legasy device not able to connect WPA2-AES

    EMPLOYEE
    Posted Feb 18, 2015 06:35 PM
    It looks like the client is not responding with its identity. Can you
    confirm that this device supports WPA2-Enterprise?


  • 11.  RE: legasy device not able to connect WPA2-AES

    Posted Feb 18, 2015 09:07 PM

    Yes, its supports WPA2, It has the option to select WPA2-AES [MSCHAPv2]



  • 12.  RE: legasy device not able to connect WPA2-AES

    EMPLOYEE
    Posted Feb 18, 2015 09:21 PM

    Did you load the Radius Server's Server Certificate on the device?  https://www.lrz.de/services/netz/mobil/802_1x/eduroam_S60v5_en/



  • 13.  RE: legasy device not able to connect WPA2-AES

    Posted Feb 18, 2015 12:26 PM

    Yes its able to connect open n/w , captive portal, psk,

     

    Here is the output of tracebuf

     

    Feb 18 06:07:21  station-up             *  00:25:48:c0:1f:89  00:24:6c:b2:2d:c0  -  -  wpa2 aes
    Feb 18 06:07:21  eap-id-req            <-  00:25:48:c0:1f:89  00:24:6c:b2:2d:c0  1  5
    Feb 18 06:07:21  eap-start             ->  00:25:48:c0:1f:89  00:24:6c:b2:2d:c0  -  -
    Feb 18 06:07:21  eap-id-req            <-  00:25:48:c0:1f:89  00:24:6c:b2:2d:c0  1  5
    Feb 18 06:07:21  station-down           *  00:25:48:c0:1f:89  00:24:6c:b2:2d:c0  -  -
    Feb 18 06:07:32  station-up             *  00:25:48:c0:1f:89  00:24:6c:b2:2d:c0  -  -  wpa2 aes
    Feb 18 06:07:32  eap-id-req            <-  00:25:48:c0:1f:89  00:24:6c:b2:2d:c0  1  5
    Feb 18 06:07:32  eap-start             ->  00:25:48:c0:1f:89  00:24:6c:b2:2d:c0  -  -
    Feb 18 06:07:32  eap-id-req            <-  00:25:48:c0:1f:89  00:24:6c:b2:2d:c0  1  5
    Feb 18 06:07:32  station-down           *  00:25:48:c0:1f:89  00:24:6c:b2:2d:c0  -  -
    Feb 18 06:08:01  station-up             *  00:25:48:c0:1f:89  00:24:6c:b2:2d:c0  -  -  wpa2 aes
    Feb 18 06:08:01  eap-id-req            <-  00:25:48:c0:1f:89  00:24:6c:b2:2d:c0  1  5
    Feb 18 06:08:01  eap-start             ->  00:25:48:c0:1f:89  00:24:6c:b2:2d:c0  -  -
    Feb 18 06:08:01  eap-id-req            <-  00:25:48:c0:1f:89  00:24:6c:b2:2d:c0  1  5
    Feb 18 06:08:01  station-down           *  00:25:48:c0:1f:89  00:24:6c:b2:2d:c0  -  -



  • 14.  RE: legasy device not able to connect WPA2-AES

    Posted Feb 18, 2015 12:33 PM

    yes its able to connect with open, captive portal, psk.

     

    here is the o/p of tracebuf

     

     

    Auth Trace Buffer
    -----------------


    Feb 18 06:07:21 station-up * 00:25:48:c0:1f:89 00:24:6c:b2:2d:c0 - - wpa2 aes
    Feb 18 06:07:21 eap-id-req <- 00:25:48:c0:1f:89 00:24:6c:b2:2d:c0 1 5
    Feb 18 06:07:21 eap-start -> 00:25:48:c0:1f:89 00:24:6c:b2:2d:c0 - -
    Feb 18 06:07:21 eap-id-req <- 00:25:48:c0:1f:89 00:24:6c:b2:2d:c0 1 5
    Feb 18 06:07:21 station-down * 00:25:48:c0:1f:89 00:24:6c:b2:2d:c0 - -
    Feb 18 06:07:32 station-up * 00:25:48:c0:1f:89 00:24:6c:b2:2d:c0 - - wpa2 aes
    Feb 18 06:07:32 eap-id-req <- 00:25:48:c0:1f:89 00:24:6c:b2:2d:c0 1 5
    Feb 18 06:07:32 eap-start -> 00:25:48:c0:1f:89 00:24:6c:b2:2d:c0 - -
    Feb 18 06:07:32 eap-id-req <- 00:25:48:c0:1f:89 00:24:6c:b2:2d:c0 1 5
    Feb 18 06:07:32 station-down * 00:25:48:c0:1f:89 00:24:6c:b2:2d:c0 - -
    Feb 18 06:08:01 station-up * 00:25:48:c0:1f:89 00:24:6c:b2:2d:c0 - - wpa2 aes
    Feb 18 06:08:01 eap-id-req <- 00:25:48:c0:1f:89 00:24:6c:b2:2d:c0 1 5
    Feb 18 06:08:01 eap-start -> 00:25:48:c0:1f:89 00:24:6c:b2:2d:c0 - -
    Feb 18 06:08:01 eap-id-req <- 00:25:48:c0:1f:89 00:24:6c:b2:2d:c0 1 5
    Feb 18 06:08:01 station-down * 00:25:48:c0:1f:89 00:24:6c:b2:2d:c0 - -

     



  • 15.  RE: legasy device not able to connect WPA2-AES

    Posted Feb 18, 2015 12:35 PM
    yeah its able to connect to open, captive portal, psk N/W without issue..


    here is the output of tracebuf.

    Auth Trace Buffer
    -----------------


    Feb 18 06:07:21 station-up * 00:25:48:c0:1f:89
    00:24:6c:b2:2d:c0 - - wpa2 aes
    Feb 18 06:07:21 eap-id-req <- 00:25:48:c0:1f:89
    00:24:6c:b2:2d:c0 1 5
    Feb 18 06:07:21 eap-start -> 00:25:48:c0:1f:89
    00:24:6c:b2:2d:c0 - -
    Feb 18 06:07:21 eap-id-req <- 00:25:48:c0:1f:89
    00:24:6c:b2:2d:c0 1 5
    Feb 18 06:07:21 station-down * 00:25:48:c0:1f:89
    00:24:6c:b2:2d:c0 - -
    Feb 18 06:07:32 station-up * 00:25:48:c0:1f:89
    00:24:6c:b2:2d:c0 - - wpa2 aes
    Feb 18 06:07:32 eap-id-req <- 00:25:48:c0:1f:89
    00:24:6c:b2:2d:c0 1 5
    Feb 18 06:07:32 eap-start -> 00:25:48:c0:1f:89
    00:24:6c:b2:2d:c0 - -
    Feb 18 06:07:32 eap-id-req <- 00:25:48:c0:1f:89
    00:24:6c:b2:2d:c0 1 5
    Feb 18 06:07:32 station-down * 00:25:48:c0:1f:89
    00:24:6c:b2:2d:c0 - -
    Feb 18 06:08:01 station-up * 00:25:48:c0:1f:89
    00:24:6c:b2:2d:c0 - - wpa2 aes
    Feb 18 06:08:01 eap-id-req <- 00:25:48:c0:1f:89
    00:24:6c:b2:2d:c0 1 5
    Feb 18 06:08:01 eap-start -> 00:25:48:c0:1f:89
    00:24:6c:b2:2d:c0 - -
    Feb 18 06:08:01 eap-id-req <- 00:25:48:c0:1f:89
    00:24:6c:b2:2d:c0 1 5
    Feb 18 06:08:01 station-down * 00:25:48:c0:1f:89
    00:24:6c:b2:2d:c0 - -



    --
    sent from my android.
    Thanks


  • 16.  RE: legasy device not able to connect WPA2-AES

    Posted Feb 18, 2015 12:50 PM

    Yeah its able to connect Open , captive portal, psk .

     

    here is the output of the tracebuf

     

    Auth Trace Buffer
    -----------------


    Feb 18 06:07:21  station-up             *  00:25:48:c0:1f:89  00:24:6c:b2:2d:c0  -  -  wpa2 aes
    Feb 18 06:07:21  eap-id-req            <-  00:25:48:c0:1f:89  00:24:6c:b2:2d:c0  1  5
    Feb 18 06:07:21  eap-start             ->  00:25:48:c0:1f:89  00:24:6c:b2:2d:c0  -  -
    Feb 18 06:07:21  eap-id-req            <-  00:25:48:c0:1f:89  00:24:6c:b2:2d:c0  1  5
    Feb 18 06:07:21  station-down           *  00:25:48:c0:1f:89  00:24:6c:b2:2d:c0  -  -
    Feb 18 06:07:32  station-up             *  00:25:48:c0:1f:89  00:24:6c:b2:2d:c0  -  -  wpa2 aes
    Feb 18 06:07:32  eap-id-req            <-  00:25:48:c0:1f:89  00:24:6c:b2:2d:c0  1  5
    Feb 18 06:07:32  eap-start             ->  00:25:48:c0:1f:89  00:24:6c:b2:2d:c0  -  -
    Feb 18 06:07:32  eap-id-req            <-  00:25:48:c0:1f:89  00:24:6c:b2:2d:c0  1  5
    Feb 18 06:07:32  station-down           *  00:25:48:c0:1f:89  00:24:6c:b2:2d:c0  -  -
    Feb 18 06:08:01  station-up             *  00:25:48:c0:1f:89  00:24:6c:b2:2d:c0  -  -  wpa2 aes
    Feb 18 06:08:01  eap-id-req            <-  00:25:48:c0:1f:89  00:24:6c:b2:2d:c0  1  5
    Feb 18 06:08:01  eap-start             ->  00:25:48:c0:1f:89  00:24:6c:b2:2d:c0  -  -
    Feb 18 06:08:01  eap-id-req            <-  00:25:48:c0:1f:89  00:24:6c:b2:2d:c0  1  5
    Feb 18 06:08:01  station-down           *  00:25:48:c0:1f:89  00:24:6c:b2:2d:c0  -  -