[BUG] wpa_supplicant in SAE mode kills AP on same PHY

[Charlemagne Lasse]

2017-02-25 8:59 GMT+01:00 Jouni Malinen <j at w1.fi>:
> On Thu, Feb 23, 2017 at 03:13:36PM +0100, Charlemagne Lasse wrote:
>> I found a weird problem in LEDE 17.01 with an ath9k device and
>> reported it at https://bugs.lede-project.org/index.php?do=details&task_id=550
>> . But it looks like it is a bug in hostapd/wpa_supplicant because I
>> cannot reproduce it when using authsae.
> Can you produce debug logs from both wpa_supplicant and hostapd for
> this?

Yes, here is the output from hostapd -ddddd (the STOP_AP happens after
starting WPA_SUPPLICANT):

nl80211: ssid - hexdump_ascii(len=8):
    6d 65 73 68 65 64 41 50                           meshedAP
nl80211: ssid - hexdump_ascii(len=8):
    6d 65 73 68 65 64 41 50                           meshedAP
RX ctrl_iface - hexdump_ascii(len=7):
    53 54 4f 50 5f 41 50                              STOP_AP
RX ctrl_iface - hexdump_ascii(len=7):
    53 54 4f 50 5f 41 50                              STOP_AP

The -ddddd output from wpa_supplicant is attached
-------------- next part --------------
A non-text attachment was scrubbed...
Name: wpa_supplicant.log
Type: text/x-log
Size: 27452 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/hostap/attachments/20170228/b97a1025/attachment-0001.bin>