From oberman@slan.es.net  Wed May 31 14:43:11 2006
Return-Path: <oberman@slan.es.net>
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 236FE16A6DB
	for <FreeBSD-gnats-submit@freebsd.org>; Wed, 31 May 2006 14:43:11 +0000 (UTC)
	(envelope-from oberman@slan.es.net)
Received: from slan.es.net (slan-lvk.es.net [198.128.4.60])
	by mx1.FreeBSD.org (Postfix) with ESMTP id E6DCD43D48
	for <FreeBSD-gnats-submit@freebsd.org>; Wed, 31 May 2006 14:43:10 +0000 (GMT)
	(envelope-from oberman@slan.es.net)
Received: by slan.es.net (Postfix, from userid 9381)
	id 780475C50; Wed, 31 May 2006 07:43:10 -0700 (PDT)
Message-Id: <20060531144310.780475C50@slan.es.net>
Date: Wed, 31 May 2006 07:43:10 -0700 (PDT)
From: Kevin Oberman <oberman@es.net>
Reply-To: Kevin Oberman <oberman@es.net>
To: FreeBSD-gnats-submit@freebsd.org
Cc:
Subject: wpa_supplicant blacklist not working
X-Send-Pr-Version: 3.113
X-GNATS-Notify:

>Number:         98218
>Category:       bin
>Synopsis:       wpa_supplicant(8) blacklist not working
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    freebsd-wireless
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Wed May 31 14:50:15 GMT 2006
>Closed-Date:    
>Last-Modified:  Wed Feb 19 20:28:45 CET 2014
>Originator:     Kevin Oberman
>Release:        FreeBSD 7.0-CURRENT i386
>Organization:
ESnet-The Energy Sciences Network
>Environment:
System: FreeBSD slan.es.net 7.0-CURRENT FreeBSD 7.0-CURRENT #15: Tue May 23 14:19:22 PDT 2006 root@slan.es.net:/usr/obj/usr/src/sys/IBM-T43 i386


	
>Description:
	If multiple BSSes match an entry in the wpa_supplicant.conf
file, it is possible that the BSS chosen will not associate, but
instead of blacklisting the BSS and trying another, the wpa_supplicant
continues to try to attach to the unusable BSS with a new attempt every
10 seconds.

This was observed in a non-secured situation. That is there were
multiple BSSes showing in the scan and the first had a very low signal
strength. The supplicant would try to associate with that BSS, but
could not. ifconfig always showed the interface with no carrier.

I believe that the supplicant should have blacklisted that BSS and
tried another on the list, but would keep trying the same one over and
over. Restarting the supplicant would cause a new list of BSSes to be
generated which was identical to the first except for order. If the
first BSS on the list proved functional, association would take place
and things progressed normally. If the first entry would not
associate, the same thing, re-attempts to associate with the same BSS
every 10 seconds would repeat.

For the record, the configuration file in question was my generic
wireless of:
network={
	ssid=""
	key_mgmt=NONE
	priority=0
}

My wireless card is an Atheros 5212, although inspection of the code
leads me to believe that this is not related to the card chosen.

>How-To-Repeat:
	Attempt to use the wpa_supplicant in an environment where
several APs are available, some of which have poor signals and will
not associate.
>Fix:
Modify the supplicant to blacklist a BSS that fails to associate so
that other available APs will be tried.


>Release-Note:
>Audit-Trail:
Responsible-Changed-From-To: freebsd-bugs->freebsd-net 
Responsible-Changed-By: vwe 
Responsible-Changed-When: Wed Jan 14 23:27:31 UTC 2009 
Responsible-Changed-Why:  

Over to maintainer(s). 

http://www.freebsd.org/cgi/query-pr.cgi?pr=98218 
State-Changed-From-To: open->feedback 
State-Changed-By: brueffer 
State-Changed-When: Wed Feb 19 16:52:12 CET 2014 
State-Changed-Why:  
Hi Kevin, wpa_supplicant has been updated since this PR was filed.  Do you 
still see this behaviour in newer FreeBSD releases? 

http://www.freebsd.org/cgi/query-pr.cgi?pr=98218 
State-Changed-From-To: feedback->closed 
State-Changed-By: brueffer 
State-Changed-When: Wed Feb 19 17:57:32 CET 2014 
State-Changed-Why:  
Hi Kevin, thanks for the quick answer and sorry this PR sat around for so 
long.  I close the PR with this, but in case you come into the situation where 
you can test this again, we'd be happy to hear your report. 

Happy retirement! 

http://www.freebsd.org/cgi/query-pr.cgi?pr=98218 
State-Changed-From-To: closed->open 
State-Changed-By: brueffer 
State-Changed-When: Wed Feb 19 20:27:18 CET 2014 
State-Changed-Why:  
Adrian says this is likely still an issue, open and assign to freebsd-wireless at his request. 


Responsible-Changed-From-To: freebsd-net->freebsd-wireless 
Responsible-Changed-By: brueffer 
Responsible-Changed-When: Wed Feb 19 20:27:18 CET 2014 
Responsible-Changed-Why:  
Adrian says this is likely still an issue, open and assign to freebsd-wireless at his request. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=98218 
>Unformatted:
