On 2015/12/17 13:22, Stefan Sperling wrote: > On Thu, Dec 17, 2015 at 12:40:48PM +0100, Marcus MERIGHI wrote: > > iwn0: sending auth to 80:1f:02:c1:fd:86 on channel 5 mode 11b > > iwn0: sending assoc_req to 80:1f:02:c1:fd:86 on channel 5 mode 11b > > iwn0: received auth from 80:1f:02:c1:fd:86 rssi -54 mode 11b > > iwn0: association failed (status 18) for 80:1f:02:c1:fd:86 > > IEEE80211_STATUS_BASIC_RATE = 18, > > This could mean we're sending a bad basic rate element in > association requests while in 11n mode. I'll investigate. > > Is your AP restricting clients to a particular mode, like 11g-only? > Perhaps it means your AP requires clients to support MCS higher > than MCS 7, which we don't support yet? > > Can you somehow change AP settings in this regard? >
It seems that some APs get upset if you send rates that are not in their advertised list. https://supportforums.cisco.com/document/141136/80211-association-status-80211-deauth-reason-codes says "Will happen if the rates in the assoc request are not in the BasicRateSet in the beacon" for this. We don't do much decode of assoc requests in tcpdump at the moment. Marcus, it might be useful to get a pcap file (tcpdump -s1500 -iiwn0 -yIEEE802_11_RADIO -w /tmp/iwn.pcap) from while it's trying to associate - if you send it to me off list (and probably best to cc stsp) I can take a look and see if I spot anything.
