From owner-freebsd-questions@FreeBSD.ORG Sat Jul 30 18:30:51 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 120D016A41F for ; Sat, 30 Jul 2005 18:30:51 +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 A70B443D45 for ; Sat, 30 Jul 2005 18:30:50 +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 j6UIUmms093596 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 30 Jul 2005 11:30:48 -0700 (PDT) (envelope-from sam@errno.com) Message-ID: <42EBC77F.1010601@errno.com> Date: Sat, 30 Jul 2005 11:31:27 -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> In-Reply-To: <42EBC41E.4070102@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 18:30:51 -0000 Eric Schuele wrote: > Sam Leffler wrote: > >> Sam Leffler wrote: >> >>> Brooks fixed a bunch of bugs in dhclient and I just committed an >>> important fix to wpa_supplicant to work right when wireless cards are >>> ejected (previously it would loop). >>> >>> I also tested that dhclient does the right thing for roaming between >>> ap's--switching causes dhclient to immediately collect a new lease. >>> >>> I just ran tests with wpa_supplicant and found that it does appear to >>> handle open ap's properly. >>> >>> Everything except the wpa_supplicant changes have been MFC'd to >>> RELENG_6 for the 6.0RC2 build that's going to happen soon (I'm hoping >>> to get re to approve the wpa_supplicant changes). >> >> >> >> FWIW I just MFC'd the wpa_supplicant fix. >> >>> >>> So the question is what are the outstanding issues with dhclient and >>> wpa_supplicant? I'm mostly concerned with wireless devices but feel >>> free to talk about wired interfaces too. If something doesn't work >>> right please try to give steps to reproduce the problem. Otherwise >>> please provide detailed info include ifconfig output. Remember that >>> dhclient logs info to /var/log/messages and you should also see link >>> state change msgs there too. >> >> >> >> s/6.0RC2/6.0BETA2/. >> >> Sam >> _______________________________________________ >> freebsd-current@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-current >> To unsubscribe, send any mail to >> "freebsd-current-unsubscribe@freebsd.org" >> > Hello, > > I am very interested in getting wpa_supplicant & dhclient to work. > Presently it does not work for me the way I would hope it would. > > I would think that if it were setup properly on my machine I could turn > the machine on at home, and have it associate with my AP and then > acquire a lease. Then I could shut it down... go to the office... turn > it on and then have it associate with the AP there and acquire a lease. > > However it does not seem to do this. It seems to only want to associate > with the last AP it ever associated with. I then have to down the > interface and manually ifconfig it. > > I am fairly sure I do not have things setup properly, since others have > had much better results. Can you please point me to the most current > docs or a "How To" to push me in the right direction. > > I have RELENG_6 as of last night. I have appended some conf files to > the bottom for your review. > > Thanks, > > rc.conf contains > =========================== > network_interfaces="lo0 bfe0 ath0" > ifconfig_ath0="WPA DHCP" > ifconfig_bfe0="DHCP" > > 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. > > 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. Sam