Date: Tue, 19 Oct 2010 08:30:37 +0200 From: Bernhard Schmidt <bschmidt@techwires.net> To: Buganini <buganini@gmail.com> Cc: FreeBSD Current <freebsd-current@freebsd.org> Subject: Re: wpa_supplicant and ssid Message-ID: <201010190830.37974.bschmidt@freebsd.org> In-Reply-To: <AANLkTi=man27aW4Sy3Qy64OuZbcS_GP2gqVsx5rE5usW@mail.gmail.com> References: <AANLkTi=man27aW4Sy3Qy64OuZbcS_GP2gqVsx5rE5usW@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Monday, October 18, 2010 18:55:34 you wrote: > It seems that wpa_supplicant iterate through all scanned ssids and try to > associate with each, > and that cause two problem for me. > > 1) in my school, there are many AP, and connection is not stable, when > disconnect, > it take many time to try and fail to associate with those ssids until the > one I want. You can add a 'priority' statement to each network block in wpa_supplicant.conf. > 2) i can't associate with a non-discoverable ssid > > but probably it is my wireless driver's problem, > i'm using bwn0 and currently I need to force it to use mode 11b or it is > unusable. Tried different options for the scan_ssid parameter? > or should I complain to upstream ? Before doing so, can you capture the output of 'wlandebug 0xffffffff' while trying to get a connection? -- Bernhard
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201010190830.37974.bschmidt>