Hi, everyone.
After seeing this
Why are EAP messages such as request identity, etc encapsulated in an EAPOL header? Which is basically the part where it says 802.1X Authentication.
Wouldn’t it make more sense to just grab those fields in EAP and include them in EAPOL altogether?
Rene said that EAP messages are always carried by another protocol which is EAPOL in this case.. Are there any other protocols that can also carry EAP messages? What if EAPOL just wasn’t there? If we removed the EAPOL header, couldn’t the EAP message still be read? Why do EAP messages need to be transported via another protocol?
David