Date: Tue, 8 Aug 2006 17:26:57 -0400 From: Dylan Alex Simon <dylan@dylex.net> To: Doug Barton <dougb@FreeBSD.org> Cc: freebsd-net@FreeBSD.org Subject: Re: wpa_supplicant on ndis cannot associate Message-ID: <20060808212657.GA29190@dylex.dylex.net> In-Reply-To: <44D4E939.3060607@FreeBSD.org> References: <20060805153714.GA22424@dylex.dylex.net> <44D4E939.3060607@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> Are you by any chance not broadcasting the ssid on the WAP? I had problems > similar to what you described when I turned that feature off, but when I > turned it back on (so the WAP was broadcasting its ssid again) everything > worked fine with wpa-psk and TKIP, and -D ndis. (I could not get any > "higher" level of WPA working, but that's another story.) The SSID is being broadcast (and shows up on the scan). Actually, trying in a controlled setup, it does work when I use RSN/WPA-PSK/TKIP with -D ndis. However, it does not work with an open AP (no encryption/authentication). wpa_supplicant seems to say that it will work with open networks if so configured (key_mgmt=NONE). Is this not the case? I roam between a few open networks that use a separate vpn layer for security, and I'd really like to have it automatically figure out which to use (and then setup the right vpn too). I considered using dhclient.conf media settings, but it sounds like that won't work either. :-Dylan
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060808212657.GA29190>