On Tue, 2014-12-02 at 16:35 -0600, Brent Taylor wrote: > 1417557229.339147: WPA: RSN IE in EAPOL-Key - hexdump(len=22): 30 14 > 01 00 00 0f ac 04 01 00 00 0f ac 04 01 00 00 0f ac 02 00 00 > 1417557229.339179: WPA: RSN IE in Beacon/ProbeResp - hexdump(len=26): > 30 18 01 00 00 0f ac 04 02 00 00 0f ac 04 00 0f ac 02 01 00 00 0f ac > 02 00 00 > 1417557229.339192: WPA: RSN IE in 3/4 msg - hexdump(len=22): 30 14 01 > 00 00 0f ac 04 01 00 00 0f ac 04 01 00 00 0f ac 02 00 00 On the STA side: The RSN IE in the EAPOL-Key and the 3/4msg are the same, and contain only the CCMP pairwise suite. The RSN IE in the Beacon/ProbeResp debug message contains both CCMP and TKIP pairwise suites. Earlier in the run we have: 1417557228.979261: WPA: set AP RSN IE - hexdump(len=26): 30 18 01 00 00 0f ac 04 02 00 00 0f ac 04 00 0f ac 02 01 00 00 0f ac 02 00 00 1417557228.979342: WPA: Set own WPA IE default - hexdump(len=22): 30 14 01 00 00 0f ac 04 01 00 00 0f ac 04 01 00 00 0f ac 02 00 00 which is where the extra TKIP bit comes from. I'm guessing this is from wpa_supplicant_set_suites() because of the closely paired AP RSN IE/own WPA IE calls. Brent, is there any chance you can run the supplicant on the laptop with "-dddt" to get *all* the debug messages? It seems the logs are missing quite a few that could tell us where wpa_supplicant_set_suites() is getting called. Dan _______________________________________________ ath6kl mailing list ath6kl@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/ath6kl
