From owner-freebsd-mobile@FreeBSD.ORG Tue Dec 22 23:21:34 2009 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 5C0961065670 for ; Tue, 22 Dec 2009 23:21:34 +0000 (UTC) (envelope-from freebsd-mobile@m.gmane.org) Received: from lo.gmane.org (lo.gmane.org [80.91.229.12]) by mx1.freebsd.org (Postfix) with ESMTP id 167AC8FC19 for ; Tue, 22 Dec 2009 23:21:34 +0000 (UTC) Received: from list by lo.gmane.org with local (Exim 4.50) id 1NNDiK-0003wY-6o for freebsd-mobile@freebsd.org; Wed, 23 Dec 2009 00:00:24 +0100 Received: from 200.41.broadband11.iol.cz ([90.178.41.200]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 23 Dec 2009 00:00:24 +0100 Received: from gamato by 200.41.broadband11.iol.cz with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 23 Dec 2009 00:00:24 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-mobile@freebsd.org From: martinko Date: Tue, 22 Dec 2009 23:59:57 +0100 Lines: 73 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: 200.41.broadband11.iol.cz User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.9.1.6) Gecko/20091220 SeaMonkey/2.0.1 In-Reply-To: Sender: news Subject: Re: iwi connect problems in 9.0-CURRENT 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: Tue, 22 Dec 2009 23:21:34 -0000 michael brindle wrote: > Hey all. > I recently upgraded to 9.0-CURRENT from 7.2-RELEASE, to help test and debug > it. > The only problem I've encountered so far that I've not yet been able to fix > is that I have yet to get my wireless card (Intel IPW 2200 b/g) to connect > to my wireless network (which has an Apple Airport as the wireless router). > Hallo, I've just upgraded to 8.0-release and I'm seeing some issues too. > my /etc/rc.conf file (with unrelated parts deleted): > wlans_iwi0="wlan0" > defaultroute=192.168.1.1 > ifconfig_wlan0="up" > ifconfig_wlan0="DHCP" > > my /etc/start_if.wlan0 file: > ifconfig wlan0 ssid BrinNet channel 1 authmode shared wepmode on wepkey PASS > weptxkey 1 > First, off-topic, I'm wondering why you do it as above .. ? These 2 lines are IMHO unnecessary: defaultroute=192.168.1.1 ifconfig_wlan0="up" Also, you could get rid off of /etc/start_if.wlan0 and use wpa_supplicant(8) that is very convenient and powerful. > with the license agreed to, as stated in the iwi(4) man page. > > dhclient will discover my network. However, it won't get any offers from it. > DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 5 > DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7 > DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 10 > DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 11 > DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 15 > DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 13 > No DHCPOFFERS received. > No working leases in persistent database - sleeping > > Another thing I noticed, the output of ifconfig wlan0 > wlan0: flags=8843 metric 0 mtu 1500 > ether 00:0e:35:20:37:0a > inet 0.0.0.0 netmask 0xff000000 broadcast 255.255.255.255 > media: IEEE 802.11 Wireless Ethernet autoselect mode 11b > status: associated > ssid BrinNet channel 1 (2412 Mhz 11b) bssid 00:60:1d:f1:51:1b > country US authmode OPEN privacy ON deftxkey 1 wepkey 1:40-bit > txpower 0 bmiss 24 scanvalid 60 wme > > most importantly, the txpower being set to 0, because I cannot change it at > all, or even reconfirm that it's at 0: > younata# ifconfig wlan0 txpower 1 > ifconfig: SIOCS80211: Operation not supported > younata# ifconfig wlan0 txpower 0 > ifconfig: SIOCS80211: Operation not supported > > So, my questions are: > Why is txpower set to 0, what does that mean? That it can't transmit at all? > Why can I not manually change it? > Which leads to the ultimate question of: > How do I get it to connect? > The same here -- txpower is zero while it used to be non-zero before (on 6.x). Seems like a bug or something. Regards, Martin