On 09/10/2010 09:37 AM, Johannes Berg wrote:
On Thu, 09 Sep 2010 21:52:31 -0700, Ben Greear<greearb@xxxxxxxxxxxxxxx>
wrote:
After some more debugging, it seems at least part of the problem is that
ath9k uses ieee80211_iterate_active_interfaces_atomic to determine which
MACs to add to the BSSID mask. But, before things are associated
properly,
sdata isn't 'running', so ath9k doesn't calc the mask properly.
Looks a bit like chicken-and-egg issue, and for some reason, it doesn't
seem to happen with WPA (but then, WPA doesn't authenticate properly
either).
Maybe a new iterator is needed to get interfaces that want to go active
(maybe by determining if sdata->dev is 'UP') ?
Err, that's exactly what the active interfaces iterator does. sdata is
in fact 'running' as soon as the interface is UP.
Maybe that bssidmask logic runs before sdata is actually brought up
then. I'll keep poking at things.
Thanks,
Ben
--
Ben Greear <greearb@xxxxxxxxxxxxxxx>
Candela Technologies Inc http://www.candelatech.com
--
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
