Subject: Re: RFC:  mac80211/ath9k:  allow scanning single channel if other
 VIF is associated.
From: Johannes Berg <johannes@sipsolutions.net>
To: Ben Greear <greearb@candelatech.com>
Cc: Jouni Malinen <j@w1.fi>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
In-Reply-To: <4C90E708.5050109@candelatech.com>
References: <4C8EB03D.7070808@candelatech.com>
	 <20100915030316.GB30253@jm.kir.nu>  <4C9059DC.7060009@candelatech.com>
	 <1284545796.3842.11.camel@jlt3.sipsolutions.net>
	 <4C90D683.7000801@candelatech.com>
	 <1284560664.7705.3.camel@jlt3.sipsolutions.net>
	 <4C90E708.5050109@candelatech.com>
Content-Type: text/plain; charset="UTF-8"
Date: Wed, 15 Sep 2010 17:37:13 +0200
Message-ID: <1284565033.7705.5.camel@jlt3.sipsolutions.net>
Mime-Version: 1.0
Sender: linux-wireless-owner@vger.kernel.org

On Wed, 2010-09-15 at 08:32 -0700, Ben Greear wrote:

> >> Right, but as soon as one finished, the next would start, and at least in .31,
> >> that caused the first to un-associate, giving never-ending loop of interfaces
> >> scanning and trying to associate.
> >
> > There should be a grace period maybe?
> 
> I don't think that really fixes anything, except make the race between
> full scan and attempting for the first interface to associate harder to
> hit (and that is only useful if the scan-one logic is enabled anyway).

I think you just need to update ... newer kernels shouldn't be allowing
a scan while trying to associate, I think.

johannes