From owner-freebsd-mobile@FreeBSD.ORG Mon Nov 23 07:16:16 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 2A53C1065676; Mon, 23 Nov 2009 07:16:16 +0000 (UTC) (envelope-from onemda@gmail.com) Received: from mail-ew0-f226.google.com (mail-ew0-f226.google.com [209.85.219.226]) by mx1.freebsd.org (Postfix) with ESMTP id 812848FC1B; Mon, 23 Nov 2009 07:16:15 +0000 (UTC) Received: by ewy26 with SMTP id 26so1684653ewy.3 for ; Sun, 22 Nov 2009 23:16:14 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=VHg/PArdrPusyMJREs1EfIkHfMEjWnD3VCXScaZlB20=; b=tzCcFAwCEOvr0CsIZd3WyA/l/MvFbYS8R9k3UOpq6OCcQEXlErItk/UgK12nb5gz7W laf8ocaNoiiIP7vEw/8FFuU9tZBJ1hAkpXgEnXszLPufqW2b0rOYjAZH2XhX2Z4/dtSZ l8tl95JRYtjMdt0eMjUbJ/LgIwIh/JrgfXI3Q= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=PxEIsMSG6ooVdaz05gMcfWP3uTJv2aI4M1bSLJ4NVMXZOoN8o/Onc537cjUSH5DYR9 D5gA6tDea7rPQEnER9CVBgSPt1xwNau2tXI8SRPV+tx83V0Ccca0GL5Q+qyCMFLhqOsP x5CFrbthUj5d/Sd/3mcUxXtk5I8LYzvzEZQ9M= MIME-Version: 1.0 Received: by 10.213.23.84 with SMTP id q20mr3265125ebb.55.1258960574394; Sun, 22 Nov 2009 23:16:14 -0800 (PST) In-Reply-To: References: Date: Mon, 23 Nov 2009 07:16:14 +0000 Message-ID: <3a142e750911222316m7b7b374ajd087fd28581a7256@mail.gmail.com> From: Paul B Mahol To: Rui Paulo Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-mobile@freebsd.org, michael brindle 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: Mon, 23 Nov 2009 07:16:16 -0000 On 11/23/09, Rui Paulo wrote: > On 22 Nov 2009, at 23:39, 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). >> >> 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 >> >> 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? > > No, it could just be that the driver is providing wrong tx power > information. No, because regdomain is not set txpower is always reported to be 0. iwi driver doesn't have TXPMGT cap (looks to be bug), so you can not set txpower at all because net80211 thinks it is not supported.