>
> Yup, I use it, no problem at all. Much more solid for me than ipw3945
> cards.
>
> Why don't you write back with the output of
> iwconfig
> (as root, edit out your wireless password) and give the explicit
> commands you use with iwconfig to set up your config.
>

To begin with, I have never had any problems with dhcpcd, if they were,
they were, they were always with buggy dhcp servers.

Anyway, the sequence goes:

iwconfig indicates as follows:

Cell 01 - Address: 00:08:A1:A8:02A
ESSID:"Exploris"
Protocol:IEEE 802.11bg
Mode:Master
Channel:11
Encryption keyn
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Quality=77/100 Signal level=-52 dBm
Extra: Last beacon: 64ms ago

then

iwconfig eth1 essid Exploris key s:BLAblaBLA

which gives correct hex code:

iwconfig once again

eth1 IEEE 802.11g ESSID:"Exploris" Nickname:"slacky"
Mode:Managed Frequency:2.462 GHz Access Point:
00:08:A1:A8:02A
Bit Rate:54 Mb/s Tx-Power=20 dBm Sensitivity=8/0
Retry limit:7 RTS thrff Fragment thrff
Encryption key:3339-3735-3637-3437-4141-0000-00 Security
modepen
Power Managementff
Link Quality=77/100 Signal level=-52 dBm Noise level=-87 dBm
Rx invalid nwid:0 Rx invalid crypt:40 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

finally:

dhcpcd eth1


And as a result no IP is assigned though wifi card stayed connected to AP

dhcpcd debug looks like this:

dmesg states as follows:
ieee80211_crypt: registered algorithm 'WEP'

A bit puzzling to me is the fact that module ieee80211_crypt_wep is never
loaded and dmesg somehow regonizes this protocol. Possibly another
ieee80211 module handle this since modinfo ipw2200 does not mention WEP
among supported protocols.

Anyway I provided passphrase with and without s: option, tried to run
dhcpcd with -r option.

On the other hand I will give a different dhcp client a try since dhcpcd
-d returns "timed out waiting for a valid DHCP server response "

--
luk