On Wed, 2012-06-20 at 17:23 +0300, Luciano Coelho wrote: > If an AP is beaconing with different capabilities than the one we get > in the associate response, we were still using the capabilities > received in the beacons. One example is when the AP is beaconing with > the short slot bit set to zero and then we try to connect to it with > long slot. In this case, we would keep using long slot until the next > beacon was received. > > Fix this by using the correct capability value when calling > ieee80211_handle_bss_capability(). We were using cbss->capability, > but we should use the bss_conf->assoc_capability instead. Applied. johannes -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
