From owner-freebsd-mobile@FreeBSD.ORG Sun Jan 24 07:04:14 2010 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 554CF106566B for ; Sun, 24 Jan 2010 07:04:14 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mx21.fluidhosting.com [204.14.89.4]) by mx1.freebsd.org (Postfix) with ESMTP id EFDB38FC0A for ; Sun, 24 Jan 2010 07:04:13 +0000 (UTC) Received: (qmail 15650 invoked by uid 399); 24 Jan 2010 07:04:13 -0000 Received: from localhost (HELO foreign.dougb.net) (dougb@dougbarton.us@127.0.0.1) by localhost with ESMTPAM; 24 Jan 2010 07:04:13 -0000 X-Originating-IP: 127.0.0.1 X-Sender: dougb@dougbarton.us Message-ID: <4B5BF0F3.3090402@FreeBSD.org> Date: Sat, 23 Jan 2010 23:04:19 -0800 From: Doug Barton Organization: http://SupersetSolutions.com/ User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.9.1.7) Gecko/20100123 Thunderbird/3.0.1 MIME-Version: 1.0 To: knowtree@aloha.com References: <201001211829.o0LIT3xR020721@yoda.pixi.com> In-Reply-To: <201001211829.o0LIT3xR020721@yoda.pixi.com> X-Enigmail-Version: 1.0 OpenPGP: id=D5B2F0FB Content-Type: multipart/mixed; boundary="------------030605020405060802020005" Cc: freebsd-mobile@freebsd.org Subject: Re: wi (Lucent) panics on ifconfig wi0 up X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 24 Jan 2010 07:04:14 -0000 This is a multi-part message in MIME format. --------------030605020405060802020005 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit On 01/21/10 08:29, knowtree@aloha.com wrote: > ifconfig wlan0 ssid MYNET > > sets the ssid but > > ifconfig wlan0 up > > does nothing ... no carrier. You want to up the wlan0 interface first thing, otherwise you will get weirdness. When testing manually I can usually do: ifconfig wlan0 up ssid blah with a good success rate, but if you're still having problems with that then you may have to do it as; ifconfig wlan0 up ifconfig wlan0 ssid blah Also, if you're testing with a lot of different configurations I find it useful to completely reset the thing each time, otherwise, once again, weirdness. I use the attached script (which I think I've cleaned up enough to make it usable for you). After you run this you should be able to do 'ifconfig wlan0 up' and start fresh. Also, please be aware that wi cards are very limited, and since they are not in wide use anymore the code hasn't had a lot of love and attention in recent years. Good luck, Doug -- Improve the effectiveness of your Internet presence with a domain name makeover! http://SupersetSolutions.com/ Computers are useless. They can only give you answers. -- Pablo Picasso --------------030605020405060802020005 Content-Type: text/plain; name="reset-wlan" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="reset-wlan" #!/bin/sh wif=wi0 [ -n "$1" ] && wif=$1 if [ -z "$wif" ]; then echo "Need a wireless interface name" exit 1 fi pkill dhclient ifconfig wlan0 down sleep 1 ifconfig wlan0 destroy ifconfig $wif down sleep 1 ifconfig $wif up ifconfig wlan0 create wlandev $wif ifconfig $wif ifconfig wlan0 exit 0 --------------030605020405060802020005--