750403f3ad
The key server may be removed due to the ingress packets delay. In this situation, the endpoint of the key server may not be aware of this participant who has removed the key server from the peer list. Because the egress traffic is normal, the key server will not remove this participant from the peer list of the key server. So in the next MKA message, the key server will not dispatch a new SAK to this participant. And this participant cannot be aware of that that is a new round of communication so that it will not update its MI at re-adding the key server to its peer list. So we need to update MI to avoid the failure of re-establishment MKA session. Signed-off-by: Ze Gan <ganze718@gmail.com> |
||
|---|---|---|
| .. | ||
| ieee802_1x_cp.c | ||
| ieee802_1x_cp.h | ||
| ieee802_1x_kay.c | ||
| ieee802_1x_kay.h | ||
| ieee802_1x_kay_i.h | ||
| ieee802_1x_key.c | ||
| ieee802_1x_key.h | ||
| ieee802_1x_secy_ops.c | ||
| ieee802_1x_secy_ops.h | ||
| Makefile | ||