From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from he.sipsolutions.net ([78.46.109.217]:51910 "EHLO sipsolutions.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755503Ab0IJQha (ORCPT ); Fri, 10 Sep 2010 12:37:30 -0400 To: Ben Greear Subject: Re: RFC: Allow multiple STA connected to same AP. MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Date: Fri, 10 Sep 2010 18:37:28 +0200 From: Johannes Berg Cc: In-Reply-To: <4C89B98F.3090000@candelatech.com> References: <4C8959BC.7040501@candelatech.com> <7fa0decef9a717c1562ee155bba78ce9@localhost> <4C896747.6090905@candelatech.com> <9b3afa510682d20c031f85f20345abd7@localhost> <4C89B98F.3090000@candelatech.com> Message-ID: <848696fe638aa1c29d8420fc9186fee9@localhost> Sender: linux-wireless-owner@vger.kernel.org List-ID: On Thu, 09 Sep 2010 21:52:31 -0700, Ben Greear 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. johannes