iwi connect problems in 9.0-CURRENT

[michael brindle]

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?
Why can I not manually change it?
Which leads to the ultimate question of:
How do I get it to connect?

Thanks in advance.
Michael Brindle.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: YOUNATA
Type: application/octet-stream
Size: 13106 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-mobile/attachments/20091123/ec259d8f/YOUNATA.obj