From owner-freebsd-current@FreeBSD.ORG Mon Mar 16 20:49:15 2009 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EE7B7106566B for ; Mon, 16 Mar 2009 20:49:14 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mx22.fluidhosting.com [204.14.89.5]) by mx1.freebsd.org (Postfix) with ESMTP id 9C3DA8FC2A for ; Mon, 16 Mar 2009 20:49:14 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: (qmail 21716 invoked by uid 399); 16 Mar 2009 20:49:10 -0000 Received: from localhost (HELO lap.dougb.net) (dougb@dougbarton.us@127.0.0.1) by localhost with ESMTPAM; 16 Mar 2009 20:49:10 -0000 X-Originating-IP: 127.0.0.1 X-Sender: dougb@dougbarton.us Message-ID: <49BEBB45.7050605@FreeBSD.org> Date: Mon, 16 Mar 2009 13:49:09 -0700 From: Doug Barton Organization: http://www.FreeBSD.org/ User-Agent: Thunderbird 2.0.0.19 (X11/20090312) MIME-Version: 1.0 To: freebsd-current@FreeBSD.org X-Enigmail-Version: 0.95.7 OpenPGP: id=D5B2F0FB Content-Type: multipart/mixed; boundary="------------050601030103070007000708" Cc: Subject: Is wpa_supplicant supposed to work with a hidden ssid? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Mar 2009 20:49:15 -0000 This is a multi-part message in MIME format. --------------050601030103070007000708 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit I spent a pretty long, frustrating evening last night getting wpa_supplicant working with my Intel 3945abg (wpi) card. I could connect when the network was open, or using WEP just fine. However it turned out that I could not connect with WPA unless the AP was showing the ssid. Now hiding ssid is not a show-stopper for me, I just think it's odd that I can't do it. FWIW, I vaguely recall that the same thing was true with ath-based cards as well. I still have one somewhere, and I can double-check this if anyone is interested. Now this seems to be related to the fact that we can only use ap_scan=1 with the wlan module. The description in the example conf file seems to indicate that setting that option to 2 would do the trick, but the man page for wpa_supplicant.conf says that we can only use ap_scan=1. Therefore I'd like to propose the attached patch which would have saved me a lot of time flailing around with this (since I assumed that the example conf file had the necessary information). Since we have svn now, the "pristine" copy of the file will still live on in the vendor tree, and there is no "expense" to changing things in contrib like there was with cvs. Doug -- This .signature sanitized for your protection --------------050601030103070007000708 Content-Type: text/plain; name="wpa_supp.diff" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="wpa_supp.diff" Index: wpa_supplicant.conf =================================================================== --- wpa_supplicant.conf (revision 189866) +++ wpa_supplicant.conf (working copy) @@ -84,24 +84,7 @@ eapol_version=1 # AP scanning/selection -# By default, wpa_supplicant requests driver to perform AP scanning and then -# uses the scan results to select a suitable AP. Another alternative is to -# allow the driver to take care of AP scanning and selection and use -# wpa_supplicant just to process EAPOL frames based on IEEE 802.11 association -# information from the driver. -# 1: wpa_supplicant initiates scanning and AP selection -# 0: driver takes care of scanning, AP selection, and IEEE 802.11 association -# parameters (e.g., WPA IE generation); this mode can also be used with -# non-WPA drivers when using IEEE 802.1X mode; do not try to associate with -# APs (i.e., external program needs to control association). This mode must -# also be used when using wired Ethernet drivers. -# 2: like 0, but associate with APs using security policy and SSID (but not -# BSSID); this can be used, e.g., with ndiswrapper and NDIS drivers to -# enable operation with hidden SSIDs and optimized roaming; in this mode, -# the network blocks in the configuration file are tried one by one until -# the driver reports successful association; each network block should have -# explicit security policy (i.e., only one option in the lists) for -# key_mgmt, pairwise, group, proto variables +# For use in FreeBSD with the wlan module ap_scan must be set to 1. ap_scan=1 # EAP fast re-authentication --------------050601030103070007000708--