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

auth trace buffer showing eap-id-mismatch

This thread has been viewed 2 times

  • 1.  auth trace buffer showing eap-id-mismatch

    Posted Nov 06, 2012 09:14 AM

    anyone encountered this message in the auth trace buffer: eap-id-mismatch, what would it point to?

     

    this is the full trace buffer surrounding it:

     

    Nov 6 14:59:42 station-up * 00:56:6a:2d:5c:70 6c:f3:dd:db:0e:71 - - wpa2 aes

    Nov 6 14:59:42 eap-id-req <- 00:56:6a:2d:5c:70 6c:f3:dd:db:0e:71 1 5

    Nov 6 14:59:42 eap-start -> 00:56:6a:2d:5c:70 6c:f3:dd:db:0e:71 - -

    Nov 6 14:59:42 eap-id-req <- 00:56:6a:2d:5c:70 6c:f3:dd:db:0e:71 1 5

    Nov 6 14:59:42 eap-id-resp -> 00:56:6a:2d:5c:70 6c:f3:dd:db:0e:71 1 27 AD
    ame

    Nov 6 14:59:42 rad-req -> 00:56:6a:2d:5c:70 6c:f3:dd:db:0e:71 9 209

    Nov 6 14:59:42 rad-resp <- 00:56:6a:2d:5c:70 6c:f3:dd:db:0e:71/radius2 9 122

    Nov 6 14:59:42 eap-req <- 00:56:6a:2d:5c:70 6c:f3:dd:db:0e:71 2 38

    Nov 6 14:59:42 eap-id-mismatch * 00:56:6a:2d:5c:70 6c:f3:dd:db:0e:71 - -

    Nov 6 14:59:42 eap-nak -> 00:56:6a:2d:5c:70 6c:f3:dd:db:0e:71 2 6

    Nov 6 14:59:42 rad-req -> 00:56:6a:2d:5c:70 6c:f3:dd:db:0e:71/radius2 10 226

    Nov 6 14:59:42 rad-reject <- 00:56:6a:2d:5c:70 6c:f3:dd:db:0e:71/radius2 10 56

    Nov 6 14:59:42 eap-failure <- 00:56:6a:2d:5c:70 6c:f3:dd:db:0e:71 2 4 server rejected

    Nov 6 14:59:42 station-down * 00:56:6a:2d:5c:70 6c:f3:dd:db:0e:71 - -



  • 2.  RE: auth trace buffer showing eap-id-mismatch

    Posted Nov 07, 2012 04:02 PM

    it might be the type of EAP used e.g. CHAP, TLS, MSCHAPv2, etc

     

    check that both of them are of the same type.