Date: Tue, 31 May 2011 13:46:12 -0400 From: John Baldwin <jhb@freebsd.org> To: Bernhard Schmidt <bschmidt@freebsd.org> Cc: freebsd-hackers@freebsd.org, Yuri <yuri@rawbw.com> Subject: Re: ndis driver presents the valid WiFi network as having the name 0x000000 Message-ID: <201105311346.12267.jhb@freebsd.org> In-Reply-To: <201105311836.43543.bschmidt@freebsd.org> References: <4DE01421.7080902@rawbw.com> <201105311029.15259.jhb@freebsd.org> <201105311836.43543.bschmidt@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tuesday, May 31, 2011 12:36:43 pm Bernhard Schmidt wrote: > On Tuesday 31 May 2011 16:29:15 John Baldwin wrote: > > On Friday, May 27, 2011 5:14:09 pm Yuri wrote: > > > Underlying card is Broadcom BCM94312MCGSG (mini-card for laptop) with > > > Windows driver. > > > This same card and driver work fine with pretty much any other network I > > > tried. > > > But this one particular network shows as 0x000000 and I can't connect to it. > > > Another FreeBSD desktop with native ath driver and apple both connect to > > > it fine. > > > > > > What might be causing such weird behavior? > > > Is this a known problem? > > > Any way to troubleshoot this? > > > > I have this same problem. I've had to resort to using wpa_cli to 'select' my > > network at work that has this issue and then using 'ap_scan 2' to force > > wpa_supplicant to associate with it. You also will want ndis_events running > > if you need to do WPA authentication. > > Are you using -D bsd or -D ndis as the driver for wpa_supplicant? Whatever the defaults are (which would be -B ndis). -- John Baldwin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201105311346.12267.jhb>