If you have 2 Xsupplicant clients (or an XSupplicant client and any other client) that connect on the same switch port the XSupplicant gets booted off when the other supplicant logs on.
I initially thought that it was because the XSupplicant was sending an EAPOL logoff message before sending the START message, and that was causing the other client to disconnect. However, I see that if I use Xsupplicant on one client, and the XP supplicant on the other client, the Xsupplicant still logs off when the XP client logs on, but the XP supplicant does not send the LOGOFF message when starting EAPOL.
After the XP client has logged on, the Xsupplicant client can attempt to log on again, and will be successful. However, if 2 Xsupplicant clients are trying to log onto the same physical port, they will always knock each other off when they start the EAPOL process.
I am using Parallels with 2 virtual machines connected on the same interface.
I'm not an 802.1x expert, but is it supposed to send the LOGOFF message prior to sending the START message?
The attachment is a capture of one client (mac 18:83) successfully logging in. Then the second client (mac f5:bf) logs on, and the first client is kicked off, and eventually times out.