On Mon, Apr 17, 2017 at 11:44:01AM -0500, Dan Williams wrote: > On Sat, 2017-04-15 at 10:56 +0200, Gilles wrote: > > https://pastebin.com/raw/mhumwTkp > > The first attempt successfully associates and 4-way handshakes with the > AP. But then there is no DHCP reply, so NetworkManager terminates the > connection because it cannot get an IP address. > > Then NM asks the supplicant to try again. The supplicant associates > successfully, but then never receives the EAPOL frame from the AP that > starts the 4-way handshake. After a few seconds (waiting for that > frame) the driver disconnects from the AP (Reason: > 15=4WAY_HANDSHAKE_TIMEOUT). > > All further attempts result in (Reason: 15=4WAY_HANDSHAKE_TIMEOUT). > > This is either a driver/supplicant problem, or an AP problem. There > could be a race condition in the supplicant or driver that is > discarding the EAPOL frame after association but before it's in a state > to process the start of the 4-way handshake. If other devices work > fine with this AP, that's what I'd guess the problem is. That looks more like a lower layer issue of getting packets through than some kind of a race condition. In other words, that would require someone to take a look at the drivers and/or wireless capture to make more sense to what is happening. -- Jouni Malinen PGP id EFC895FA _______________________________________________ Hostap mailing list Hostap@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/hostap
