EAPOL Key Message 4 of 4 twice

PelionIoT / mbed-cloud-client-example

Reference example application using Izuma Device Management Client library

https://izumanetworks.com

Apache License 2.0

30 stars 97 forks source link

Closed dannywahlquist closed 4 years ago

dannywahlquist commented 4 years ago

Any idea why my devices respond to EAPOL Key Message 1 of 4 and 3 of 4 with 4 of 4 both times?

ciarmcom commented 4 years ago

ARM Internal Ref: IOTCLT-3901

yogpan01 commented 4 years ago

Hi, Can you please elaborate your use case? What is EAPOL Key Message and what is the sequence you are expecting vs. what you are observing?

dannywahlquist commented 4 years ago

I verified that it is working correctly. The Wireshark dissector is reporting message 2 as 4 because of the way WiSUN modifies the 4-way handshake.

yogpan01 commented 4 years ago

Good to know that its working fine. Can this be considered as resolved and issue can be closed?

dannywahlquist commented 4 years ago

Yes, thanks!