On Fri, Mar 02, 2018 at 03:11:00PM -0500, msiedzik@xxxxxxxxxxxxxxxxxxx wrote: > If a live peer ever changes its Member Identifier (MI), the KaY > correctly detects a "duplicated SCI" but then proceeds to delete the > peer without deleting the peer's resources (i.e., RxSC, RxSAs, TxSAs). > > Note that a remote peer's MI will change if and when a > ieee8021XPaePortInitialize is executed on the remote port. > > The solution here is to ignore all MKPDUs containing the new MI until > after the peer (that corresponds to the old MI) expires and cleans up > its resources. After the old peer is removed reception of the next > MKPDU containing the new MI will result in the creation of a new peer > with the new MI. Thanks, applied. -- Jouni Malinen PGP id EFC895FA _______________________________________________ Hostap mailing list Hostap@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/hostap
