iwi connect problems in 9.0-CURRENT

[Paul B Mahol]

On 11/23/09, Rui Paulo <rpaulo at freebsd.org> 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<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> 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.