On Mon, Dec 21, 2015 at 2:14 PM, Jouni Malinen <j@xxxxx> wrote: > On Mon, Dec 21, 2015 at 11:52:32AM -0800, Galen Seitz wrote: >> We are also continuing to to work on collecting relevant time-correlated >> packet and wpa_supplicant logs. In the meantime, I thought I would ask >> whether anyone has any seen this type of problem and whether there is a >> fix or workaround. > > There are way too many possible reasons for this type of issues to even > try to speculate on what could have happened without seeing those logs. > In other words, I'd recommend trying again once the logs are available.. Jouni, et al. Here are links to the wpa_supplicant log and an over-the-air packet capture made from a nearby device, respectively: https://personaltelco.net/~russell/wpa2j.log https://personaltelco.net/~russell/snoopy2j.pcap The two radios of importance are station: 00:0a:52:25:f9:3a and AP: 30:5a:3a:51:53:c8. There are lots of other radios nearby, so it helps to filter the pcap file. The clocks for logging device and the pcap'ing device had a chance to synchronize to ntp servers prior to the captures, so the clocks should be at least close, within the precision of embedded devices. In this connection, several timeouts occurred before eventual success. From the packet captures, the 4-way handshake appears to be finally successful when the replay counter of the 4of4 is equal to the replay counter of the most recent in 3of4. The station (00:0a:52:25:f9:3a) in this instance is running a slightly customized OpenWrt r46505. I have tried a very recent version of OpenWrt as well, without notable improvement. Thanks! _______________________________________________ Hostap mailing list Hostap@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/hostap
