From owner-freebsd-questions@FreeBSD.ORG Sat Jul 30 21:58:00 2005 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0126B16A41F for ; Sat, 30 Jul 2005 21:58:00 +0000 (GMT) (envelope-from sam@errno.com) Received: from ebb.errno.com (ebb.errno.com [66.127.85.87]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9B5B743D45 for ; Sat, 30 Jul 2005 21:57:59 +0000 (GMT) (envelope-from sam@errno.com) Received: from [66.127.85.93] ([66.127.85.93]) (authenticated bits=0) by ebb.errno.com (8.12.9/8.12.6) with ESMTP id j6ULvvms094242 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 30 Jul 2005 14:57:57 -0700 (PDT) (envelope-from sam@errno.com) Message-ID: <42EBF80C.7030702@errno.com> Date: Sat, 30 Jul 2005 14:58:36 -0700 From: Sam Leffler Organization: Errno Consulting User-Agent: Mozilla Thunderbird 1.0.2 (Macintosh/20050317) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Eric Schuele References: <42EAD325.60707@errno.com> <42EAD80C.9060707@errno.com> <42EBC41E.4070102@computer.org> <42EBC77F.1010601@errno.com> <42EBD3A0.5070407@computer.org> In-Reply-To: <42EBD3A0.5070407@computer.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: FreeBSD Questions Subject: Re: dhclient and wpa_supplicant X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 30 Jul 2005 21:58:00 -0000 Eric Schuele wrote: > Sam Leffler wrote: > >> Eric Schuele wrote: >> > > > >>> dhclient.conf contains >>> =========================== >>> interface "ath0" { >>> #send option host-name "myhost"; >>> #send option domain-name "nxdomain.org"; >>> send dhcp-client-identifier "myhost"; >>> >>> media >>> ### Home >>> "ssid mode 11b channel 11 wepmode on weptxkey 1 wepkey >>> 0x", >>> ### Office >>> "ssid >> 0x"; >>> request subnet-mask, broadcast-address, routers, >>> domain-name-servers, domain-name; >>> } >> >> >> >> Do not use media statements to setup wireless parameters; this does >> not work. You need to run wpa_supplicant and let it identify the >> network and setup the key parameters. > > > How do I tell wpa_supplicant about the network media? I had found an > older post of yours regarding NOT doing it in dhclient.conf.... but I've > found no other way to accomplish it. The above dhclient.conf lists media settings that are all handled by wpa_supplicant so you don't specify any of them. Specifically you set ssid, band, channel, and wep parameters; all these are handled by wpa_supplicant. The intent is that dhclient deal only with the dhcp protocol and stop being involved in the discovery and selection of wireless networks (a job wpa_supplicant is better equipped to handle). > >> >>> >>> wpa_supplicant.conf >>> ============================= >>> ctrl_interface=/var/run/wpa_supplicant >>> ctrl_interface_group=wheel >>> >>> # Home Network >>> network={ >>> ssid="" >>> scan_ssid=1 >>> key_mgmt=NONE >>> wep_tx_keyidx=0 >>> wep_key0="" >>> } >>> >>> # Office Network >>> network={ >>> ssid="" >>> scan_ssid=1 >>> key_mgmt=NONE >>> wep_tx_keyidx=0 >>> wep_key0="" >>> } >>> >> >> Not sure you need scan_ssid set, I'd leave it out. >> >> If you have problems try disabling auto-startup of ath0 and run >> wpa_supplicant by hand with the -d flag to see what it's doing. Once >> that's going then enable startup in rc.conf. If you continue to have >> problems provide the output wpa_supplicant -d -i ath0 -c >> /etc/wpa_supplicant.conf (or similar) when you have trouble. There is >> also a pending issue with locating some ap's that are setup to hide >> their ssid. If one of the ap's is configured in this way contact me >> directly--I've been trying to collect the info I need to identify >> what's going on. > > > Both my APs (home and office) hide their ssids. One is a wrt54g (home), > the other is linksys as well... though I forget the model at the moment > (FWIW its a/b/g). What can I do to provide the info you need? These should work; I've had reports of problems with certain Cisco ap's. Note however that configuring an ap to hide it's ssid adds no real security. Sam