On Tue, Oct 27, 2015 at 06:47:15AM +0000, Avichal Agarwal wrote: > This patch provide the exact information whether WPA/RSN EAPOL-Key message sent > successfully or failed. wpa_eapol_key_send will return >=0 on success and < 0 on failure. > After receiving 3/4 EAPOL packet , wpa_supplicant sends 4/4 EAPOL packet and shows > CTRL_EVENT_CONNECTED only after verifying that whether 4/4 packet send was success or failed. This is only checking whether the l2_packet call to send the frame succeeds. Whether the kernel driver manages to send the frame out in a way that the AP receives it is a completely different question and I'd expect it to be much more common for the frame to get lost at that point rather than when getting it delivered to local kernel with send() on the packet socket. The changes themselves look fine to add, but I would like to understand whether there is indeed a case where this shows failures in real use cases. Would you have a wpa_supplicant debug log that can show such a case and if so, do you happen to know why the packet socket send() call failed? -- Jouni Malinen PGP id EFC895FA _______________________________________________ Hostap mailing list Hostap@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/hostap
