On Fri, Mar 02, 2018 at 03:11:03PM -0500, msiedzik@xxxxxxxxxxxxxxxxxxx wrote: > To prevent a remote peer from getting stuck in a perpetual 'potential > peer' state, only update the peer liveness timer 'peer->expire' for live > peers and not for potential peers. > > Per IEEE802.1X-2010 9.4.3 Determining liveness, potential peers need to > show liveness by including our MI/MN in their transmitted MKPDU (within > potential or live parameter sets). > > When a potential peer does include our MI/MN in an MKPDU, we respond by > moving the peer from 'potential_peers' to 'live_peers'. > > If a potential peer does not include our MI/MN in an MKPDU within > MKPDU_LIFE_TIME, then let the peer expire to facilitate getting back in > sync with the remote peer. Thanks, applied. -- Jouni Malinen PGP id EFC895FA _______________________________________________ Hostap mailing list Hostap@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/hostap
