Wireless Access

Reply
Frequent Contributor II
Posts: 144
Registered: ‎01-21-2015

legasy device not able to connect WPA2-AES

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..

 

rana
Guru Elite
Posts: 8,632
Registered: ‎09-08-2010

Re: legasy device not able to connect WPA2-AES

Turn on user-debugging for the client and then run "show auth-tracebuf mac
"

Tim Cappalli | Aruba Security TME
@timcappalli | timcappalli.me | ACMX #367 / ACCX #480
MVP
Posts: 4,301
Registered: ‎07-20-2011

Re: legasy device not able to connect WPA2-AES

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 

Thank you

Victor Fabian
Lead Mobility Engineer @ Integration Partners
AMFX | ACMX | ACDX | ACCX | CWAP | CWDP | CWNA
Frequent Contributor II
Posts: 144
Registered: ‎01-21-2015

Re: legasy device not able to connect WPA2-AES

how to turn on user debug....
plz tell me
rana
Guru Elite
Posts: 8,632
Registered: ‎09-08-2010

Re: legasy device not able to connect WPA2-AES

[ Edited ]

Logging level debugging user-debug <client-mac>


Tim Cappalli | Aruba Security TME
@timcappalli | timcappalli.me | ACMX #367 / ACCX #480
Frequent Contributor II
Posts: 144
Registered: ‎01-21-2015

Re: legasy device not able to connect WPA2-AES

[ Edited ]

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  -  -

rana
Frequent Contributor II
Posts: 144
Registered: ‎01-21-2015

Re: legasy device not able to connect WPA2-AES

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 - -
rana
MVP
Posts: 4,301
Registered: ‎07-20-2011

Re: legasy device not able to connect WPA2-AES

Can that device connect to an open SSID ?

Thank you

Victor Fabian
Lead Mobility Engineer @ Integration Partners
AMFX | ACMX | ACDX | ACCX | CWAP | CWDP | CWNA
Frequent Contributor II
Posts: 144
Registered: ‎01-21-2015

Re: legasy device not able to connect WPA2-AES

[ Edited ]

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  -  -

rana
Frequent Contributor II
Posts: 144
Registered: ‎01-21-2015

Re: legasy device not able to connect WPA2-AES

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  -  -

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