On Mon, Oct 10, 2016 at 4:32 PM, Bob Copeland <me@xxxxxxxxxxxxxxx> wrote:
> Ah, ok, that probably explains it. I think there is an outstanding issue
> with the default rateset in wpa_s not matching that of the in-kernel
> peering manager.
Before I initially contacted the mailing list, I noticed that wpa_s
defaults to HT20 mode while iw does not default to HT mode, so I
enabled HT mode on the end configured with iw. Alas, it didn't fix
the issue.
> You can set user_mpm = 0 in wpa_s will use the kernel MPM in both cases,
> and that should work. If not, let us know. In the meantime I'll take a
> stab at fixing this issue.
Setting user_mpm = 0 didn't work. Below is a piece of the output from
wpa_s. I'm still working on that pcap. I'll get it as soon as I can.
Thanks for the support.
~Nate
wlan0: skip - SSID mismatch
wlan0: 24: 18:a6:f7:07:73:b0 ssid='mz_mesh' wpa_ie_len=0 rsn_ie_len=0
caps=0x0 level=-28 freq=2412
wlan0: allow in non-WPA/WPA2
wlan0: selected BSS 18:a6:f7:07:73:b0 ssid='mz_mesh'
wlan0: Considering connect request: reassociate: 0 selected:
18:a6:f7:07:73:b0 bssid: 00:00:00:00:00:00 pending:
00:00:00:00:00:00 wpa_state: SCANNING ssid=0x17001a8
current_ssid=(nil)
wlan0: Request association with 18:a6:f7:07:73:b0
wlan0: user_mpm is not enabled in configuration
wlan0: joining mesh mz_mesh
nl80211: mesh join (ifindex=3)
* freq=2412
* vht_enabled=0
* ht_enabled=1
* sec_channel_offset=0
* channel_type=1
* Mesh ID (SSID) - hexdump_ascii(len=7):
6d 7a 5f 6d 65 73 68 mz_mesh
* flags=00000002
nl80211: mesh join failed: ret=-95 (Operation not supported)
wlan0: mesh join error=-95
nl80211: Set wlan0 operstate 0->1 (UP)
netlink: Operstate: ifindex=3 linkmode=-1 (no change), operstate=6 (IF_OPER_UP)
wlan0: Could not join mesh
RTM_NEWLINK: ifi_index=3 ifname=wlan0 wext ifi_family=0 ifi_flags=0x1003 ([UP])
_______________________________________________
Hostap mailing list
Hostap@xxxxxxxxxxxxxxxxxxx
http://lists.infradead.org/mailman/listinfo/hostap
